Crazy/dangerous idea... Problems with upgrading

[mallabik]

Thanks for the quick responses everyone, really appreciate that.

To start off, the exported file is the same size as database listed on the cpanel. Yesterday through my hours of reading, I read that the .sql file would be a file with a ton of text that doesn't make much sense to humans but is in plain text that can be parsed and put back into tables.Yesterday, I looked into that file because I was curious and it is readable text and there is a lot of it, about 7 MB of data... so I hope it was exported fine.

I followed the steps outlined by DrByte in one of the many posts I read about the database procedure. I just can't find the link as I type this message out.

I will try to use the copy function, but I will have to try the "create database" option because I deleted the v1.5.4 database to test the import function.

[DrByte]

..., but I will have to try the "create database" option because I deleted the v1.5.4 database to test the import function.

You can re-create the test database the same way you did previously using your hosting service control panel.

[mallabik]

A couple of observations from the last few days.

The copy database feature from the myphpadmin worked in duplicating the "live" (old 1.3.9h) database to the "demo" (1.5.4) database. (I deleted the original 1.5.4 store database so it didn't have any tables to get confused with). I did notice that when I copied the zc_install directory onto the demo file structure and tried to run the "update database" only button it kept asking for the admin password which is were I ran into issues.

The newly created "demo" (1.5.4) admin password did not work. I tried it many times and actually deleted and re-installed the demo site and process twice in case I was getting the password wrong. I then realized that it may have been asking for the old admin password because I copied the old database over to the new 1.5.4 database.

I tried the old admin password and sure enough it worked. I did get a couple of errors I am hoping aren't a huge ideal and they won't impact the process.

SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist.
SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist.
SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists.
SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.

I'm going to take everyone's advice this time and *not* mess with the master template and just install template found in the download section of this site. Once I have the new template working to my liking I have one and final question...

I read in several threads that if I rename the old store /includes and /admin/includes to includes_139 and /admin/includes_139 copy the demo /includes and /admin/includes to the root of the store (in theory moving the demo store to the live store). I should have a working copy of the new store from the old store location? Correct?

The reason why I ask, I noticed none of the product images were working because the paths in the database are off by one level. I'm just hoping that moving the new template /includes and /admin/includes doesn't mess anything else.

I will have to re-configure the paypal module, but that's expected with any 1.5.4 installation.

[mc12345678]

I tried the old admin password and sure enough it worked. I did get a couple of errors I am hoping aren't a huge ideal and they won't impact the process.

SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist.
SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist.
SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists.
SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.

I'm going to take everyone's advice this time and *not* mess with the master template and just install template found in the download section of this site. Once I have the new template working to my liking I have one and final question...

I read in several threads that if I rename the old store /includes and /admin/includes to includes_139 and /admin/includes_139 copy the demo /includes and /admin/includes to the root of the store (in theory moving the demo store to the live store). I should have a working copy of the new store from the old store location? Correct?

The reason why I ask, I noticed none of the product images were working because the paths in the database are off by one level. I'm just hoping that moving the new template /includes and /admin/includes doesn't mess anything else.

I will have to re-configure the paypal module, but that's expected with any 1.5.4 installation.

Username and password is tied to the database, old database, old credentials. Glad you figured that out.

Those messages are not errors. They provide information about what action(s) were attempted but not performed.

Yes, ideally leave the classic directory and template_default directory as they are. It will certainly make things easier in the future.

I believe I saw the same suggestion about moving the store(s), but I would think that the admin directory should be the one renamed not the includes folder inside of it. (There are other folders inside the admin directory besides the includes folder.)

As to the image offset, the database locations are based off of the DIR_WS_IMAGES constant defined in the includes/configure.php file. So if your previous structure was images/images/imagefile.jpg then that same structure would be expected to exist in the new store. The database would reflect images/imagefile.jpg most likely, but could also reflect just imagefile.jpg if the depending on the define of the applicable configure.php file.

So in short with that, moving the store will not resolve that issue and in fact should be resolved before moving the store. Otherwise how will you know what caused the problem?

[mallabik]

Thanks MC for the quick response, love the support everyone here in this community gives.

I should have clarified, I would like to move the new 1.5.4 /includes folder and the /admin folder (not just the /admin/includes) I should have made that more clear. so that I can keep the same links from the rest of the site. I will be doing a major overhaul of the entire website which is why I am looking to move the new store files to the original location so I can keep many of the links the same.

[mallabik]

Hm... what a strange setting... I can only edit my posts up to 7 minutes of posting :)

Once I get the templates working as I wish, I guess I can always copy the 1.5.4 folders with new names to the live store, rename the old /includes and /admin directories to temp directories copy the 1.5.4 folders and see how everything works. I just need to do a bit of research for 1.5.4 captcha and the ability to download files on the new platform. I think the worst is past, unless those skipped actions are cause for concern.

[mallabik]

It's been a few days since I was able to work on the site. You're tips have been really helpful and the site is almost up and running.

I've got the admin side working (or at least it seems to be) after renaming the old admin/ folder to admin_139/ and copying the 1.5.4. admin/ to the root location. I say "I believe" because on the admin side, all of the links are pointing to the right location and they work when I click on them.

One thing I noticed is if I try and use the 1.5.4 configure.php and use the demo location ie /store/v2 everything works. If I rename the store locations inside the 1.5.4 configure.php to /store/ and /store where application. It gives me the "You are seeing this for several reasons" message.

If I use the 1.3.9 configure.php everything seems to work. The links on the home page, images everything points back to /store and it seems ok. Should I be concerned that I have to use 1.3.9 configure.php?