hahaha Look at this point I have to laugh...or throw my laptop out a window!! haha
Agreed - project1/www Good Idea
Agreed - Server name and the project folder should also match for ease of use
(originally thats what I had had. By 5:30 AM when I finally copy and pasted yours and started to change to site1/site2 I missed the obvious server name.)
This is evident in something we BOTH missed. In your updated version project1 is listed twice, cause I copied and pasted and then modified accidentally skipping the servername due to fatigue.
What wasn't my mistake, which obviously I can't evidence, is the 1/2 dozen times I copied and pasted correctly. Naming it site1 & site2 didn't come from me. Nor did the idea of putting it directly into C:\ as I priory thought that was not possible. Still not convinced it is.
I have copied and pasted the NEW files I have.
They look very pretty! Problem is not fixed, it's worse! Now it automagically triggers a yahoo search! hahaha
Personal aside - I like your logic of the one million to one. Unfortunately, apache doesn't qualify for that exemption. It doesn't count when you have ten million database engineers constantly posting to help 1/2 billion people who cant make the crap work on a daily basis. I wouldn't define that, nor having a near monopoly of the playing field as "qualifiers" for a good system. It only proves that without a BA in server technologies...I have no other choice
It's not a position I have to argue, Google is my friend on that front. Just as anyone making 100k by developing for Apache will tell you it's wonderful.
All that crap is moot and non productive.
So since we STILL have a problem. "What have I done wrong", "What have I FAILED to do this time?"
Problem restated: Now typing project1 or typing project2 into the url will yield a yahoo search.
Steps taken: vhost file modified prior to starting Wamp
hosts file modified - CMD opened as admin - net stop dnscache - net start dnscache (success messages both times) Closed and reopened hosts to verify changes saved. Anything else? Vhosts file was opened in notepad++ which visually tells me when I need to save a file so that is it's own verification of completion.
Edits - changed duplicate project1 server definition to project2. Removed site1/site2 references and replaced with project1/project2 references. Changed destination folders to project1/project2. Added /www folders to project1/project2. Inserted the index.php files into said www folders.
(change to files included with this message) Removed your commented out lines from hosts file, resaved, verified save, stop/start cache (success) removed index.php from project1. Still only localhost works. Others open yahoo search. Open project1 from localhost and www folder showed up in index of. Open that and an error relating to an improper hello world php I slammed in there and was too lazy to fix.
Type project1/www or project2/www and nothing is found. One has a php file inside and one does not.
Before sending this message - Double checked the localhost and there is still NO virtual hosts menu.
Honestly I DO hope you prove me wrong. What would I gain by being right in this situation??? seriously? But using the scientific method...title to this post still stands until such proof illuminates the situation.
UPDATE: After doing all this fooling around, many websites started loading very slowly. Wonderful. Luckily took CCLEANER and cleaned the registry. Shutdown hotspot in case of throttling. and waited 5 minutes. Good as new. So I tried my vhosts once again and noticed something i missed. (also changed default search engine to google) A small button in Firefox asks if I want to GO to project1 or project2. This of course is after initiating a search. Then it proceeds to take me to localhost under the selected vhost name.
Thanks for the response and the thoughtful help thus far. Regardless of my personality, It is appreciated.
Here's what I think is happening. At one point I did look for an alternative. Tried 2 things (this was a couple months ago) I tried EasyPHP. DON'T EVER try that program!!! Uninstall the program, fix admin environmental paths only to find them automagically reappear. Yeah, like that! I hammered the problem for 3 days before finally destroying their lock on my system and doing a successful restore. They even went so far as to have MS say system restore wasn't possible due to a damaged disk. Funny...MS tooks checked and called BS on that!!!!!
Around that same time I testdrove MS IIS. IF it wasn't for EasyPHP leaving ghosts that probably interfered with my IIS user experience and prevented me from creating my Wamp stack with their software, If not for that my suspicion would be IIS ghosts remaining as a dirty trick to bring me back to IIS and basically "accidentally" shut you and your software out, unbenonst to me. But then again system restore should've made that all but impossible. I went back way before either of those programs was installed. Something is saying your program can't do this on my machine. I just don't know what it is. Tinkering with apache usually leads to problems exactly like this. That's why I deliberately try to avoid things like vhosts, unfortunately now I need one.
I may just have to call Microsoft and see what they recommend for my machine, of which they're just going to recommend IIS once again...grrr. Do you make a Lamp product that I can put on my Mint17 laptop? At least then if I have a problem a Linux techy will advise me how to use the console to FORCE your program to comply with the machine's written COMMANDS! Something that's not advisable to do on a MS machine. sigh....
Hosts File
----------------------------------
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 localhost
127.0.0.1 localhost
127.0.0.1 localhost
127.0.0.1 localhost
127.0.0.1 localhost
127.0.0.1 localhost
127.0.0.1 localhost
127.0.0.1 localhost
::1 localhost
#project1, not site1
127.0.0.1 project1
::1 project1
#project2, not site2
127.0.0.1 project2
::1 project2
VHOSTS file
----------------------
# Virtual Hosts
#
# Required modules: mod_log_config
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:[
httpd.apache.org];
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.
#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
#
<VirtualHost *:80>
DocumentRoot "c:/wamp/www"
ServerName localhost
<Directory "c:/wamp/www">
AllowOverride All
Require local
</Directory>
</VirtualHost>
<VirtualHost *:80>
DocumentRoot "c:/wamp/www/project1/www"
ServerName project1
<Directory "c:/wamp/www/project1/www">
AllowOverride All
Require local
</Directory>
</VirtualHost>
<VirtualHost *:80>
DocumentRoot "c:/project2/www"
ServerName project2
<Directory "c:/project2/www">
AllowOverride All
Require local
</Directory>
</VirtualHost>