Need help to do an upgrade from 1.5.0 to 1.5.5

Managed to get the padding and the sidebox fixed.

When editing language files (for French), i doubt that entering "Ligne épaisse" will display correctly. I am familiar with the fact that in product headers, I would have to write "Ligne épaisse".
Is that the same code i should use for those language files?

Another question about language files. From what i see, any file in the "language" folder inside the admin folder seem to be only related to the admin side of the store, and not the front end, seen by the customers. Is that accurate? If that is the case, it means i would not need to translate those since i always use the English backend. Correct?

CaroleAs:

Another question about language files. From what i see, any file in the "language" folder inside the admin folder seem to be only related to the admin side of the store, and not the front end, seen by the customers. Is that accurate? If that is the case, it means i would not need to translate those since i always use the English backend. Correct?
Correct. The customers only see the text from the "store_root/includes/languages/YOUR_LANGUAGE" folders. So translation of additional module language files only have to be done for those. (I almost never translate admin files)

Design75:

Correct. The customers only see the text from the "store_root/includes/languages/YOUR_LANGUAGE" folders. So translation of additional module language files only have to be done for those. (I almost never translate admin files)

Thanks. That is what i thought too. No point to translate the admin side on my store either. That much less work to do!

Getting closer to the time I will be doing the live update.

• I edited the stylesheets as well as i will for now. I am quite happy with the current look. Similar enough for my audience to feel familiar, while still being updated.
• I installed 8 mods, which are probably going to be the bulk of my mods. They all work well so far.
• I translated all the pages I think I need translated, from the template and mods.

Although a lot of it was trial an error, i need to thank you for helping me.

But I still have a couple of questions to tweak my test site:
1- On my live store, I have a slideshow on the main page. I have NO CLUE how i did it, or where the file would be. Even using the F12, what I get does not help me. Would anyone be able to make sense of that information, so i can copy it to the test store? Once i know how to do that, i could do it again on the live site.

The slideshow is visible on the main page here: http://creationcassel.com/store
and the test store is here: http://challengemehq.com

I copied the content (source) from the live site to the test site, but i am obviously missing something.

2- - in any product description, is there a way to get the description on the right of the image, wrapped around? It looks odd to have all that blank space and evenything written below all the images.

I want to address something before those other more "viewing" related items get addressed.

You say: "I'm almost ready to do my live site upgrade"... tell me: how many times have you practiced doing an upgrade of the live site without affecting the current live site? What's it been a week or so of working through to this point? You may want to revisit the early postings of this thread, but you want to be able to transition the live site to the upgraded site relatively quickly (I mean if it takes you an hour or two not too big of a deal generally speaking, but you don't want it to take a day or two days...) so.

Practice... setup yet another database, use phpmyadmin to copy the database over. Copy your old store files to a location, edit the configure.php files to match this new store. Now... with your new files. Update this test site... go... :P

Does it look and act like your current test site? Have you removed whatever "protections" that you had/needed so that visitors and search engines alike can see the site and index it. Etc... if so, go ahead and put those back, but need to be able to do this and not take forever and possibly put your existing work in jeopardy.

1 - looks like the slideshow is generated by "fadeshow". Use the Developers Toolkit to search for "fadeshow1" in your old template's files.

DrByte:

1 - looks like the slideshow is generated by "fadeshow". Use the Developers Toolkit to search for "fadeshow1" in your old template's files.

Thanks. I found it in the html_header.php file. So I copied the script snippet to the test environment file, copied all the images and edited all the image source links. I copied it to the includes/templates/MY template/common/html_header.php but it is still not showing. It is a javascript and I am not familiar with that so I am not sure if there is anything else that should be copied.

mc12345678:

I want to address something before those other more "viewing" related items get addressed.

You say: "I'm almost ready to do my live site upgrade"... tell me: how many times have you practiced doing an upgrade of the live site without affecting the current live site? What's it been a week or so of working through to this point? You may want to revisit the early postings of this thread, but you want to be able to transition the live site to the upgraded site relatively quickly (I mean if it takes you an hour or two not too big of a deal generally speaking, but you don't want it to take a day or two days...) so.

Practice... setup yet another database, use phpmyadmin to copy the database over. Copy your old store files to a location, edit the configure.php files to match this new store. Now... with your new files. Update this test site... go... :P

Does it look and act like your current test site? Have you removed whatever "protections" that you had/needed so that visitors and search engines alike can see the site and index it. Etc... if so, go ahead and put those back, but need to be able to do this and not take forever and possibly put your existing work in jeopardy.

