When running zc_install appears not to have upgraded

RAD1964:

So I am using the new admin folder because it may contain updated files, I made sure in both config files to point the paths to the new shopping folder and the paths to the admin without it being renamed.

I am now getting an Internal Server Error 500 when I try to connect to the store and the admin.

The admin path inside of the admin/includes/configure.php file should be autogenerated, don't have to provide/type in the path for the admin path. Still required to identify the path to the store side in both configure.php files. Further, if you are going to provide a paath for the admin directory, then the files need to exist in that directory.

The thing is though, in order to perform the zc_install process, the admin directory must be named admin and it would be highly advisable that the admin configure.php have all of the proper references to where files are stored and the uri associated with getting to the directory as well as to be able to get to the store.

so because I may have added a path to the admin, would that negate the update process I did? Or can I remove the that path and it will auto-generate?! Should I start the entire process over?

I still have template upgrades to do as well :(

THANKS for your time,

Robert

Can I change line #29 define.. back to** /path** from the /shopping2/admin I entered in the admin/imcludes/configure.php file. I say back to because that is what the dist-configure.php file had in it from version 1.5.3.

RAD1964:

so because I may have added a path to the admin, would that negate the update process I did? Or can I remove the that path and it will auto-generate?! Should I start the entire process over?

I still have template upgrades to do as well :(

THANKS for your time,

Robert

Sorry for the delay in responding. What would help make things a little easier to diagnose would beif you could post your configure.php files, but if there is a direct assignment to your admin path to do something so that no one knows your path to your secret admin AND do something to obscure your database information. If you were able to successfully update the database before, good... Database taken care of, now to get/keep the files working so that the store can process things.

I have a lesson learned also. I was corrected in an alternate thread that if all that is desired to be done (and one is doing) then the directory that contains admin files does not need to be renamed to admin for a database only upgrade... Sorry. That's only necessary for upgrading the configure.php files and to basically reset the database to a blank state.

So, if now the problem is accessing the store from the web, more than likely there are errors in the configure.php file(s) or the host is having an issue. There may also be something in the .htaccess, but I didn't review back to the first page to identify if that has been discussed yet.

Am I correct though that you received a satisfactory notification of upgrading the database?

RAD1964:

Can I change line #29 define.. back to** /path** from the /shopping2/admin I entered in the admin/imcludes/configure.php file. I say back to because that is what the dist-configure.php file had in it from version 1.5.3.

The dist-configure.php file is a generic file and shows the general format expected for the new file (ie. In your case with an upgrade from 1.3.x) so that the specifics of say path are filled in. In the admins configure.php file there should notbe any readable text that identifies what path it actually is in. Everything is "coded" and designed to figure out where the file(s) are. So all of that path information should end up matching what is in the includes/configure.php say for the cache directory, etc... There are different constants defined in the admin configure.php file, but there are others that are the same name, etc...

Path information for the constants that have FS in them should be available through your cPanel and typically include up to public_html. If the store is then in a subdirectory then the subdirectory should be added as identified in the example(s) of the dist-configure.php file.

Help at all?

I am starting over again in the upgrade process.. my host states that files are corrupted (Their catch-all phrase when they can't figure something out.)

So the first issue I see is when I moved a copy of my 1.3.8 zencart to my root (nothing was there prior) is that I renamed my admin back to admin for the upgrade, but can not connect to the admin using the conventional /admin/index.php I changed both config files to point to the /admin/ what gives?!

RAD1964:

So the first issue I see is when I moved a copy of my 1.3.8 zencart to my root (nothing was there prior) is that I renamed my admin back to admin for the upgrade, but can not connect to the admin using the conventional /admin/index.php I changed both config files to point to the /admin/ what gives?!

ZC is written to only allow access to the admin content when the folder is renamed as something other than admin, but uses the admin folder to do "initial" setup

If. Doing a database only upgrade using zc_install, that does not need to know all of the same details so the admin folder can remain "secret".

Take a look at this thread for rebuild steps: http://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading

RAD1964:

So the first issue I see is when I moved a copy of my 1.3.8 zencart to my root (nothing was there prior) is that I renamed my admin back to admin for the upgrade, but can not connect to the admin using the conventional /admin/index.php I changed both config files to point to the /admin/ what gives?!

Wait... Both configure.php files point to admin???? Only the admin/includes/configure.php file should have any reference to the admin directory assuming that the /admin directory only contains admin files and not the ZC store... Ie, store is accessed via URI, while admin is expected to be accessed via URI/admin.

Under newer coding there should be nothing that can be seen with the eye in the admin/includes/configure.php file that shows the path to the admin directory... A configure.php file created under ZC 1.5.3 (any after 1.5.0) has a calculated admin path not a typed in path to the admin directory.

I think you misread my comment or I didn't make myself clear.

I started over in the process, wiped out the shopping2/ folder which had both sets of 1.38 and the 1.5.3 overwritten. But they are gone. I made a new database with my most recent 1.3.8 backup.

all I did was move a working 1.3.8 from htdocs/shopping/ to htdocs/

and then renamed the admin to admin

and then changed my 2 config files to point to the new database and to use the "admin" and not "jdbhwuc764bhdjk"

So fuuny me, I expect the admin to work since no update has yet been done, only a move to one directory below what it was. (Now the root)

So because 1.3.8 admin/includes/configuration.php had paths to admin in it, I changed them to reference a un-renamed admin folder. (/admin/)

On defines that do use admin in 1.3.8,

I do this:

define('DIR_WS_ADMIN', '/admin/');
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_ADMIN', '/admin/');
define('DIR_WS_HTTPS_CATALOG', '/');

Why is the admin not working, all I did was rename the admin to admin?! 1.3.8 still :(

A little of both. :)

Okay, so at least under newer versions, the admin directory won't work if it is actually called admin. A side note, if the "garbled" directory for the admin still exists for the currently functional site, it should be renamed asap with new admin directories/includes/configure.php updated to reflect the new location.

But, back to the directory move version, the store's (root)/includes/configure.php file has also been updated to remove the subdirectory that was present?

Also, have you verified that the constants thatinclude FS have been modified and end with or without the appropriate /?

Yes the includes/configures.php has this line:

define('DIR_FS_CATALOG', '/home/users/web/XXXX/pow.phylisjo/htdocs/');

I have not changed this line at all (because I removed the 'pointer' which used a subdomain shopping/ as the store)

and in the admin/includes/configuration.php I have..

define('DIR_FS_ADMIN', '/home/users/web/XXXX/pow.phylisjo/htdocs/admin/');
define('DIR_FS_CATALOG', '/home/users/web/XXXX/pow.phylisjo/htdocs/');

define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');
define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');
define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');
define('DIR_FS_CATALOG_TEMPLATES', DIR_FS_CATALOG . 'includes/templates/');
define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');
define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');
define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

Has the fix_cache_key utility been run since the move of the files? (http://www.zen-cart.com/downloads.php?do=file&id=8 (fix_cache_key utility))

Keep saying the admin is not working, but the store side is? Php issues possibly? Sorta have to guess what's going on based on what has been presented and assuming that it still works for the location it was in before both moves (up one directory for the store and a new folder name for the admin.)

<p> I just ran the cache fix, deleted the file after it ran and said it had synched my location. But.. admin does not show still :( Yes I can still pull up the admin/index.php log in page on the original shopping/ folder still. Since relocating the installation to the root (or /htdocs/) the following (below) are my paths to the "catalog".. are they correct?</p> <p> <strong><span style="font-size:2;">define('DIR_WS_CATALOG', '/'); define('DIR_WS_HTTPS_CATALOG', '/');</span></strong></p>

define('DIR_WS_CATALOG', '/'); define('DIR_WS_HTTPS_CATALOG', '/');

I'm going to humbly suggest that you are doing what many of us did on first arrival to the Zen Cart family.
"I'm a ##########___ (fill in here Developer, Programmer, Designer, Etc), I can just jump in here with both feet and get this done."
Several will agree with me that this only leads to :frusty:
Your are upset with the instructions yet you seem to be jumping around doing things that, unfortunately, are just making matters worse. Been there, done that.
You've got to go step by step and make some starting decisions based on the fact that you are using 1.3.8. It's VERY old and hackable. Most mods that worked in 1.38 will NOT work in 1.5.3. You will need to decide which ones you really need for 1.5.3 and determine their currency. If not available, you will have to make something else work or just drop the mod. That's step a) of http://www.zen-cart.com/entry.php?3-How-do-I-rebuild-my-site-on-the-new-version-instead-of-upgrading rebuild method which is, IMHO, your best bet.
Here's what I would do in your case.
Load a copy of the latest hotfix zip to your site's root.
Create a new database for the rebuild. ZC will populate it for you during installation. NOTE: the new database prefix should match any prefix in the old database.
Extract the hotfix zip to the root and rename that directory to test.
Run yoursite.com/test/zc_install to zencart and populate the database.
DO NOT drop the zc_install directory or rename the admin just yet.
If not already done, I would go to the admin of the 1.3.8 and set it Down for Maintenance.
Delete the tables from the 1.5.3 database and insert the tables from the 1.3.8 database.
Run yoursite.com/test/zc_install and select update the database. It will ask for the admin password. That is the admin from the 1.3.8 database that you inserted.
When done, you may see some skip or ignore notices. They can be ignored.
NOW you can delete the zc_install directory and rename the admin to something of your choosing.

NOTE: Never during any of this did I mention either configure.php file. They are designed to be created and take care of themselves during installation!

The only things you will need from your old installation are the define_page files and images (product, etc) from the old site.

At this point, you have an ugly, operational cart that has no shipping or payment modules. Put the shipping and paying in place and start thinking about a mods. Zen Cart is browser/search engine ready out of the box so, for speed in getting back to work, use the minimum mods. You just have to have to make it work your way.

Next, get rid of the ugly. A new template is in order. With today's tablets and smart phones, look at something that's responsive. It will give you a step up on the competition.

When you are happy with the basic operation/look of the site, head back to your site's file manager and compress the root directory into a zip (don't include the test directory). Essentially this is a backup just in case it's needed. Delete all the old 1.3.8 files and copy the files in the test directory to the root. NOW YOU ARE GOING TO NEED TO CHANGE BOTH CONFIG FILES UNDER THE ROOT TO REMOVE THE /test REFERENCE. About four to five places in each one.

You now have two working 1.5.3 ZC shops pointing to the same database. If you want to continue using the /test directory for development, copy the 1.5.3 database to another (use the same username and password) and put the name of the new database in the two configure.php files inside the /test directory. You now have an operational shop in the root and a operational test site in /test. Time to PLAY!

Most of this can be done in less time than it took me to type it. AND... I would not have done so had you not mentioned your qualifications. I would not avoid the steps in the link above for most folks. I believe you're going to have those "I can do this" moments that get you in trouble.

EXTRA NOTE: Can't think of a single time that ZC has caused a 500 error. Those are problems on the server.
No one has brought this up yet, BUT, since you are running 1.3.8....Is your server ready for 1.5.3? http://www.zen-cart.com/content.php?48-what-are-the-server-requirements-to-run-zen-cart

Hang in there, try not to read into things, stay on track and let us know when you have a question.:yes:

<p> I figured, if I can move my store from a subfolder to the root, I can implement an upgrade and a responsive template. I can't even move a working store... Now I have actual error messages for the admin: </p> <p> **Warning**: include(includes/auto_loaders/config.core.php) [[function.include](http://www.shimmys.net/admin/function.include)]: failed to open stream: No such file or directory in **/hermes/waloraweb003/xxxx/pow.phylisjo/htdocs/admin/includes/initsystem.php** on line **21**<br /> <br /> **Warning**: include() [[function.include](http://www.shimmys.net/admin/function.include)]: Failed opening 'includes/auto_loaders/config.core.php' for inclusion (include_path='.:/usr/local/lib/php-5.2.17/lib/php') in **/hermes/waloraweb003/xxxx/pow.phylisjo/htdocs/admin/includes/initsystem.php** on line **21**<br /> <br /> **Warning**: dir(includes/auto_loaders) [[function.dir](http://www.shimmys.net/admin/function.dir)]: failed to open dir: No such file or directory in **/hermes/waloraweb003/xxxx/pow.phylisjo/htdocs/admin/includes/initsystem.php** on line **22** **Fatal error**: Call to undefined function zen_get_languages() in **/hermes/waloraweb003/xxxx/pow.phylisjo/htdocs/admin/includes/header.php** on line **18**</p> <p>  </p> <p> If it's easy (yeah right) I would love to trouble shoot this, if, however it is as conveluted as the upgrade process, I will start from the beginning, yet again, this time installing 1.5.3, truncating the database and loading in 1.3.8 database... Only one question regarding your instructions, were you say: Delete the tables from the 1.5.3 database and insert the tables from the 1.3.8 database. Since I have a SQL dump, I am guessing that contains header rows etc., will I need a different dump or can I still use the sql dump?</p>

Well, decided to go at a 1.5.3 install route..

<p> Created new install of 1.5.3, new database, all green checks on php.ini, path to admin has the Warning about renaming the admin and deleting the zc_install folder so that seems to be working, however, The store URL shimmys.net is giving a 404 error, I let the host know.</p> <p> I did choose to install the demo store data...</p> <p> Robert</p>