WampServer

Hello,

WampServer 2.5 (Apache 2.4.9, PHP 5.5.12, MySQL 5.6.17) is now available on the home page of Wampserver.com

This is also available from Sourceforge WampServer 2.5 and for the 32bit version choose
"wampserver2.5-Apache-2.4.9-Mysql-5.6.17-php5.5.12-32b.exe/download"

and for the 64bit version choose
"wampserver2.5-Apache-2.4.9-Mysql-5.6.17-php5.5.12-64b.exe/download"
And not the big green Download button.

Wampserver 2.5 will not run on Windows XP

Two versions in 32 and 64 bits comprise the same Apache, PHP and MySQL versions.
I recommend always installing the 32-bit version, even on a 64 bit system.

Do not install this version over an existing version , follow the steps : Installing a new release of WAMPServer [forum.wampserver.com].


If you really want to install both the 32bit and 64bit versions on the same machine it can be done, however it must be done in two different folders, eg C:\wamp\ and C:\wamp64\.
The two versions can coexist on the same machine but do not run both at the same time.




See the bottom of this document for some late breaking changes and correction



-------------------------------------------------- ---------

WampServer 2.5
- Apache 2.4.9
- PHP 5.5.12
- MySQL 5.6.17
- PhpMyAdmin 4.1.14
- SqlBuddy 1.3.3
- XDebug 2.2.5
- phpsysinfo 3.1.12

Requirements .

WampServer 2.5 includes, among others , Apache 2.4.9 and PHP 5.5.12 that are "compiled" with Visual C++ 2012, more commonly referred to as VC11.

The VC11 library will not run on Windows XP, even SP3 or Windows Server 2003, so the minimum system requirements to run WAMPServer 2.5 are:
Windows 7 SP1 ,
Windows 8/8.1 ,
Windows Vista SP2 ,
Windows Server 2008 R2 SP1 ,
Windows Server 2012/R2.

A binary compiled using VC11 can load modules compiled with VC11, VC10 or VC9, but is totally incompatible with modules compiled using VC6.
This means that only Apache, PHP or MySQL versions compiled with VC9+ can be retrofitted, which excluded PHP 5.2.x, Apache 1.3 and 2.0 branches.

WampServer 2.5 uses symbolic links and junctions and will only work with NTFS formatted disks or partitions and not with FAT32 drives.
You should also ensure that you have the latest versions of the VC11 C++ runtime: [ [www.microsoft.com] ]

Note: If you use a Windows 64-bit version, you must install both 32 and 64 bits versions of the VC11 (2012) runtime. The vcredist_arm.exe file only concerns ARM and Windows RT, for example the shelves SURFACE processors.

None of the addons available for download are compatible with WAMPServer 2.5
However it is perfectly possible to manually add versions of Apache, PHP and MySQL. See the forum for help on this.
-------------------------------------------------- -

News for WAMPServer aficionados:
here are the main changes and trends:

--- Home WampServer ( wamp/www/index.php )
- The vhosts folder is no longer used, as the new vhosts menu uses the original /apachex.y.z/conf/extra/httpd-vhost.conf file to display all your virtual hosts on a new menu.
- Tools, Projects and Alias are now displayed in 3 columns at the bottom of the homepage
- Recoding in utf-8
- Added index in $languages ??[ 'en' ] and [ 'en' ] :
'local' for set_locale
' DOCP url PHP documentation
' docm url MySQL documentation
' doca2.2 url of the Apache 2.2 documentation
' doca2.4 url of the Apache 2.4 documentation
'server' Server Software
- PHP extensions are displayed alphabetically, depending on your location
- Links now exists to the Apache, PHP and MySQL documentation
- Added variable $suppress_localhost = true;
true will stop localhost/ being placed in front of the subfolder name, useful for Virtual Hosts links.
- W3C Compliance by adding <li> ... </li> on variables $aliasContents and $projectContents when empty

