After signing on or off I sometimes get a quick PHP error. The error page goes away as it’s forwarded to the next page so I took a screenshot to capture it.
<<Execution of a query to the database failed - Duplicate entry `2137483647` for key 1 >>
SQL: INSERT INTO `modx`.modx_log_hosts(id, data) VALUES(’3197491101’, ’my.cablemodmem.address.com’)
Parser timing... 16 Requests
Here’s the code, which I took from the included example blog code. I haven’t modified the snippet or chunk code.
[!WebLogin? &tpl=`FormLogin` &loginhomeid=`38`!]
-
MODX Staff
- 12,272 Posts
Please provide your environment details.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
☆ A M B ☆
- 24,524 Posts
That’s that CRC32 hash of the client’s hostname name being bigger than the database field for the logging will hold again.
-
MODX Staff
- 10,725 Posts
Disable resolution of hostnames in your configuration settings if you must use the internal visitor tracking features. The entire visitor tracking feature will be gone in the next release, as it simply causes too many problems, and is a distraction IMO to the core competency of MODx (i.e. Content Management). There are plenty of qualty alternatives for tracking stats on your server such as awstats, or you can easily integrate third party trackers like Mint, Slimstat, Google Analytics, etc. as others have done and described in this community, so unless you really want these local stats being tracked in your database (and having to be manually purged or archived regularly, if you get any kind of traffic), I recommend you disable the native visitor tracking in MODx.
Thanks for the quick and helpful response.
I’ve disabled tracking. I figured it would be a hit but knowing where my users are going was worth it. I’m using Google Analytics as well, but I just don’t find it as helpful as an integrated tool.
