Apache Friends Support Forum

Hello everyone --

Just a couple of notes on my experience in upgrading from 1.7.7 to 1.8, in case it helps anyone.

This time around, when I went to set the MySQL password through the panel (http://localhost/security/), it did not update the configuration files automatically.

I was baffled for a bit, but was able to resolve everything once I followed the instructions here:

http://www.apachefriends.org/en/faq-xampp-windows.html#password2

I had to manually set the cookie preference as well; it did not go through from the security console.

http://www.apachefriends.org/en/faq-xampp-windows.html#outsidepma

Lastly -- and I have never upgraded XAMPP before, so maybe this is standard, I don't know -- when I unistalled 1.7.7, I requested for the databases to be saved. Everything worked great, but all priviliges were revoked from users other than root, so I had to reset them through phpMyAdmin (or the command line would work too, I suppose.)

So... maybe someone will find this useful.

I am on Win 7 32-bit Home premium.

XAMPP 1.8.0 was announced as a new version - not as an upgrade

I"m curious how you did this:

when I unistalled 1.7.7, I requested for the databases to be saved.

The uninstaller asks to save your htdocs and mysql data folder. That would be fine if you were reinstalling the same version but when upgrading, you should really manually backup and reimport your custom databases.

there is a bug in 1.8 where it mangles drive letters on virtual servers.
for instance, I got
ServerRoot "E:E:/xampp/apache"
<Directory "E:E:/xampp/htdocs">
ScriptAlias /cgi-bin/ "E:E:/xampp/cgi-bin/"
<Directory "E:E:/xampp/cgi-bin">

mysql has the same problem in the my.ini
I think the installer has a problem.
I didn't check anything else. I suspect everything else is similarly broken if you have existing config files with specified drive letters.

WilliL wrote:XAMPP 1.8.0 was announced as a new version - not as an upgrade

So... what do you mean?

It means there are all new configurations, as its all on a new version. (among other things. Apache 2.4.2)

Therefore, you have to 'meld' old configurations into new ones. Only 'upgrades' fix configurations...

Its effectively like moving to a new server.

Does that make sense?

Good Luck