One-Page Checkout [Support Thread]

[jpda]

@jpda, are there any debug-logs being generated? I'm wondering if (somehow) the DIR_FS_LOGS definition got mangled during the upgrade.

After updating/merging the 1.5.5f file system files, I tried to run zc_install to update the db, knowing there were none. I coul not complete zc_install because it only offered me to create a new database, so I quitted zc_install. However, it had produced several zcInstallLog_*.log files in the logs directory. In configure.php no explicit define('DIR_FS_LOGS' ...) because optional in store and admin.

jpda

[jpda]

After updating/merging the 1.5.5f file system files, I tried to run zc_install to update the db, knowing there were none. I coul not complete zc_install because it only offered me to create a new database, so I quitted zc_install. However, it had produced several zcInstallLog_*.log files in the logs directory. In configure.php no explicit define('DIR_FS_LOGS' ...) because optional in store and admin.

jpda

Anyway, I did check the local versions of configure.php, of course. No explicit defines for DIR_FS_LOGS, but I added them and now I do get myDEBUG logs AND also from OPC!
Thus, I checked the configure.php files from the original site and they do have those explicit DIR_FS_LOGS defines (probably because that site had been upgraded from zc 1.5.4 to zc 1.5.5e.
Question now is: Why does ZC tell me those defines are optional?

Cheers,

jpda

[lat9]

Woo-hoo! I'm glad you got the issue sorted. Those /includes/local/configure.php files can be "tricky" on an upgrade.

Zen Cart 1.5.5 (and later) split the DIR_FS_LOGS (and other definitions) out to /includes/defined_paths.php since the majority of the file-locations are simple derivatives of DIR_FS_CATALOG. That's why the definition is documented as "optional".

[jpda]

Woo-hoo! I'm glad you got the issue sorted. Those /includes/local/configure.php files can be "tricky" on an upgrade.

Zen Cart 1.5.5 (and later) split the DIR_FS_LOGS (and other definitions) out to /includes/defined_paths.php since the majority of the file-locations are simple derivatives of DIR_FS_CATALOG. That's why the definition is documented as "optional".

Thanks a lot for your help and explanation!

Cheers,

jpda

[jpda]

Woo-hoo! I'm glad you got the issue sorted. Those /includes/local/configure.php files can be "tricky" on an upgrade.

Zen Cart 1.5.5 (and later) split the DIR_FS_LOGS (and other definitions) out to /includes/defined_paths.php since the majority of the file-locations are simple derivatives of DIR_FS_CATALOG. That's why the definition is documented as "optional".

Do you mean that defined_paths.php is ignored when reading local configure.php? Because in the local configure.php's DIR_FS_CATALOG has been defined correctly...

jpda

[lat9]

Do you mean that defined_paths.php is ignored when reading local configure.php? Because in the local configure.php's DIR_FS_CATALOG has been defined correctly...

jpda

Nope, the defined_paths.php will supply the DIR_FS_LOGS definition by extending DIR_FS_CATALOG if that definition doesn't already exist ... which it did!

[jpda]

Nope, the defined_paths.php will supply the DIR_FS_LOGS definition by extending DIR_FS_CATALOG if that definition doesn't already exist ... which it did!

Thanks again, I will check things again and report back because I think the DIR_FS_CATALOG existed and DIR_FS_LOGS was not explicitly defined in local configure.php. No log files were written at that point in time. They appeared again after I had explicitly defined DIR_FS_LOGS in the local configue.php

Cheers,

jpda

[jpda]

Thanks again, I will check things again and report back because I think the DIR_FS_CATALOG existed and DIR_FS_LOGS was not explicitly defined in local configure.php. No log files were written at that point in time. They appeared again after I had explicitly defined DIR_FS_LOGS in the local configue.php

Have checked it again.
Removed both local directories and put both local configure.php files in their 'normal' directories (/includes/ and /admin/includes/, w/o explicit defines for logs. Thus forcing reading of these configure files.
Result: both debug logs were written.

Restored both local directories, put both local configure.php files in those local directories (/includes/local/ and /admin/includes/local/), w/o explicit defines for logs
And:
Restored both original configure.php files from the live site into their 'normal' directories (/includes/ and /admin/includes/).
Result: no log files!

Extra check: when I remove all configure.php files from /includes/ and /admin/includes/, leaving the local versions w/o explicit defines for logs, then debug logs will be written!

Conclusion?

Cheers,

jpda