Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!
I’ve been transferring one of our clients websites from one server to another and ever since the migration was completed Mint has stopped tracking.
I’ve followed the instructions in the sticky in the forums on how to move Mint and everything went just fine, except that Mint doesn’t track anything since it was moved :(
Could there be anything that I’ve overseen or anything that I can try to get it tracking again. All help would be mostly appreciated!
The Mint JavaScript include only appears on one (that I found) page of your site. It must be added to every page you want tracked.
That isn’t the site, please look up the site on this account starting with d. Also, everything was working just fine until I moved Mint, so I’m not sure if the issue is the mint JavaScript include tags.
When you moved Mint the mint_visit table lost its primary key or auto_increment settings. You need to use a tool like PhpMyAdmin to set the id column of any Mint-related table to primary key and auto_increment.
i moved from 32bit apache to 64 bit litespeed. now mint isn’t working anymore. i used your checksum script, which worked last time, from 32bit to 64. didn’t work this time.
what can i do? i don’t understand your last post.
here’s my mint table:
Have you run the Mint Server Compatibility Suite on the new server? I have no experience with litespeed.
i just run it. completed it successfully. this is what i guessed, since litespeed is apache interchangeable, they say, ls also supports the htaccess files from apache. this is annoying. what can i do next?
Your server is returning a “403 Forbidden” error for record requests. This is usually the result of overzealous mod_security rules. More info here.
didn’t work :-( contacted my host, maybe they can find a solution.
You must be logged in to reply. Login above or create an account
