Closed (fixed)
Project:
Simplenews Statistics
Version:
6.x-1.1
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 Feb 2009 at 12:00 UTC
Updated:
25 Mar 2009 at 08:00 UTC
Hi,
I have installed the latest version of Simplenews and simplenews Statistics module on Drupla 6 and created a few newsletter issues and sent them.
However the statistics table is showing no newsletters all the time.
I have made sure cron is unchecked and my newsletters are being sent when i save the pages.
The newsletters are coming fine to my email addresses as well.
Can you anyone help if they had similar problems before.
Comments
Comment #1
danielkorte commentedThe problem may have to do with what was brought up here. At least it seemed to work for me.
Here is what you do:
1) Uncheck the module from admin/build/modules and hit 'Save Configuration'
2) Run cron if it asks you to (if it doesn't, run cron anyway)
3) Go to admin/build/modules/uninstall and uninstall 'Simplenews Statistics' (THIS IS VERY IMPORTANT, BECAUSE YOU NEED TO EMPTY THE DATABASE TABLES ASSOCIATED WITH SIMPLENEWS STATISTICS)
4) Then you are going to have to change the file 'simplenews_statistics.install' on line 19, line 47, and line 81 from 'size' => 'tiny', to 'size' => 'normal',
5) Then make sure that install file replaces the old install file on your server then reinstall it through drupal in admin/build/modules
This worked for me! Hope it does for you to.
The reason is, as the fore-mentioned post points out, that the size 'tiny' only goes up to 127. So when your node number exceeds that it is unable to write to the database properly. If you check your admin/reports/dblog you probably were getting errors along the lines of "Duplicate entry '127' for key 1 query: INSERT INTO simplenews_statistics (nid, send) VALUES (479, 1) in /public_html/drupal/sites/all/modules/simplenews_statistics/simplenews_statistics.module on line 110."
Comment #2
Docc commentedThis could be the problem. Does Drupal logs any errors? try the fix in #1 or wait for the next dev version
Comment #3
brei9000 commentedThis fixed the issue for me. Thanks danielkorte!
Comment #4
Docc commented