I didn't find much or complete information on how to install a second wordpress module in wamp stack, so I hope this helps.
Sadly Im using windows vista.
This is for localhost
1.Open command line
start bitnami-wordpress-4.1-0-module-windows-installer.exe --wordpress_instance_name whatevernameyouwant
3. Complete the setup
Note: change "4.0-1" for your actual version.
Thats it, if you dont see any prompt about an already existing wordpress folder that is not empty then everything is fine.
After that, you can access trough localhost/whatevernameyouwant
In phpmyadmin your database is in bitnami/bitnami_whatevernameyouwant
Remeber: this is for installing a second module, not a second stack
Note: This should work for any other module, joomla, drupal, magento, etc.
If you still can't install it, you can try installing multiple instances of wordpress on the same module, i.e, wordpress/site1, wordpress/site2 so youll have 3 wordpress instances running, 1. root 2. site1 3. site2 and it will work fine, to do this just copy a wordpress package to each directory and run the normal wp install, (create a database for each site)
The problem with this method is when you use custom permalink structure, or diferent from the wordpress default on site 1 and 2. It would try to redirect you to the root directory and youll see a 404 error.
- Open index.php on your root instalation i.e. wordpress/htdocs/index.php
- On line 17 change "
require( dirname( __FILE__ ) . '/wp-blog-header.php' );" to "
require( dirname( __FILE__ ) . 'site1/wp-blog-header.php' );" or "
require( dirname( __FILE__ ) . 'site2/wp-blog-header.php' );" depending on the site you're working.
This is a temporal solution so you would need to change this line for using each site using custom permalink structure.
Note: It may be a complemetary solution editing .htacces but It will work just editing index.php
Solution number 3 would be to set multisite. Im not sure at this moment so if someone may clear this part, youll be sharing database between sites with this method, so in case youll need to reset it for a single site youll need to find the database tables for that site and manually delete it. Its a minor problem but something to consider.