Of course, we have been at it for almost 2 weeks (but not working full time at it either)! During that time i have taken copious notes, i had issues with the database (caused by the tech from my host, while i now know how to do it myself), i had tried to install a mod that i will NOT install, searched for mods that would be compatible with 1.5.5 that could do what the previous ones did, i spent time installing and fixing installation on some mods that i had not installed correctly (took notes on that), translated many pages and files to French (took notes on that and saved the fiiles), worked with the css files for hours on my own (took more notes and will have the files saved).

So yes, I still have in-between steps before going "live". And i need your help AGAIN. When i had a test copy of my store, it was attracting visitors and they would make purchases on the wrong site. I had someone set up a redirect of some kind to the live site, but in doing so, also redirects the admin site, meaning i have no way to even log in. Since it was a clone of my site (a couple of years ago, but i had not made any change since, to the live site except adding 100+ products), i would like to use that as a second test to use an existing site to "upgrade". However, i need help figuring out what might have been changed/edited to cause the automatic redirect. I could try to compare files but i have no clue where to start with. Would you have a suggestion where to look and how i could access that existing test store?

The test store is here: http://creationcassel.com/storetest/

More than likely it is in your .htaccess at the root of the domain. It could also be in the sub-folder of that domain.

mc12345678:

More than likely it is in your .htaccess at the root of the domain. It could also be in the sub-folder of that domain.

There is one file on the root of the domain but both sites are on that, one with the /store/ and the other /storetest/.
I have one .htaccess at the root of the /store/ but not for /storetest/. Where should i compare??

Just in case (trial and error here), i compared the .htaccess file from the root of the domain, to the .htaccess inside the /storetest/ installation.
I see these lines that are in the /storetest/ file only:

RewriteCond %{REMOTE_HOST} !^142.167.20.37 <-- this looks like my IP but since i have a dynamic IP, right now, it is not the right one. So should i remove that? Changing it to my IP of today might block me again in the future.

Then, i see this line on the "original"
RewriteRule .* - [F]

but this in the /storetest/
RewriteRule (.*)$ http://www.creationcassel.com/store [R=301,L] <-- which looks like it might be a 301 redirect to the live store. Should i remove that and replace it with what is in the .htaccess of the root?

Would that grant me access to the store or will that cause other problems?

CaroleAs:

There is one file on the root of the domain but both sites are on that, one with the /store/ and the other /storetest/.
I have one .htaccess at the root of the /store/ but not for /storetest/. Where should i compare??

CaroleAs:

Just in case (trial and error here), i compared the .htaccess file from the root of the domain, to the .htaccess inside the /storetest/ installation.
I see these lines that are in the /storetest/ file only:

RewriteCond %{REMOTE_HOST} !^142.167.20.37 <-- this looks like my IP but since i have a dynamic IP, right now, it is not the right one. So should i remove that? Changing it to my IP of today might block me again in the future.

Then, i see this line on the "original"
RewriteRule .* - [F]

but this in the /storetest/
RewriteRule (.*)$ http://www.creationcassel.com/store [R=301,L] <-- which looks like it might be a 301 redirect to the live store. Should i remove that and replace it with what is in the .htaccess of the root?

Would that grant me access to the store or will that cause other problems?
First there seems to be a discrepancy between the two posts. First says no htaccess in the storetest directory, second says there is, so which is it?

Second thing is that the one in the store directory does do a redirect for all visitors no matter what file/directory they are trying to reach.
At this point it depends on how you want to proceed and what you want to do/be able to do. You could rename the folder and change the associated configure.php files, create the store folder again and place that htaccess there so that it continues to redirect like it always has been and then setup/establish the renamed folder to do like you are doing with your test location to prevent indexing and to indicate that the location is not a "functional" site.

You could also make the admin folder accessible by not redirecting if the admin folder has been chosen/used to access the site. Could also add a "temporary" ip redirect as part of that or not that... temporary because of the non-dedicated ip address and would have to be changed whenever your ip address changed.

As to the htaccess in the root, it too could have something in it that prevents access as htaccess files are somewhat similar to interfere with access to the store directory or once there to have caused an unexpected/undesired action.

All depends on how you want to have things set up.

mc12345678:

First there seems to be a discrepancy between the two posts. First says no htaccess in the storetest directory, second says there is, so which is it?
You are right. I reversed the two; one file in the domain itself and one on the /storetest/ but none in the /store/

mc12345678:

Second thing is that the one in the store directory does do a redirect for all visitors no matter what file/directory they are trying to reach.
At this point it depends on how you want to proceed and what you want to do/be able to do. You could rename the folder and change the associated configure.php files, create the store folder again and place that htaccess there so that it continues to redirect like it always has been and then setup/establish the renamed folder to do like you are doing with your test location to prevent indexing and to indicate that the location is not a "functional" site.

