User tracking mod

[TamyA]

In ZC 1.5.5, there is no additional action for the catalog side (ie. do not have to do anything to add $zco_notifier->notify('NOTIFY_FOOTER_END', $current_page_base); which is located in includes/templates/template_default/common/tpl_main_page.php and includes/templates/responsive_classic/common/tpl_main_page.php

As to User Tracking Config, that feature is added as part of the installation which generates configuration options to be selected from the configuration menu. As stated in a thread where installation appeared to occur continuously the install files need to be installed in their correct location (and also not in their incorrect location) to be able to perform the installation one time and one time only... Again, request to verify that the files located within the YOUR_ADMIN directory are not also duplicated to the catalog side.

For example, the following files should not be found on the catalog side:
includes/auto_loaders/config.user_tracking_install.php
includes/init_includes/init_user_tracking.php
includes/languages/english/user_tracking.php
includes/languages/english/extra_definitions/user_tracking.php
Also, the following files should be removed from the admin side of the store if a previous version had been installed. In particular if the server does not support/allow unlinking (deleting) files by code. The most recent
version does not include code files that were previously included as the code has been moved into other areas. Which if this is/was a fresh install of ZC with a fresh install of User tracking (no database entries existing from a previous version), then the only database related action of the version install would be to update the version number and none of the actions in the 1.5.8.php version file would be executed.

So more specifically: admin/init_includes/init_user_tracking.php initiates the install process and then it is in the version 1.5.3 installer where the configuration menu is first installed and it is then edited as necessary in later versions.

I just downloaded the plugin again, unzipped it, change
"YOURADMIN" to my admin Directory name, Dragged the 2 folders (includes and admin) to the root of my store and the same result again.

Also i got some extra this time and these will load on top of the admin page unless i delete the files from Admin/includes/installers/user_tracking/*.*

Updated sort order configuration for User Tracking

Installed User Tracking v1.5.3

Installed User Tracking v1.5.4

Installed User Tracking v1.5.5

Installed User Tracking v1.5.6

Installed User Tracking v1.5.7

Installed User Tracking v1.5.8

[mc12345678]

I just downloaded the plugin again, unzipped it, change
"YOURADMIN" to my admin Directory name, Dragged the 2 folders (includes and admin) to the root of my store and the same result again.

Also i got some extra this time and these will load on top of the admin page unless i delete the files from Admin/includes/installers/user_tracking/*.*

Updated sort order configuration for User Tracking

Installed User Tracking v1.5.3

Installed User Tracking v1.5.4

Installed User Tracking v1.5.5

Installed User Tracking v1.5.6

Installed User Tracking v1.5.7

Installed User Tracking v1.5.8

Ok, so let's go a little more systematically.

Please identify all of the files located in the following directories:
catalog/includes/auto_loaders
catalog/init_includes

I just installed it on a ZC 1.5.5a site, received an initial report upon first admin navigation, but did not receive any further user tracking notifications.

[TamyA]

Problem Solved.

I uninstalled the database configuration using the SQL provided with the mod and installed again. Thanks.

[mc12345678]

Problem Solved.

I uninstalled the database configuration using the SQL provided with the mod and installed again. Thanks.

Unfortunately, some of the earlier installation process steps had a tendency to leave behind some remnants that could get in the way of an upgrade install where it may not have been realized to be an upgrade... ie. if the software had previously been installed or attempted to be installed to the database, but then not fully removed (even if the removal instruction of the time were followed). Happens and why it is part of the instructions when problems have been identified with installation and why it was suggested in the previous referenced thread.