Wamp Server Old Version Download

0 views

Skip to first unread message

Maitane Roderiques

unread,

Aug 3, 2024, 1:16:35 PM8/3/24

to trimenitria

I am having a problem in downgrading the MySQL version in WAMP. Currently I am using 5.6.12 and I need to downgrade it it 5.5. But before I can download the old version. By choosing 'get more...' option and it leads me to the MySQL add-on. But the website looks different. It only shows the WampServer installation. I can't find the MySQL add-ons.

First, make sure you have Wampserver 3.0.9 (or newer) installed on your machine. As of the time I'm writing this, it is not possible to download this version directly from the wampserver official homepage. You have to download and install 3.0.6 from wampserver.com and then update to 3.0.9. You can find the update installer here .

When I restart wamp I have the 2 versions of php the one I use actualy (5.5.12) and the one I want to instal (5.2.4) but when I choose the 5.2.4 my wamp icon became orange and stay like this I don't understand why.

I think best and easiest solution is download older version WAMP ,when installing WAMP you can choose what version of php(default they choose latest version, so attention for that,) do you need, that is work for me. for me need to install to php 7.00 so i tried this wamp 3.2 link here

After restarting WAMP services, and re opening the terminal, and restarting computer, it still not updated through phpinfo. It probably related the php version used by Apache service. How can I change this to 5.6.xAny suggestions ?Many thanks

Note : The issue is not related with changing php cli version as it was pointed here. I do not understand why some of them insist that this is potential duplication without reading the post carefully.

I have faced kind of similar issue, I have installed wampserver upgrades from =en. I needed php 7.3 and 7.4, after installing the php upgrades, those new versions were not being reflected in wampserver traymenu (left click on wamp icon->php-versions). After spending quite some time looking into this, finally could fix this by following steps :

(Long explanation)Hi, this happened to me today. I was trying to change the php version from 7.2 to 5.6 to test something. However, Wampserver was not changing the web version of php. After much searching in the web and noticing in certain videos that some people were getting a different menu than me in the wamp server icon, I realised that there is a whole left click menu in wampserver in which you can change the php version and it does change the web version of php.

I understand that this can be a bit confusing for people who are used to using wampserver, but for someone who is using it for the first time, we are not used to having a left click menu in the bottom right icons. I hope this saves some time for others who have a similar issue than mine.

If when you open a command windows and run the PHP interpreter >php.exe you actually get to the PHP interpreter, then you must have added one of the possible paths to one of WAMPServers PHP folders to the Window's PATH. You should never do this with WAMPServer, so if this is what you did, UNDO IT! This is for obvious reasons as you could have multiple versions of PHP available and want to run any one of them at any time as the CLI Version to test some code against multiple versions of PHP.

There is a tool for checking if you have all the possible required VC Runtimes installed. Go to this page, the backup repo for WAMPServer, and download the little utility called Checks VC++ packages installed you will find it down near the bottom of the page. Download and run it, then throw it away, as it changes over time as new VC Runtimes become required.

There is a Wamp Server 2.4 installed in my C: drive. I want to have a Wamp Server 2.5 in my D: drive. Because of some reason I cannot stop Wamp Server in C:. But at the same time I want to use 2.5 version.

However you cannot have 2 separate installs on 2 different drive as the services ( Apache/MySQL) will be overridden by the second install even though it in on a separate drive!!! So you will actually be running the second install and not the first.It is best if you install it in the root of the Disk you pick i.e. X:\wamp

Don't install it into Program Files, it will install there, but it adds unnecessary directory complexity and can cause problems as there is a space in that directory name. Remember, Apache/PHP/MySQL was ported from Unix and Unix does not like spaces in directory or filenames.

As of WampServer 2.5+ it is possible to install WampServer 32bit and WampServer 64bit at the same time on the same machine. This is because the names used for the 64bit Apache and MySQL services has been changed from the standard wampapache and wampmysql to wampapache64 and wampmysql64, so the 32bit services and the 64 bit services now have different names.

There is no real benefit in installing the 64bit WAMPServer over the 32bit version. In fact if you look at the PHP.NET site it warns us that 64bit PHP is infact still experimental. In fact it has not yet been completely ported to full 64bit code.

