edpaffjr wrote:Any update on this? Or has anyone done an update using another method?
Since Apache was so obsolete and the security nazis in my organization threatened shutdown unless Apache was updated I went ahead and did a new installation into a differently named parallel folder using the zip file. I copied the sample configuration files to the correctly named ones (see the 8 configuration files listed at end of http://www.apachefriends.org/en/xampp-windows.html
). Then I brought up each of the configuration files alongside the same file from the original installation in text editors, scrolled through, and copied over any customized settings. If a setting was not listed in the original I just left it at default.
I then copied over the MySQL data folder intact (a backup and restore is probably a better approach). I also copied over any contents from httpdocs folder that was not default. I renamed both xampp root folders so the new one was now xampp as in a default installation. By keeping the original folder intact with no changes it is a simple procedure to restore original setup. Let's see, I then ran the setup_xampp batch file in xampp because I like absolute paths. This worked perfectly for me on a WordPress server. No problems. Oh, I think I had to reregister Apache and MySQL services. Like I said, you can't hurt anything if you keep original xampp installation intact.
No sooner did I accomplish that then I have to upgrade to the Apache in the currently unavailable XAMP Windows 1.7.3 beta. Yes, I know you aren't supposed to actually use xampp in a production environment and I probably wouldn't if I had to do it over again, but only because of the lag time in security updates on the Windows side of things. It is totally awesome otherwise.