V1.5.5a - do not see my data

Hi

Just downloaded V1.5.5a. Ran Zcinstall, everything OK in my Xampp PC test site.
Only problem is I do not see my data after logging into V1.5.5a, see screenshot.
I had linked to a back up version of my DB which has ca. 3 years data. I understand the zcinstall updates the db structure?

When I click on "storefront" in V1.5.5a I see a ZC screen with "Congratulations! You have successfully installed your Zen Cart® E-Commerce Solution."

I have not changed or added anything to the V1.5.5a code, except I did download my images.

I have a v1.5.4 test site on my PC (never got around to porting to my live site) so today I linked to the same db version I used for V1.5.5a and v1.5.4 works as expected.

Any suggestions welcomed.

Suggest checking all of the DB_ related entries in the includes/configure.php files paying particular attention to DB_PREFIX.

mc12345678:

Suggest checking all of the DB_ related entries in the includes/configure.php files paying particular attention to DB_PREFIX.

Thanks, did check both v155a config files and they are identical to the v154 files. I do not use DBprefix.

Out of interest I changed the DB passwords in the DBs and in the config files- same result; 154 is OK and 155a is not.

Would I be able to log into 155a if there was no DB connection? I thought the login info is held in the ZC DB?

marton_1:

Thanks, did check both v155a config files and they are identical to the v154 files. I do not use DBprefix.

Out of interest I changed the DB passwords in the DBs and in the config files- same result; 154 is OK and 155a is not.

Would I be able to log into 155a if there was no DB connection? I thought the login info is held in the ZC DB?

The login information is contained in the database, but the admin side is controlled by admin/includes/configure.php where the store is controlled by includes/configure.php. So in the case of comparing two versions of ZC to each other, at least the two 1.5.5 files should be compared with each other as well as either of those files to your 1.5.4 version. Seeing as the image above is related to the admin, the admin versions should be compared.

An additional location to check is the admin/includes/local directory for any files that provide an alternate DB_ arrangement. As shown above, it appears that the database referenced by your 1.5.5 store (store side/admin side) is referencing an empty database which would be expected for a newly installed store before changing reference to a different database or importing a database to the one referenced by 1.5.5.

mc12345678:

The login information is contained in the database, but the admin side is controlled by admin/includes/configure.php where the store is controlled by includes/configure.php. So in the case of comparing two versions of ZC to each other, at least the two 1.5.5 files should be compared with each other as well as either of those files to your 1.5.4 version. Seeing as the image above is related to the admin, the admin versions should be compared.

An additional location to check is the admin/includes/local directory for any files that provide an alternate DB_ arrangement. As shown above, it appears that the database referenced by your 1.5.5 store (store side/admin side) is referencing an empty database which would be expected for a newly installed store before changing reference to a different database or importing a database to the one referenced by 1.5.5.

Great thanks.

Obvious when I think about it. :smartalec:

I checked and my 155 DB is empty! It has all the correct tables but the tables are empty! But why?

For both 154 and 155 I created a new DB and imported my latest back up. 154 is correctly populated.

Xampp reported the DB imports were OK.

zc install finished OK

I will start again from the beginning (reinstall the 155 download in my test folder, create a new DB and import, after import I will check the tables are populated :smile:, then run zc install) check the result and report back.

Well, if the actions were in the sequence described above, then the database tables are empty because after the import of the database zc_install was first run without requesting or being offered a database upgrade. If the database was now imported, things should be different and zc_install would need to be run to do the database upgrade...

mc12345678:

Well, if the actions were in the sequence described above, then the database tables are empty because after the import of the database zc_install was first run without requesting or being offered a database upgrade. If the database was now imported, things should be different and zc_install would need to be run to do the database upgrade...

Thanks for your patience!
Yes, many thanks - I reinstalled zc_install, imported the DB ran database upgrade and the DB is OK.

Now I cannot login because it is looking for the German language add-on. As mentioned I just installed the vanilla 155a without any addons/plugins.
In v154 this was a PHP warning. In v155a it is a PHP fatal error, see below(false admin name). I hope there is something I can change in the DB to lock English in?
I tried changing the priorities (see below) to select English but no luck!

PHP Fatal error:  require(): Failed opening required 'includes/languages/german.php' (include_path='.;C:\xampp\php\PEAR') in C:\xampp\htdocs\zencart155\adminxxxxxxx\includes\init_includes\init_languages.php on line 35

Four "micro" solutions come to mind:

1. Install the German language pack. (most suggested)
2. Duplicate english.php to german.php
3. Change the folder name of German to English in the database record.
4. Backup the database and then delete the entry for German. (likely to cause a bloated database issue as other German entries likely exist. This is least preferred method.)

mc12345678:

Four "micro" solutions come to mind:

1. Install the German language pack. (most suggested)
2. Duplicate english.php to german.php
3. Change the folder name of German to English in the database record.
4. Backup the database and then delete the entry for German. (likely to cause a bloated database issue as other German entries likely exist. This is least preferred method.)

Thanks, as I feared; no solution without work for a lazy guy like me :smile:

marton_1:

Thanks, as I feared; no solution without work for a lazy guy like me :smile:

Well, now that have looked at the code for that area, if you included the following on the url path for your admin login, it may let you in?!

?language=en

If there is already a ? in the url, then use:
&language=en

You could also perform some "database surgery" using phpMyAdmin and change your default language to English until you get that German language pack loaded:

UPDATE [B]configuration [/B]SET configuration_value = 'en' WHERE configuration_key = 'DEFAULT_LANGUAGE' LIMIT 1;

If your store is using a non-blank DB_PREFIX, you'll need to reflect that value in the name of the configuration table.

mc12345678:

Well, now that have looked at the code for that area, if you included the following on the url path for your admin login, it may let you in?!

?language=en

If there is already a ? in the url, then use:
&language=en

:oops:

Darn it, I did the work and installed the German add-on (which works fine now) and then saw your solutions.

Thanks again

:bow:

marton_1:

:oops:

Darn it, I did the work and installed the German add-on (which works fine now) and then saw your solutions.

Thanks again

:bow:

You're all the better off for it... Installing/reinstalling the German add-on is better in the long run anyways. Now if you no longer want/need the German part, using ZC to remove the language would be "better" than surgically removing related information. Temporary fixes while good to get out of a bind do not solve the overall problem and the longer one lives with patches, the harder things will eventually fall. :)

But, glad that you were able to get off your lazy backside and solve it. :P :cheers:

mc12345678:

You're all the better off for it... Installing/reinstalling the German add-on is better in the long run anyways. Now if you no longer want/need the German part, using ZC to remove the language would be "better" than surgically removing related information. Temporary fixes while good to get out of a bind do not solve the overall problem and the longer one lives with patches, the harder things will eventually fall. :)

But, glad that you were able to get off your lazy backside and solve it. :P :cheers:

Hallelujah!!

:D :cheers:

Relaxing on my lazy backside with a nice Argentian Malbec

Now I just have to migrate the other 30 or 40 php's I was foolish enough to modify :(