NT Servers - PHP Upgraded 4.3.5

[Brangwyn]

S*** happens Dave, thanks for dealing with the issues promptly once they started cropping up.

For me personally it's not the fact there were problems, but more that we didn't know in advance something was being upgraded so we could have the chance to warn customers of potential errors. Like we are with Vortech, our customers are always a little more forgiving if they've had some advance warning.

[bigdave]

How much notice would everyone like when we do things like this? A day? A week? Is it more or less to let your customers know that the issue was planned and not a "problem"?

[Brangwyn]

For something like a PHP upgrade or similar I think 24-36 hours would be heaps for me personally .. just gives me a chance to at least post it on my support forum, and send out an email if I think it needs it too.

[bigdave]

Ok, Deal!

Originally Posted by Bladesnitz

I would suggest that if your app is dependent on these kind of variables that you specifically enable them via ini_set or a php.ini file, so that changes like this don't cause you problems. It may be that you are willing to risk the security of your site with such options, but our default settings will always be a little bit more secure.

Except that you have magic_quotes_gpc turned *on* on the Unix boxes--and you had it turned on on the NT boxes before the upgrade. Fortunately the web app (which I didn't write--I agree with you on the security issue) was being tested on one of my sites, and was not on a customer site. I don't like getting emails from a customer saying, "Hey, why isn't my content management (or calendar or whatever) not working?" and not having any idea why there's a problem.

I have no problem with uploading my own php.ini files. But, as has been pointed out elsewhere on the forum, some notice (at *least* 24 hours) would be nice when you're making changes that might break apps I've installed on my customers' sites.

Thanks.

[nelsonke]

Originally Posted by Brangwyn

For something like a PHP upgrade or similar I think 24-36 hours would be heaps for me personally .. just gives me a chance to at least post it on my support forum, and send out an email if I think it needs it too.

I am glad to hear that this will "never happen again" since we have had this discussion about notice before. On the positive side, thanks for staying with it and getting it fixed once the problem became evident!!!