WampServer

First I installed wordpress direcly under C:\wamp\www. Then when I was going to install joomla I made a new directory called wordpress and put all files there.
Then I installed joomla with its direcory beside wordpress.
when I now tried localhost I get a page with "index of" and the name of the two cms.

What shall I do?

You have overwritten the index.php file that comes with wamp and is the wamp homepage.

NOTE: Always create a subfolder under the c:\wamp\www folder for your own sites, and never put your work in there.


Copy the Contents of index.php
OR Download index.php



Edited 10 time(s). Last edit at 02/06/2013 04:42PM by stevenmartin99.

now I get
( ! ) SCREAM: Error suppression ignored for
( ! ) Parse error: syntax error, unexpected '<<' (T_SL) in C:\wamp\www\index.php on line 92

Did you copy paste my original or click the link that Steve replaced it with??

I copied and pastet in index.php

Try clicking the links that Steve replaced my copy/paste code with.

I guess something got corrupted by the bulletin board software

When I read the conversation I can see that I didnt mentioned that I had a functionell database and localhost before I tried to install joomla. Does that change the solution maybee?

I have pasted in the new index.php and now I can reach the configuration page with my two projekts on. But when I am clicking my old projekt It takes me to a page "The webbrowser cant find the page" and a google searcher comes.

