Already installed in root/zencart/ folder but want to view/access from root folder

oavs:

Ok Thank you for the good advise. I found a easier way may not be the developers ideal way.

For design/template.file customization changes

1. Duplicated the site on the server in a sub directory/folder
2. Make changes in the config file that is in the sub folder to reflect the sub folder location
   leave rest as is as same database /user/paswrd will work

For any database changes

1. Duplicate database in MySql change database name to xxxx_01

2. Make changes in the config file that is in the sub folder to reflect the xxxx_01 database name
   leave rest as is as same user/paswrd will work

3. Then copy of the edited /added files/images that work from sub folder to root site folder.

4. Make similar changes to mysql files if any.

Your idea that "design/template.file customization changes" somehow don't involve database changes is incorrect/misguided.. install a Pica-Flor Azul template as an example of what I mean -- install ANY module which adds an admin configuration menu and see how your "shared" database will impact your production site.. In fact install my WP4Zen plugin on your "dev" site with your shared database and see how it WILL BREAK YOUR LIVE SITE once you install the admin config options and update the dev site files but not the LIVE site files..

Sharing the LIVE database username/password with your DEVELOPMENT site is just a plain old BAD IDEA for all the reasons we cited before.. In fact this is a WORSE setup than your original idea of using redirects to point to the top level domain from a sub-directory after finishing development..

You seem resistant from doing things "the developer way" for reasons which make no good sense... Seems like you are trying to save yourself some time, and your time saving measures are aimed at the very wrong things and you are HE!! bent on implementing some DANGEROUS and FOOLISH (yep I said it..) practices...

You asked for suggestions and we gave you suggestions/best practice based ideas because we know from FIRST HAND EXPERIENCE that using poorly planned development shortcuts like the ones you propose will lead to issues.. I am probably not overreaching when I say that most who have chimed in here will probably support my thoughts when I say that your development shortcuts are flawed and will lead to issues..That said, you can approach this however you like..

Happy Zenning..

Hi
My be I did not explain correctly.

I did not say share the database.
"Sharing the LIVE database username/password with your DEVELOPMENT site is just a plain old BAD IDEA for all the reasons we cited before.. In fact this is a WORSE setup than your original idea of using redirects to point to the top level domain from a sub-directory after finishing development.. "

I said
"For any database changes

1. Duplicate database in MySql change database name to xxxx_01"

Having installed on the same same server with to identical database content with different database names on a separate folder with identical duplicate files has no baring on your live site. They are NOT connected. Its like having two identical cars (white and black)in the same garage with different rego/plates. They are identical in the sense that they DO look a like but in reality they are two different identities.

oavs:

Ok Thank you for the good advise. I found a easier way may not be the developers ideal way.

For design/template.file customization changes

1. Duplicated the site on the server in a sub directory/folder
2. Make changes in the config file that is in the sub folder to reflect the sub folder location
   leave rest as is as same database /user/paswrd will work

For any database changes

1. Duplicate database in MySql change database name to xxxx_01

2. Make changes in the config file that is in the sub folder to reflect the xxxx_01 database name
   leave rest as is as same user/paswrd will work

3. Then copy of the edited /added files/images that work from sub folder to root site folder.

4. Make similar changes to mysql files if any.

oavs:

Hi
My be I did not explain correctly.

I did not say share the database.
"Sharing the LIVE database username/password with your DEVELOPMENT site is just a plain old BAD IDEA for all the reasons we cited before.. In fact this is a WORSE setup than your original idea of using redirects to point to the top level domain from a sub-directory after finishing development.. "

I said
"For any database changes

1. Duplicate database in MySql change database name to xxxx_01"

Having installed on the same same server with to identical database content with different database names on a separate folder with identical duplicate files has no baring on your live site. They are NOT connected. Its like having two identical cars (white and black)in the same garage with different rego/plates. They are identical in the sense that they DO look a like but in reality they are two different identities.

The new content did not clarify the old content. (Language issue maybe?) It still appears that right now, both stores are using the same database. Once it is determined that something is to be changed in the database from the development site, then the new database would be created (or all of the tables copied and renamed, etc...) Until then, and the reason I provided the summary I did, it appears (even still now) that both systems will operate off of the same data. If it is true that the duplicate database won't exist until determined that data needs to be changed, then one would have to be extra vigilant to check all code before installing it for testing until that backup database is created. If both sets of data tables now exist in one database, then understand that one of the reasons to have a development site is to support updating of the software/database. By having a different table prefix/suffix, additional effort is needed to perform thatupgrade/replacement for transfer ofdatabase data between the two stores. This again is just one more way to make a mistake and take hours to troubleshoot and repair.

Consider the advice as what was paid for if desired, but either way the setup is likely to cause trouble in the future and does not fully take advantage of ZC's flexibility and ease of use.

oavs:

Hi
My be I did not explain correctly.

Your first option does INDEED say that you will have two sets of store files sharing the same database..

For design/template.file customization changes

1. Duplicated the site on the server in a sub directory/folder
2. Make changes in the config file that is in the sub folder to reflect the sub folder location
   leave rest as is as same database /user/paswrd will work

Did mc12345678 and I BOTH misunderstand this?? Because it certainly sounds as if you think that this setup works just fine if all you are doing is "design/template.file customization changes".

The short answer is that your assumption is wrong.. For all the reasons both mc12345678 and I have stated, but you seem VERY determined to work this way because you are CONVINCED this is easier/faster/shorter somehow.. So I wish you luck with your process.. I have to say that try as you may, you will not convince ANYONE who's done this kind of work for any length of time that your process will be easier/faster/shorter.. (again.. we REALLY know from FIRST HAND EXPERIENCE THAT IT'S NOT..)

So let's just say we'll agree to disagree with your process and wish you the best of luck..:smile:

Happy Zenning..