J'ai installer Wampserveur 2.5 64 bits qui fonctionne bien sur mon pc avec Windows 7 64 bits. Mais lorsque j'ai installé Webdev 18 avec l'option de configurer automatiquement le serveur web wamp, ce dernier (wampserveur) ne fonctionne plus, après avoir lancé une page web crée avec webdev. Ce qui est curieux, je vois le contenu du fichier httpd.conf de Apache être effacé et réduite tout simplement en ceci:
# # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:[httpd.apache.org]; for detailed information. # In particular, see # <URL:[httpd.apache.org]; # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/access_log" # with ServerRoot set to "/usr/local/apache2" will be interpreted by the # server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log" # will be interpreted as '/logs/access_log'. # # NOTE: Where filenames are specified, you must use forward slashes # instead of backslashes (e.g., "c:/apache" instead of "c:\apache". # If a drive letter is omitted, the drive on which httpd.exe is located # will be used by default. It is recommended that you always supply # an explicit drive letter in absolute paths to avoid confusion. ServerSignature On ServerTokens Full
# # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to specify a local disk on the # Mutex directive, if file-based mutexes are used. If you wish to share the # same ServerRoot for multiple httpd daemons, you will need to change at # least PidFile. # ServerRoot "c:/wamp/bin/apache/apache2.4.9"
Define APACHE24 Apache2.4
# # Mutex: Allows you to set the mutex mechanism and mutex file director ule ldap_module modules/mod_ldap.so #LoadModule logio_module modules/mod_logio. es/mod_speling.so #LoadModule ssl_module modules/mod_ssl.so #LoadModule status_module modules/mod_status.so #LoadModule substitute_module modules/mod_substitute.so #LoadModule unique_id_module modules/mod_unique_id.so #LoadModule userdir_module modules/mod_userdir.so #LoadModule usertrack_module modules/mod_usertrack.so #LoadModule version_module modules/mod_version.so LoadModule vhost_alias_module modules/mod_vhost_alias.so #LoadModule watchdog_module modules/mod_watchdog.so #LoadModule xml2enc_module modules/mod_xml2enc.so
<IfModule unixd_module> # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User daemon Group daemon
</IfModule>
# 'Main' server configuration # # The directives in this section set up the values used by the 'main' # server, which responds to any requests that aren't handled by a # <VirtualHost> definition. These values also provide defaults for # any <VirtualHost> containers you may define later in the file. # # All of these directives may appear inside <VirtualHost> containers, # in which case these default settings will be overridden for the # virtual host being defined. #
# # ServerAdmin: Your address, where problems with the server should be # e-mailed. This address appears on some server-generated pages, such # as error documents. e.g. admin@your-domain.com # ServerAdmin admin@example.com
# # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. e> # # Redirect: Allows you to tell clients about documents that used to # exist in your server's namespace, but do not anymore. The client # ows you to have certain browsers uncompress # information on the fly. Note: Not all browsers support this. # AddEncoding x-compress .Z AddEncoding x-gzip .gz .tgz # # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types: # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz AddType application/x-httpd-php .php AddType application/x-httpd-php .php3
# # AddHandler allows you to map certain file extensions to "handlers": # actions unrelated to filetype. These can be either built into the server # or added with the Action directive (see below) # # To use CGI scripts outside of ScriptAliased directories: # (You will also need to add "ExecCGI" to the "Options" directive.) # #AddHandler cgi-script .cgi
# For type maps (negotiated resources): #AddHandler type-map var
# # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI): # (You will also need to add "Includes" to the "Options" directive.) # #AddType text/html .shtml #AddOutputFilter INCLUDES .shtml </IfModule>
# # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # #MIMEMagicFile conf/magic
# # Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects # # Some examples: #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 [www.example.com] <Files Catalogue_Internet_PHP> ForceType application/WebDev18-awp Require all granted Allow from all </Files>
Jamais vous ne faites de sauvegardes AVANT d'installer des « trucs » ? Et puis, ne croyez-vous pas que l'aide, vous devriez la demander chez Webdev ? Parce que, AVANT Webdev, Wampserver fonctionnait sans problème. Vous avez installé Wampserver en 64 bits, mais est-ce que Webdev est, lui aussi en 64 bits ou compatible avec Apache, PHP et MySQL en 64 bits ?
Pour retrouver votre httpd.conf d'origine (et, peut-être d'autres fichiers modifiés subrepticement par Webdev), suivez la procédure ci-dessous.
Démarrer WampServer Icône wampmanager -> Arrêter les services Icône wampmanager -> MySQL -> Service -> Supprimer le service Icône wampmanager -> Apache -> Service -> Supprimer le service Maintenant on va quitter wampmanager. Clic-Droit Icône wampmanager -> Fermer Renommer le dossier wamp en ce que vous voulez, par exemple wamp_old. C'est votre sauvegarde.
Installer la même version de Wampserver que celle précédemment utilisée, dans le même dossier que la première installation C:\wamp\
Après cette installation, qui doit être fonctionnelle, même procédure : Démarrer WampServer Icône wampmanager -> Arrêter les services Icône wampmanager -> MySQL -> Service -> Supprimer le service Icône wampmanager -> Apache -> Service -> Supprimer le service Maintenant on va quitter wampmanager. Clic-Droit Icône wampmanager -> Fermer Renommer le dossier wamp en ce que vous voulez, par exemple wamp_new.
Renommer le dossier wamp_old en wamp Copier dans le dossier wamp, depuis wamp_new les fichiers qui ont été modifiés par Webdev.
Lancer Wampserver - Bien sûr, l'icône ne sera pas verte, mais : Icône wampmanager -> Apache -> Service -> Installer le service Icône wampmanager -> MySQL -> Service -> Installer le service Icône wampmanager -> Démarrer les services