Riggs Folly: disapointed with you. How can you quit a conversation without go to botton with the question.
Dont y ou want us to use wamp??????`

I need to know:
1. The indexfile index.php shall it lay under www if you just use C://wamp/www
2. If I come to the configuarationpage and can see my nboth projects and I click on one and it says
"the webbrowser cant find your page What is realy the problem
What are Wamp looking for...
Just so I know

you cant write things like that on the forum!!!

He helps completely voluntarily on the forum for Wampserver as do i, and he has tried to help you and you have been quite vague in your attempts to explain the issue you have.


Either you can get teamviewer and me or riggs will help you , or i will bin the delete the thread as its not an issue with wamp at all, but a user error.



nothing makes sense about your original post. you purposely put wordpress into the www folder, and now you moved it into a folder , so what are you actually expecting to happen when you go to localhost??

a page with the names of the 2 folders, IS the expected result.


please clarify within 24hours or i will proceed to delete the thread

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]



Edited 3 time(s). Last edit at 02/08/2013 11:38PM by stevenmartin99.

Steven,

Thanks for watching my back.

egogh,

What WAMPServer is: A cool, easy for beginners, way of installing Apache, MySQL, PHP in a ready to go configuration.

What WAMPServer is NOT: A substitute for doing some research on how to use Apache, MySQL, PHP. They are not trivial applciation and you cannot expect to just know it because the install was easy. Also your lack on knowledge in Apache and MySql is not the fault of WAMPServer.


Ok so if you want my suggestion here it is:

If you want to run WordPress and Joomla you are best advised to create a virtual host for each seperate project.
In fact I would suggest a vhost for each project regardless of whether you are writing it from scratch or piggy backing off a pre built CMS. It is a much more reliable way of developing sources that will just copy to your live hosting site.


I would suggest uninstalling WAMPServer, deleting all folder from c:\wamp and then re-installing a fresh working version. Then create yourself 2 or more virtual hosts (see below).
Then install the WordPress and or Joomla from scratch, dont try copying it from a live site, until you have read up on the issues with doing that.


Heres a HOWTO create Virtual Hosts




HowTo: Create Virtual Hosts in WAMP

BEFORE DOING ANY OF THIS PLEASE ENSURE APACHE AND MYSQL ARE WORKING PROPERLY FIRST!!!


1. Create a new folder outside the wamp directory structure.
for example

C:\websites

but this can be on any disk drive visible to the PC running wamp


2. Create a subfolder in c:\websites for each site you want to create.
for example:

C:\websites\site1
C:\websites\site2

3. Edit the file C:\wamp\bin\apache\apachex.y.z\conf\extra\httpd-vhosts.conf
where x,y and z are the version numbers of apache that you actually have installed.

NOTE: If you are switching between 2 or more versions of apache this will have to be done to all your versions of apache in turn.

SUGGESTION: I like to use the format sitename.localhost to make it obvious to me that I am dealing with my localhost copy of a site, you may prefer another notation, thats ok, the word localhost has no actual defined meaning in this case, its just my way of naming my development versions of a live site.


example contents:

	#
	# Use name-based virtual hosting.
	#
	NameVirtualHost *:80

	## must be first so the the wamp menu page loads when you use just localhost as the domain name
	<VirtualHost *:80>
	    DocumentRoot "C:/wamp/www"
	    ServerName localhost
	    Order Deny,Allow
	    Deny from all
    	Allow from 127.0.0.1
    	# You would never want a remote user to see this wamp config page.
	</VirtualHost>

	<VirtualHost *:80>
	    DocumentRoot "C:/websites/site1"
	    ServerName site1.localhost
	    Options Indexes FollowSymLinks
	    <Directory "D:/websrc/www/site1">
			AllowOverride All
			Order Deny,Allow
			Deny from all
			Allow from 127.0.0.1
		    #If you want to allow access from your internal network
		    # For specific ip addresses add one line per ip address
		    #Allow from 192.168.0.100
	    	# For every ip in the subnet, just use the first 3 numbers of the subnet
	    	#Allow from 192.168.0
		</Directory>
	</VirtualHost>

Add as many <VirtualHost> as you require so each of your sites have one, changing the DocumentRoot, ServerName and any other of the parameters as appropriate.
This also allows you to make SITE SPECIFIC changes to the configuration.

NOTE: This will make the wamp manager "Put Online" function no longer have any effect of your sites, so leave it OFFLINE.
If you want to put one or more sites online you will have to change the Allow commands MANUALLY in this my-vhosts.conf file.

To check your subnet do the following:
Launch a command window, and run

    >ipconfig

Look for the line "Default Gateway" in the output and use the third number in your Allow commands.


4. Edit your httpd.conf file and search for these lines, they are near the bottom of the file.
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

5. Add a line under these to include your vhosts file, this will cause apache to register their existance.
Leave the origial httpd-vhosts.conf unchanged, it may serve as a useful reference if you get something wrong.
Also make a backup of this file as if you re-install or upgrade wamp it may be lost.
example:

Include conf/extra/my-vhosts.conf

6. While still editing your httpd.conf file search for

	#   onlineoffline tag - don't remove
	    Order Deny,Allow
	    Deny from all
	    Allow from 127.0.0.1

	</Directory>

DO NOT CHANGE THESE LINES!

Add the following after the <\Directory> tag

<Directory "C:/websites/">
    Order Deny,Allow
    Deny from all
    Allow from 127.0.0.1
</Directory>

This is to set security on your new directory structure so that access to these new sites is only allowed from 127.0.0.1 (localhost) and your internal network.
P.S. Your internal network will probably be something like 192.168.x.y, check your system first!


7. Now in order for your browser to know how to get to these new domain names i.e. site1.localhost and site2.localhost, we need to tell windows what IP address they are located on. There is a file called hosts that is a hangover from the days before Domain Name Servers (DNS) were invented. It is a way of giving nice easy rememberable names to IP address's, which of course is what DNS Servers do for us all now.

Edit your HOSTS file, this can be found in C:\windows\system32\drivers\etc
and is a file called "hosts", the file does not have an extension.
Windows protects this file so you must be an Administrator to be allowed to save changes to this file.

If you are using VISTA or Windows7/8 you may think you are an Administrator BUT YOU ARE NOT!!!!
So to edit this file you must launch your editor, or Notepad in a specific way to gain Administrator rights. To do this find your editors icon and launch it using the following key strokes:
Shift + Right Click over its icon, this will display a menu, click the item "Run as Administrator", and click "Allow" on the challenge dialog that will appear.

Now you are ready to edit the hosts file so navigate your editor to c:\windows\system32\drivers\etc\hosts

Add the following lines to this file

   127.0.0.1   site1.localhost
   127.0.0.1   site2.localhost

NOTE: You will need to add lines to this file for each new virtual host site you create.



8. In order for Apache to pick up these changes you must bounce apache.
Do this by: Wamp manager -> Apache -> Service -> Restart Service


You should now be able to use the address site1.localhost in your browser to get to your new sites.
Copy your sites code into the "C:/websites/xxxx" folder if you already have a site coded or,
place a quick and simple index.php file into the "c:\websites\xxxx" folder to proove it all works.

example:

   <!DOCTYPE html><html lang="en-US">
   <head>
   <meta charset="UTF-8">
   <title>SITE1</title>
   </head>
   <body>
   <?php echo '<div style="background-color:red;color;white;text-align:center;font-size:18px">HELLO FROM Site1</div>'; ?>
   </body>
   </html>

TROUBLE SHOOTING:
If you have used the new domain name ( site1.localhost ) and it has not found the site.
a. Check the changes to the hosts file.
b. Restart the "DNS Service" that runs in windows. This caches all doman names that you use in a browser so that the browser does not have to query a DNS Server each time you re-use a domain name. This may have cached your failed attempt but a restart is easy and should solve the problem and is quicker that re-booting windows, which should also work.
To do this launch a command window as an Administrator ( Shift + Left Click over the command window icon ) and run these 2 commands.

>net stop "DNS Client"
>net start "DNS Client"
Note: The quotes are required as there is a space in the services name.

@RiggsFolly Thank you for all. I am very satisfied with your answers. I think you are a god consulting person and I am convinced you are going to or already have made succes in work.
Of course I know that this is volontary basis.
I have got a perfect and total answer- Now I can move on.

Thanks again