Hi, I've resisted upgrading to php 5.2.x because of the implications and potential challenges of going to the "bleeding edge." However, my case for doing so has been mounting for some time, so I just recently attempted it. I followed the instructions listed here: http://www.virtualmin.com/documentation/id,virtualmin_bleeding_edge_pack... and then used the install package updates feature on the System Information page. The upgrade seemed to go just fine. The sys info reported the newer version, and VirtualMin was clearly still working without a hitch. However, both of my php websites (driven by a CMS called Concrete5) started to misbehave. The CMS would give me page not found responses when I tried to access the home page of a given site. I had also installed the latest version of phpMyAdmin, and while I could access the login page, once I logged in, I would get a "The requested URL /cgi-bin/index.php was not found on this server." error. I noticed the file path it complained about. It clearly didn't mention any part of /public_html/phpMyAdmin.
I have since used a backup to revert to a previous state, but at this moment, my life would be much simpler if I could just get php 5.2.14 installed AND have my php sites working properly. I realize that accessing the bleeding edge repos is likely outside of the support agreement, but I have to ask if you have any ideas, or if there are any resources I can access to make this work. I've already invested way to many hours in trying to resolve a snowballing issue.
Thanks for your time.