--- General Configuration ( wamp/wampmanager.conf )
- Added editor in [main] section for the path of the text editor
You can put the full path to a text editor of your choice and any link that would have launches notepad will use your prefered editor
for example : editor = "C:\Program Files\Notepad++\notepad++.exe"
- Added [services] section with the name of the two windows services
This allows you to hold together the two versions 32 and 64 bit with different service names
ServiceApache = " wampapache " or " wampapache64 "
ServiceMysql = " wampmysqld " or " wampmysqld64 "
+ Note: The above variables require additions changes in wampmanager.conf files wampmanager.tpl ,
config.inc.php , scripts/refresh and scripts/wampserver.lib.php
The contents of the variables need to be changed with WampServer stopped.

--- Template File (wamp/wampmanager.tpl)
- There are 2 new submenus that you can have on the wampmanager left click menu.
One for your Virtual Hosts called (My Virtual Hosts ) and one for Projects i.e subfolders in the www folder called (My Projects)
The (My Projects menu is configured by default but the (My Virtual Hosts ) is not.
To activate, in the section ;WAMPMENULEFTSTART you may add a line after the localhost definition line,
;WAMPPROJECTSUBMENU For projects and
;WAMPVHOSTSUBMENU For Virtual Hosts
- Variables declared in wampmanager.conf
"notepad.exe" replaced by "${c_editor}" can be used to add your personal editor as the defult editor.
- Services and wampapache wampmysqld
wampapache replaced by ${c_apacheService}
wampmysqld replaced by ${c_mysqlService}
+ Note: The above variables have needed changes to these files
wampmanager.conf, wampmanager.tpl, config.inc.php, scripts/refresh and scripts/wampserver.lib.php

--- Library ( wamp/scripts/wampserver.lib.php )
- Fixed bug selecting the wrong php.ini file during a change of Apache.
- Create symbolic links instead of copting files
For phpx.yz/phpForApache.ini -> apachex.yz/bin/php.ini
Dll for phpx.yz/x.dll -> apachex.yz/bin/x.dll
- Updated version of PHP
- Added IPv6 detection function

--- Configuration ( wamp/scripts/config.inc.php )
- Variable for default text editor
- Variables for both services and wampapache wampmysqld
- $PhpDllToCopy Table amended to reflect new versions of PHP

--- Generator wampmanager.ini ( wamp/scripts/refresh.php )
- Symbolic links instead of copying files
- Cross referencing PHP extensions and dll files in the ext directory
The menu will show a Triangle if dll file exists but there is no extension line in php.ini
Display a "red square" if extension line in php.ini but no dll exists in the ext directory
- Same principle is used for Apache modules and LoadModule lines and file *.so
- Create any sub menus for My Projects and Virtual Hosts
- Adding variables to the path of the text editor
- Added variables for both wampapache and wampmysqld services
- Added flags FILE_IGNORE_NEW_LINES | FILE_SKIP_EMPTY_LINES in file (...)
to avoid inadvertent deletions purposes lines.
- Replacement of die ( ... ) by error_log (...)

--- Online/Offline ( wamp/scripts/onlineOffline.php )
- Supports configuration differences between Apache 2.2 and 2.4
- Support IPv6 or not

--- Change Apache Version ( wamp/scripts/switchApacheVersion.php )
- Dynamically update old Apache version used

--- Change MySQL version ( wamp/scripts/switchMysqlVersion.php )
- Dynamically Update old MySQL version used

Please do not post questions in this thread with related to this new version.
For any problems installing or running , create a new thread containing the answers to READ BEFORE YOU ASK A QUESTION


Late breaking changes and corrections to the WAMPServer 2.5 release

WampServer 2.5 and PHP 5.6.b2

- Due to a change in PHP 5.6.beta2 to "switch" properly to PHP 5.6.beta 2 you must take into account the new dll files in this PHP release.

Before switching to PHP 5.6.b2, in the "wamp\scripts\config.inc.php" file replace:

$phpDllToCopy = array (
	'icudt52.dll', //[modif oto] - Ajouts pour éviter unknown error PHP 5.6.a2

With

$phpDllToCopy = array (
	'icudt53.dll', //[modif oto] - Ajouts pour éviter unknown error PHP 5.6.b2
	'icuin53.dll',
	'icuio53.dll',
	'icule53.dll',
	'iculx53.dll',
	'icutest53.dll',
	'icutu53.dll',
	'icuuc53.dll',
	'icudt52.dll', //[modif oto] - Ajouts pour éviter unknown error PHP 5.6.a2

If you intend to install other versions of Apache or PHP and to avoid problems in future versions, it is necessary to add some extra code to detect incompatibilities between Apache and PHP.

So edit wamp\scripts\refresh.php

Change :

 // PHP incompatible avec la version courante d'apache
  $incompatiblePhp = 0;
  if ($apacheVersionTemp == '')

To

 // PHP incompatible avec la version courante d'apache [mod oto25]
  $incompatiblePhp = 0;
  if ($apacheVersionTemp == ''
      || !isset($phpConf['apache'][$apacheVersionTemp]['LoadModuleFile'])
      || empty($phpConf['apache'][$apacheVersionTemp]['LoadModuleFile'])
      || !file_exists($c_phpVersionDir.'/php'.$onePhpVersion.'/'.$phpConf['apache'][$apacheVersionTemp]['LoadModuleFile']))

And change:

 // apache icompatible avec la version courante de PHP
  $incompatibleApache = 0;

To

// apache incompatible avec la version courante de PHP [modif oto25]
  $incompatibleApache = 0;
  if ($apacheVersionTemp == ''
      || !isset($phpConf['apache'][$apacheVersionTemp]['LoadModuleFile'])
      || empty($phpConf['apache'][$apacheVersionTemp]['LoadModuleFile'])
      || !file_exists($c_phpVersionDir.'/php'.$wampConf['phpVersion'].'/'.$phpConf['apache'][$apacheVersionTemp]['LoadModuleFile']))

WAMPServer 2.5 64bit MYSQL ONLY

The my.in file contains a woops!

Edit the my.ini file using the wampmanager menus (wampmanager->MySQL->my.ini)

Locate this section header

[wampmysqld]

and change it to

[wampmysqld64]

Revert WAMPServer 2.5 "Your Projects" links to pre 2.5 mechanism

It would appear that some WAMPServer users cannot cope with creating Virtual Hosts for each of their sites/projects.

This is code that will be in the next version of WAMPServer so if you to want your "Your Projects" menu to provide links in the form 'localhost/folder_name' rather than 'folder_name' so you dont have to create a simple Virtual Host definition, here is how it should be done.

I would enphasise, this is not the recommended mechanism. The only GOOD solution is to use the Virtual Host mechanism
However, making these changes will not harm WampServer and you can always set suppressLocalhost = "yes" to keep the WAMPServer2.5 mechanism.




1 - Edit wamp/wampmanager.conf

In the section [main] add this line :

suppressLocalhost = "no"

Save the file

If this is set to "no" Your Project links will be in the form `localhost/folder_name` i.e. the pre WAMPServer 2.5 way.
If this is set to "yes" Your Project links will be in the form `folder_name` and require a Virtual Hosts definitions to work.



2a - Edit \wamp\www\index.php

Locate this line

$suppress_localhost = true;

and comment it out like so:

//$suppress_localhost = true;

2b - Find this line

$wampserverVersion = str_replace('"','',$result[1]); ajouter/add

and after that line add this code

//[modif oto] - On récupère la valeur de suppressLocalhost
preg_match('|suppressLocalhost = "(.*)"|',$wampConfFileContents,$result);
if($result[1] != "yes" )
	$suppress_localhost = false;
else
	$suppress_localhost = true;

Save this file


3 - Edit /wamp/scripts/config.inc.php
Find this line

$c_editor = $wampConf['editor']; ajouter/add :

and after that line add

//[modif oto] Ajout variable suppressLocalhost
if($wampConf['suppressLocalhost'] != "yes" )
	$c_suppressLocalhost = false;
else
	$c_suppressLocalhost = true;

Save the file



4 - Edit /wamp/scripts/refresh.php
Find this line

		{
			$myreplacesubmenuProjects .= 'Type: item; Caption: "'.$projectContents[$i].'"; Action: run; FileName: "'.$c_navigator.'"; Parameters: "['.$projectContents][$i].'/"; Glyph: 5

and REPLACE it with

		{ //[modif oto] Support de suppressLocalhost dans wampmanager.conf
			$myreplacesubmenuProjects .= 'Type: item; Caption: "'.$projectContents[$i].'"; Action: run; FileName: "'.$c_navigator.'"; Parameters: "'.($c_suppressLocalhost ? "[" : 'http://localhost/').$projectContents[$i].'/"; Glyph: 5

Save this file.


The changes are now complete.

Now restart WAMPServer



Edited 6 time(s). Last edit at 11/17/2014 10:05AM by RiggsFolly.

Bonjour,

Ajouter ou non 'localhost' dans les urls de lancement des projets.
Add or not 'localhost' in the launch projects url.

Il faut modifier quatre fichiers et les modifications sont données par rapport aux fichiers originaux tels qu'ils sont après installation de Wampserver 2.5.
Four files must be modified and the changes are relative to the original files as they are after installing WampServer 2.5.

- 1 - Fichier/file wamp/wampmanager.conf
-- 1a - À la fin de la section [main] juste après defaultLanguage = english (ou french) ajouter :
-- 1a - At the end of the [main] section just after defaultLanguage = english (or french) add:

suppressLocalhost = "no"

-- 1b - Sauvegarder le fichier modifié/Save the modified file
Nota : en remplaçant "no" par "yes" on revient au fonctionnement original.
Note: replacing "no" to "yes" we return to the original operation.

- 2 - Fichier/file wamp/www/index.php
-- 2a - commenter la ligne/comment the line $suppress_localhost = true;

//$suppress_localhost = true;

-- 2b - Après/after $wampserverVersion = str_replace('"','',$result[1]); ajouter/add

//[modif oto] - On récupère la valeur de suppressLocalhost
preg_match('|suppressLocalhost = "(.*)"|',$wampConfFileContents,$result);
if($result[1] != "yes" )
	$suppress_localhost = false;
else
	$suppress_localhost = true;

-- 2c - Sauvegarder le fichier modifié/Save the modified file

- 3 - Fichier/file wamp/scripts/config.inc.php
-- 3a - Après/after $c_editor = $wampConf['editor']; ajouter/add :

//[modif oto] Ajout variable suppressLocalhost
if($wampConf['suppressLocalhost'] != "yes" )
	$c_suppressLocalhost = false;
else
	$c_suppressLocalhost = true;

-- 3c - Sauvegarder le fichier modifié/Save the modified file

-- 4 - Fichier/file wamp/scripts/refresh.php
-- 4a - Remplacer/replace

		{
			$myreplacesubmenuProjects .= 'Type: item; Caption: "'.$projectContents[$i].'"; Action: run; FileName: "'.$c_navigator.'"; Parameters: "['.$projectContents][$i].'/"; Glyph: 5

par/by

		{ //[modif oto] Support de suppressLocalhost dans wampmanager.conf
			$myreplacesubmenuProjects .= 'Type: item; Caption: "'.$projectContents[$i].'"; Action: run; FileName: "'.$c_navigator.'"; Parameters: "'.($c_suppressLocalhost ? "["]; : 'http://localhost/').$projectContents[$i].'/"; Glyph: 5

Et voilà, c'est terminé. Il suffit de relancer Wampserver ou Clic-droit puis 'Refresh' pour que les modifications soient prises en compte.
And voila, you're done. Just restart WampServer or right-click then 'Refresh' for the changes to take effect.

Malgré tout, je persiste et je signe, c'est une très mauvaise solution, la seule bonne solution est d'utiliser les "VirtualHost".
Nevertheless, I persisted and I sign, it is a very bad solution, the only good solution is to use the "VirtualHost".

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Dear Friends!
I've followed your suggestions and now I've end up with an error message from refresh.php:

[03-Aug-2014 01:15:23 Europe/Paris] PHP Parse error: syntax error, unexpected ']' in C:\wamp\scripts\refresh.php on line 659

I've tried to restore this line or even replace "refresh.php" with an old one but nothing helped. So now WAMPSERVE icon is brown and I can't do any thing.

Could you help me like sending "refresh.php" which I can use?
Thank you very much,
Israel Khavinson



Edited 1 time(s). Last edit at 08/03/2014 03:07PM by Otomatic.

Israel,

I sent an email. you had better edit this post and remove you remail address or you will start getting lots of spam.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

hello,

i have installed wampserver2.5 and its running well on my server but i cant connect on LAN on b4bits. Kindly help me on what to do so that i can connect other clients on the network to the server where wampserver2.5 in running.
thank you.

WAMPServer is configured ( out of the box ) to be a development tool i.e. for one person to use on their PC and for security reasons all access is limited to that one PC i.e. 127.0.0.1, localhost and ::1 all of which are synonyms for ( just this PC )

So if you want to allow access from other PC's on your network you have to change apache so that it allows these accesses.

Will all these people be running a site you have created or are they all developers who will be working on developing a site?

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

wampserver2.5-Apache-2.4.9-Mysql-5.6.17-php5.5.12-64b.exe
Unmodified links !
Profiles：bin\apache\apache2.4.9\conf\extra\httpd-autoindex.conf

Alias /icons/ "c:/Apache24/icons/"

<Directory "c:/Apache24/icons">
Options Indexes MultiViews
AllowOverride None
Require all granted
</Directory>

Yes,

You will find that most of those files in the extra subdirectory are not tailored to wamp for you. They come as released by the Apache community.

Some things you have to do for yourself!

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Just a note. Your assumption about using virtual hosts being the "only good way" makes some baseless assumptions about how people do web development. In practice, the typical work flow I have seen is to do the basic web site on localserver, then move to a subfolder on a real web server for testing (web server != localserver) and customer feedback, then AFTER the customer has approved the new site move it to the final location. Localserver virtual hosts have no place in that workflow.

Also if a framework or CMS breaks on not being installed in document root that is a pretty serious bug that should be fixed, not supported with server reconfiguration. For the record neither Wordpress nor Joomla has issues with being installed to subfolders. With good reason too, as having independent sub-websites seems to be suprisingly common. (Joomla actually can emulate that with single installation, but it is often easier and more secure to install a separate Joomla in the subfolder.) And obviously you could set that subfolder as a separate domain as you seem to presume, but in many cases there is no actual benefit for doing so. (Some typical patterns: "maindomain.net/extranet", "maindomain.net/specificproject".

I'll agree that using virtual servers would make moving web sites directly to final location easier, if your workflow skips the customer feedback phase (say you are the customer or work directly for the customer), but seriously... You should not skip testing on web server before going public, period. Also moving web sites is as much of a routine operation as adding a virtual host, so there is no real saving in effort possible from using virtual host. Well, if you are REALLY competent in Apache configuration, but have limited experience in this part of web site development it might FEEL easier.

Meanwhile, I'll just tell people that WAMPserver links are broken in 2.5 version. Using links that require virtual hosts without any virtual hosts is pretty much definition of broken. I kind of understand the idea, but this just does not work. As a minimum a notice that you'd prefer people to set up virtual hosts because some people use broken software that requires that would have been nice.

Addition:
Also document root and web site root are two different and separate things. They probably usually are the same if you use mod_apache PHP like WAMPserver does, but that is not necessarily the case on shared web servers where PHP is often set up with suPHP and FCGI due to improved security and stability when using complex PHP applications (install extensions and self update) on shared servers.

I apologize for posting in this thread instead of the one specific to the topic. Feel free to move this and the post before. I came across this while looking for the necessary modifications to get the links to work, so I posted before noticing there is a separate more on-topic thread. Also I probably come off as a bit impolite, but being told that the issue is because I was too lazy to make a pointless change to Apache configuration that the links presume without notice did not improve my mood. And learning that the explanation for the change is basically nonsense did not help.

Hi Ville,

Please dont apologise, input is always welcomed. In no way do I/we consider ourselves omnipotent.

Initially, remember that it is just the links on the WAMPServer homepage that behave differently, when like you, you know what you are doing, it is of course quite possible to manually enter 'localhost/project' into the browser and a site will run just fine!


I feel though that a little bit of history may help you understand the reasoning for encouraging the general use of Virtual Hosts:


First please bear in mind that a large proportion of WAMPServers users are complete beginners to the Web Development world. They have next to zero knowledge of computing in general, and none with Apache, MySQL and PHP specifically.

A lot of them expect that because WAMPServer is so simple to install, that everything else about web development should be as simple. They expect to just install WordPress, for example, fiddle with a template and write a few pages, and a brilliant web site will fall out at the other end.
They rarely bother to hit the books and learn something about Apache or MySQL and so when they find their first challenge their solution is to blame the tools they picked i.e. WAMPServer


It was decided, by others closer to the actual WAMPServer team, that because this forum was recieving a large amount of help requests on the specific issue of moving sites developed on a localhost development environment to a LIVE mostly shared hosting package, that those that help out on the forum ( for free ) were having to spend an inordinate amount of time helping people over this process, even though it was actually nothing to do with WAMPServer but more to do with lack of knowledge and experience. It was of course because their own code was making assumptions that everything would work exactly the same on a live server as it does on their local PC environment. Lots, for example, dont even make sure that they are running a similiar version of PHP to that on their live server.


In general these issues revolved around writing code in a site in \wamp\www\{some folder} be that within a CMS or a generally available Framework or something they had come up with completely on their own. The issue almost always revolved around the fact that code was now not at the same level within the DocumentRoot on their nice new hosting package as it was when they developed it.

Of course the code that in general caused the problems was code written by these new developer without any understanding of the nuances of the environment they were developing in and not the specific CMS or Framework, although I have to say that WordPress specifically can be a complete nightmare to move from server to server even for the best of developers.


It was thought that if we encouraged the general use of Virtual Hosts that even the code written by beginners would have less likelyhood of catching them out when they moved their code, and I mean their code not the general CMS or Framework code, from their PC to their hosting package, because at least they had been developing their code in an environment that more closely matched the likely LIVE environment.



Regarding your phased release process.

Your process seems excelent, but those beginners I spoke about earlier are more likely ( judging by the request for assistance we get here ) to ask 'How do I open my develoment site up to my client so they can see it and sign it off'.
They then get sign-off and the client says, 'right put it live on this hosting package and I will pay you'.

They then ask here 'How do I do that' and get the obvious answer of copy the code using FTP and backup the database and restore it to the live server using phpMyAdmin.

They then copy it all to the clients server, restore the database to the live site, and then see that, OH NO!, It does not work, and fire off a unpleasant post here letting us know that WAMPServer has ruined their lives because it is useless.

Of course the issue is of ABSOLUTE URGENCY to them because they dont get paid untill the live site works, but the issues are not of WAMPServers making. However the solution of course is, in their eyes, totally down to someone here helping them work out what incorrect assumptions they have made in their own code.



Finally there is already code written ready for WAMPServer 2.6 ( or whatever it will be called, and dont ask me when it will be released ) that :-

1. Allows you to easily revert/switch between the old homepage mechanism and the new.

2. Adds all sorts a nice new helpful features to make using WAMPServer even more pleasurable and easy.
These we hope will also simplify the support requirements placed on this forum as well.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Thank you! The history makes it much more understandable. I'd go so far as to say you should add (copy/paste) it to the thread concerning this issue as the explanation there really did not explain anything to people who run into this. (<-only people likely to read the thread)

And yes, letting people change the behauviour based on what they are doing is obviously the way to go. Frankly the reason I got upset was that while I did not really understand what this was supposed to fix (I was lucky enough to be actually TAUGHT how to move Joomla installations, so I knew about path issues from the beginning and never connected them to WAMP), but it was blatantly obvious this new method would be a useless nuisance to many users who had already learned how to use WAMP.

And of course the biggest issue was that it didn't actually tell you to do virtual host, it would just fail without explanation, so the implementation failed in the sense of "let's reduce need for support".

Frankly still bit dubious about the value of using virtual hosts to protect people from bad code that TOTALLY WILL break sometime later, but certainly can understand how annoying answering the same basic issue repeatedly can become now that you explained the history. Although that "tutoring process" probably had an educational value of its own, and helped lots of people make better web sites. Making mistakes and then learning from them IS the natural learning method.

But seriously, thank you for giving a polite and helpful answer to my "ranting". Unfortunately, I usually post on forums when I am tired or upset about something (<-true of most people?), so while I TRY to be reasonably polite, I don't really succeed as well as I'd like.

RiggsFolly Wrote:
-------------------------------------------------------
> Two versions in 32 and 64 bits comprise the same
> Apache, PHP and MySQL versions.
> I recommend always installing the 32-bit version,
> even on a 64 bit system.
>

Hi RiggsFolly,

I am about to install version 2.5 and saw your above recommendation. Can you please advise why you do not recommend using the 64 bit system as I had assumed that this would be the preferred solution (assuming my machine is suitable).

Hi,

- Because Apache and PHP versions in 64-bit add nothing more, nor nothing better than 32-bit versions.
- Because some extensions do not exist in 64-bit.
- Because only PHP 7.0.0 brings real support for 64-bit integers.

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Hi RiggsFolly,

Firstly, I just wanted to say thanks for such a detailed response to Ville's post, at least some of us newbies do try to learn...LOL, and secondly, for being part of the team that is involved in supporting / creating this fine software.

Here is my question regarding getting 4 warning sign icons on Apache modules:
Auth_form_Module
Cache_soCache_module
Macro_Module
Proxy_wstunnel_module

By following your advice below I was able to remove 3 of my 4 warnings apart from my cache_socache_module warning.

Where I am confused is that in my \wamp\bin\apache\apache2.4.9\modules folder
the file is called mod_cache_socache.so

but you and an earlier poster Ben Brown, refer to the Cache_so_Cache_module and the file mod_cache_so_cache.so
does not exit in my modules folder.

When you have a moment can you please advise.

Many thanks.

Apache Version: 2.4.9
Php Version 5.5.12
MySql Version: 5.6.17
Windows 7 Professional
System Type: 32 bit
32 bit Wamp Version 2.5 from Wamp website
Wampserver Icon is green



RiggsFolly wrote:

“To explain these warning sign icons on Apache modules:
The warning sign means that either the module does not exist in the \wamp\bin\apache\apache2.4.9\modules folder

OR

There is no LoadModule statement in the httpd.conf file, but the module does exist in the \modules folder.

If it is the second issue then just add the relevant LoadModule statement into the httpd.conf file and if you are not actually using those modules add the '#' symbol in column 1 to make it a comment.

This should remove the warning icons.”

This line added to your httpd.conf file should solve the problem

#LoadModule cache_socache_module modules/mod_cache_socache.so

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Hi, RiggsFolly

Would you believe I had tried to do exactly that before my original posting and only now on looking again at the httpd.conf file do I see that I had made a typo...!!!

Many thanks.

Hi,

Congratulations on the (relatively) new version release! Since this is still being hosted on SourceForge and there is still a lot of distrust around the projects hosted there, would you be able to post an md5 hash of your original version of the 32/64 bit installers so we can put the concerns to rest?

I know a fair few people that have used WAMPServer in the past (myself included) but of course we absolutely cannot risk installing malware onto dev systems.

Many thanks!


Cheers,
Dave.

Hi,

> would you be able to post an md5 hash of your original version of the 32/
It is on the explanations: [sourceforge.net]

It is also on the thread about WAMPSERVER 3.0.0

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

This is perfect thankyou, and with a new version as well, even better!

Many thanks,
Dave.