What problems could arise from updating php version?

[Ezpro9]

i havent really gotten a straight answer yet for this question - my client says:

"The developers are skeptical about the possibility to update PHP on our server as this could seriously damage the entire RV site functionality."

since i know nothing about php and any potential hazards i have to ask the community to see if there is any validity to these concerns.

we cant update our version of WP unless the version of php is first upgraded from 5.1.6 to 5.2.4

client wont do this because developers say its a potential nightmare

i , as seo, want a current updated version of WP for many obvious reasons

can anyone please tell me what, if any, problems could arise from upgrading the sites php? or is it just a lot of work and the developers are making excuses because they dont want to do it?

thanks very much to whoever answers

[RobertFisher]

Alan,

I cannot think of an answer I have seen recently with the clarity of thought and ability to refute a very bad practice. (Especially on a security level). One thing we do with clients and upgrades (we do not handle clients on other peoples platforms) is to take a new update, give it a few weeks for bugs to be discovered and then do the upgrade on our end. We have clients sign off on us handling the upgrades, etc. from the beginning of the relationship.

For Erik I would suggest showing the client what has been said by someone with a lot of savvy experience. If the devs are worth their salt, they will change.

This was a good question and Alan delivered a great answer.

Robert

[AlanBleiweiss]

I've got very limited bandwidth for training (90% of my work comes from audits) - and is typically limited to in-person on-site for clients in the LA area because I find the in-person experience to be much more effective. Pricing depends on level and extent, and starts at $250 an hour so is ideal for groups (one fee regardless of participant count). Audits range from $3500 upwards of $7500 or more depending on scale.

[Ezpro9]

what do you charge for

Individual Personalized Training? and site audits?

[AlanBleiweiss]

You can thank my combined 11 years SEO after 7 years web dev project management, with a background in information security and business ownership

[Ezpro9]

i want to have your baby

brilliant answer!

i just copy/pasted the entire thing to my client - even got your pic and bio in there for added cred.

i have been asking this question in one way or another since early Feb. and you just nailed it

thank you very much

[AlanBleiweiss]

Any time you upgrade a server solution, the potential exists for things that are currently working to suddenly break. That is just the nature of technology.  In an ideal world, this wouldn't happen, however unfortunately it's quite possible for many reasons.

Just one reason is technology developers cannot possibly test for every single unique server configuration on earth when working on an upgrade.  They have time, resource and fiscal constraints.

In one example of how an upgrade from PHP 5.1.6 to 5.2.4 caused a WP site to collapse, the problem was neither with PHP OR WP. It was with a separate server solution related to firewalls that had to then be dealt with.

That example validates the concern expressed by the developers you're dealing with.

HOWEVER

Regardless of potential problems of this nature, it is irresponsible and deplorable for developers to refuse to upgrade servers out of the fear that something might break.  Could you imagine 90% of the world still operating on IBM mainframe computers because of a fear to upgrade?  The security implications alone are appalling, let alone business-case reasons.

Developers and systems administrators "should" be required to implement upgrades on a regular consistent basis, with the understanding that it is their responsibility to deal with problems that may arise, and during upgrades "should" also use intelligent best practices precautions and methods to ensure the least likely chance for a critical failure.  THAT is the only proper business path for a business to remain successful long-term.

Hiding under the guise of "it's too dangerous" is a terrible pitiful excuse for laziness.