Don't start this process if you only have 20 minutes to get it done, that should be all you need, but depending on your skill level and the number of releases of all 3 pieces of software you are skipping it may take longer.

This whole process is based upon the fact that a WAMPServer install is basically just a copy of files onto your disk, with a little file tailoring so it knows which disk you installed it onto.The only things that are linked to the folder you install it into are the creation of the 2 windows services 'wampapache' and 'wampmysql'. So if we remove those, and there is a menu option to do this on wampmanager, then the install is removed, without actually deleting and files.

If they are large and phpMyAdmin fails to back them up ( normally due to a PHP max_runtime limit ) either increase the PHP max_execution_time or you will have to backup using the mysqldump.exe. [see manual if required](dev.mysql.com} for help on that.

However if you have done things properly and created specific MySQL users and passwords for each of your site(s) databases you are going to have to go and find out what these userids and passwords are and make a note so you can recreate them after you have restored your databases on the new version of MySQL.

Click on the phpMyAdmin link on this page, and check this works also.WampServer 2.4 comes with a different phpmyadmin configuration, so it will initially load to a login page. Remember on a new install the username = root and the password is BLANK.

If you get problem with either, remember this new install does not have any of the config tailoring that you may have done to the previous release. So now would be the time to compare you old config's with the new ones and bring over anything from the old config that you need again on the new install.

Specifically check these files, but depending on what you have done to Apache/PHP/MySQL there may be others, only you can know this.Make changes to these files bit by bit checking that Apache and MySQL don't report and errors between each change

Again things change, parameters get deprecate, new ones are created etc.For example if you are using INNODB databases you will have to activate the innodb parameters which are by default commented out.You may well have to check the mysql website for some information, they supply a How to upgrade page for all releases.

if you are going to mysql 5.6 you may want to add this parameter to reduce memory allocated my MySQL, the default tends to allocate around half a gig of memory, and this will reduce it to something more sensible. You may have to play with this to match your system requirements!!!!

Also remember if you are coming from a VERY OLD version of MySQL, this restore process may not be totally straight forward, and you should expect to have to tweek a few things when you find that the new version of MySQL does not like your old data. This is fairly unusual, but may happen. Again don't try and do this 10 minutes before you have to give a presentation using the new WampServer.

Remember the instructions in this file may need tailoring to the new release of Apache.At a minimum, remember to check for the 'Allow from', 'Require' changes, mentioned earlier, and uncomment the Include conf/extra/httpd-vhosts.conf line from your new httpd.conf file.

This file tells wampmanager what the PHP interpreter dll is called, that is compatible with which major version of Apache.This is used when switching between versions of Apache and PHP using the WampManager menus.The older versions may be missing the linkage instruction for Apache 2.4, so you will need to add this extra piece of code.

However only add this new section if that version of PHP actually has a file called 'php5apache2_4.dll' in its folder.If one does not exist, and they only exist for versions of PHP > 5.3.17 or there abouts, dont add this new section to wampserver.conf

So if you are running Apache 2.4.x and a version of PHP does not have a php5apache2_4.dll file, you will see a little no-entry icon beside that version when you use the WampManager menus and look at the PHP -> Versions menu. This is a visual queue that you should not switch to this version of PHP when using the currently running Apache version. Of course you can switch the version of Apache you are running to one that is compatible with that version of PHP and the visual queues will change indicating which versions of PHP are not compatible with the new version of Apache.

But remember this mechanism is controlled by the wampserver.conf file that is unique to each version of PHP. You cannot just add the new 2.4 information to every file, but only those versions that actually come with a php5apache2_4.dll. And before you ask, yes I suppose, and only suppose, it might be possible to re-compile old versions of PHP so thay are all compatible with Apache 2.4 but it is unlikely to happen. Old versions of PHP are old for a reason and you would only consider using them if you are trying to make your Development system as similar as possible to the LIVE environment that your code will be deployed on, or you are using some very old, and probably badly written php code. In that case you would almost definitely want to use an older version of Apache as well.