You could also make the admin folder accessible by not redirecting if the admin folder has been chosen/used to access the site. Could also add a "temporary" ip redirect as part of that or not that... temporary because of the non-dedicated ip address and would have to be changed whenever your ip address changed.

As to the htaccess in the root, it too could have something in it that prevents access as htaccess files are somewhat similar to interfere with access to the store directory or once there to have caused an unexpected/undesired action.

All depends on how you want to have things set up.

Since i am not expecting a ton of visitors from Google in the storetest, maybe i could set it to be "normal", but i'd just put it in maintenance mode so i could work on it as a normal site.

On the "root" file, it has these lines that are not in the /storetest/ one:

RewriteCond %{QUERY_STRING} base64_encode.*\(.*\) [OR]
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} (\<|%3C).*iframe.*(\>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
RewriteRule ^(.*)$ index_error.php [F,L]
RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)

and

order allow,deny
deny from 80.82.78.57
allow from all 

So what would be the process to get a "live" store that i can put in maintenance mode and work as if it were the live one?

The information in your root htaccess (provided at the end of the previous post) offers some security for your site in the first "batch", the second one denies access to the site for a specific ip address. I haven't looked up to what that address belongs, but it's there.

Removal of the htaccess (by renaming or removing from the server) from the storetest directory will restore access to the site. The password has more than likely expired for the admin account(s) for that store which would still allow attempt to access if you recall it, or otherwise require "reset" by way of: http://www.zen-cart.com/content.php?44

mc12345678:

The information in your root htaccess (provided at the end of the previous post) offers some security for your site in the first "batch", the second one denies access to the site for a specific ip address. I haven't looked up to what that address belongs, but it's there.

Removal of the htaccess (by renaming or removing from the server) from the storetest directory will restore access to the site. The password has more than likely expired for the admin account(s) for that store which would still allow attempt to access if you recall it, or otherwise require "reset" by way of: http://www.zen-cart.com/content.php?44

I just renamed the .htaccess file to _.htaccess and now, it does not even display the store (test):
http://creationcassel.com/storetest/

I didn't change anything else. Am i missing a file somewhere?
Before it was locked on me, it was readily accessible.

CaroleAs:

I just renamed the .htaccess file to _.htaccess and now, it does not even display the store (test):
http://creationcassel.com/storetest/

I didn't change anything else. Am i missing a file somewhere?
Before it was locked on me, it was readily accessible.
Don't know if you put it back or because of cache on my device, but when I attempted to go to the link I was redirected to your main store. If it wasn't put back, then two things. Power of the 301 redirect is at play and/or as always when get a blank or partial blank screen: http://www.zen-cart.com/content.php?124-blank-page

mc12345678:

Don't know if you put it back or because of cache on my device, but when I attempted to go to the link I was redirected to your main store. If it wasn't put back, then two things. Power of the 301 redirect is at play and/or as always when get a blank or partial blank screen: http://www.zen-cart.com/content.php?124-blank-page

It loads this for me:
Hello. Thank you for loading Zen Cart®.

You are seeing this page for one or more reasons:
...

I found part of the problem. The config files for this cloned store were never changed (obviously, it was locked), but the whole store was somehow, transfered when i changed host, so the DB info was incorrect, the path was incorrect, etc. I fixed that on both config files BUT, i have no clue what the DB_SERVER_PASSWORD is (obviously, it is not correct). So i am trying to figure out where it is or how i can change it.

CaroleAs:

It loads this for me:
Hello. Thank you for loading Zen Cart®.

You are seeing this page for one or more reasons:
...

I found part of the problem. The config files for this cloned store were never changed (obviously, it was locked), but the whole store was somehow, transfered when i changed host, so the DB info was incorrect, the path was incorrect, etc. I fixed that on both config files BUT, i have no clue what the DB_SERVER_PASSWORD is (obviously, it is not correct). So i am trying to figure out where it is or how i can change it.
Actually from "our" perspective (viewers of this forum thread) the information provided from that message does not suggest anything directly obvious other than that there is some error in the installation. The details that are provided towards the bottom of that message are what give the clues needed to the reader.

Of course you're familiar with your own sites history so you can fill in the blanks, but providing just the top of that message does not give a lot of detail to the inquiring minds. :)

As to database access, well if the database actually did survive the/a move, you could always establish/re-establish credentials for that particular database. Be careful though, because you may have assigned the same user to have access say as your live site, and if you go and modify the password to work on your test site it may prevent access to your live site (unknowingly), so check the facts and/or create a new user with credentials, etc... keep your live site chugging as much as you can.