User tracking mod

[mc12345678]

Hi,

I've been using UT since ZC v1.3x without any issues. Last month I installed it on same server for a customer that didn't have it previously and I didn't have issues (it was a ZC upgrade from 1.5.4 to 1.5.5). Now I'm installing it on an upgrade but UT was existant on previous ZC. The issue I'm having is that everything installs fine but the "User Tracking Config" stays on the "Tools" menu and it's going to a 404 page. When I insert the correct link on browser to go to the correct config page I get an incomplete module configuration (see image).

I have uninstalled the db (following your troubleshooting on readme) but doesn't fix the issue.



Your troubleshooting "7.4" mentions an alternative installation by patch but I don't see any sql file on the file set. Would you please help me?

Sorry that there remain upgrade issues with the installer. Part of its design was consideration that the software had been updated previously at least up to when I had originally stepped in and had modified the use of the configuration on the tools menu portion. I see now that definitely can not make that assumption.

Further I didn't catch removal/modification of step 7.4.

I have recently also been shown a similar setup result via PM.

My recommended solution was to use the admin/includes/installers/user_tracking/uninstall.sql file omitting the first "line" associated with drop table if exists... and perform that query as many times as necessary in a row: recommend running at least 2 times back-to-back, until the configuration menu appears in the configuration dropdown.

In working with the site, were you able to identify what version was previously installed? This would help to revise the first of the upgrade scripts to prevent reoccurrence of this issue.

For those wondering why the move of the configuration settings away from the tools menu, even though it was previously explained in this forum, basically the old script that handled the UT configuration was nearly identical to the script needed/used for the options in the configuration menu. So much so that as ZC progressed and improved on that script, similar changes were/would be necessary to the script in UT. Forgive me, but that seems like unnecessary additional work and as was discovered with the original script, lead to a potential security issue that would otherwise be corrected by the security conscience developers of ZC. Again, why reinvent the wheel and not just use what already works?