Philip

I was against the twitter rush for the longest time, but I finally caved in. I use my twitter feed for a mix of business and pleasure, however I typically read instead of tweeting myself. For businesses, it is good because it provides (and used to be one of the fewer) real-time interaction where you can have people follow see that you are having site issues, or a new feature was launched, etc. For personal, it's nice to be able to follow celebs or follow vendors and their news/blogs.

When sending you need to be sure to have checked the "Save a copy in my outbox". If I remember correctly, this is not checked by default. (See attachment for where this is at) [attachment deleted by admin]

I'm running 8.0 and I still have it popup with a new window without a reload. :-/

At least in your eyes it is no harm, but in the website owner's eyes, it is harm. The only reason you'd be doing this is to scrape their page, no?

This topic has been moved to Miscellaneous. http://www.phpfreaks.com/forums/index.php?topic=348092.0

Legal Guide to Web & Software Development has helped me quite a bit legal issues around programming. It won't have exactly what you're looking for, but I think it would cover quite a bit. Of course, it is no replacement for an actual lawyer.

What not use something like a load balancer or scalable VPS?

Ahh, that's my favorite image to steal

Couldn't agree more. I've found after I sit down with a whiteboard and doodle a db design or logic pattern out, I tend to code quicker and end up with a result that is way more flexible & better fits my needs then when I don't. If you get completely stumped, there are plenty of open source PHP applications out there that have user permission systems, and robust ones at that.

Noise PNG can create similar images with the right settings

Whatever page you're currently on. At first it'd be index.php and then it'd be articles.php

I'm just stating facts Yup, and as thorpe mentioned in the post above, your boss may be getting somethings mixed up. IMO what I get from the quote I posted is that any form of access to any user accounts that was not created for nor by the user, then that access account (whether that's a system password such as DBs, server passwords, customer service, etc.) will need to rotate passwords every 90 days to the PCI guidelines. In the end, it really depends on your definition of "users". PS - also like thorpe said, I'm not PCI expert, and I'm not sure you'll find many of them on the forums. There might be one or two lingering around, but I don't know of any off the top of my head.

There are also scripts to reverse engineer it (despite their marketing claims). Nothing is perfect.

This PDF will help your boss win the battle. Section 8.5.9

Ads, popular tags, recent posts, etc.

Yup, which is what the one I listed does. Mounts it as as virtual hard drive

zwamp is what I use - however I've updated some of the packages manually since they are out-of-date.

Some people post links to their clients sites asking for help when they get in over their heads and then clients realize how they can't do what they promised. Another reason is because they never/couldn't fix problems on the site and the exploit still exists.

I've heard good things about CAS (Which includes a PHP lib) - but I can't say I've ever used it. I'm curious to know what your end result is, because I've always foudn this topic interesting

Sure, and that is very possible. However you could add something like an htaccess or simple php password to protect it.

Buck up and do the work quickly & correctly and then work on your own projects Brownie points to helping out others.

For us, we're more of a software / service oriented company (and more of an agency than IT, but it's close enough): System Infrastructure Upkeep of developed tools / software Solutions Planning / Design Custom Software Services Consulting / Documentation of existing software Training Project Management

Which is why I'm saying bring on the project management. Unless you're letting your team run around fixing and working on whatever they please like monkeys in a zoo pen, this shouldn't be occurring

This is where project management comes into play. Your developers should be assigned tasks, bug fixes, new developments, etc. Obviously if 2 developers are assigned 1 bug, they should be communicating back and forth on what is going on. Otherwise, typically you shouldn't run into the problem of 2 developers editing the same, in the same place. And in the case that they are editing the same file - that's what merge is for!