Closed (fixed)
Project:
Simplenews
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
16 Mar 2010 at 06:09 UTC
Updated:
14 May 2011 at 14:31 UTC
Jump to comment: Most recent file
G'Day,
After no configuration changes and 10 successful newsletter editions have been sent, Simple News is now emptying the simplenews_snid_tid table at each cron run and immediately before each Newsletter send action.
I can see all my subscribers still in the *_subscriptions table. So I copy them out and re-paste into Simple News Import Subscribers, with the target newsletter ticked on.
I get a successful import message. The snid_tid table is populated.
I take no action and wait for cron to run. Wtchdog reports this:
User: admin
Location:http://www.crcplantbiosecurity.com.au/node/1425/edit?destination=admin%2Fcontent%2Fnewsletters%2Fnotsent
Referrer: http://www.crcplantbiosecurity.com.au/node/1425/edit?destination=admin%2Fcontent%2Fnewsletters%2Fnotsent
Message: Newsletter subscription list was automatically regenerated.
What is going on and how can I fix it?
D5.20 / Ubuntu
Thanks,
JB
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | simplenews_743600_hook_node_access.patch | 922 bytes | simon georges |
Comments
Comment #1
boabjohn commentedContinuing:
I have installed the dev version, updated my Drupal to 5.22, and tested the database.
Every time I run cron, something emptys the simplenews_snid_tid table.
What can do this? Is it coming from the module itself? I searched for the text "regenerated" and found nothing in simplenews.module.
Desperate for a bit of help here...
Impossible to send the newsletter other than 20 at a time...when cron runs it sends the first batch, then the "subscription list auto regeneration" process runs, and dumps the list of subscribers.
End of sending.
HELP!!
Comment #2
sutharsan commentedSearch for "simplenews_snid_tid" in all code on your site but especially in simplenews_* modules. Do you use Simplenews Roles module?
Comment #3
boabjohn commentedJust a quick follow-up on this one. I disabled the simplenews_roles module and have had no further problems.
There is a note somewhere about sn_roles performing an *exact* sync between subscribers and authenticated users (with roles). Apparently sn_roles will delete every subscriber that it doesn't find an exact user match for.
In my case 80% of the subscribers *were* authenticated users with configured roles, while the other 20% were self-subscribing public users.
Not sure why sn_roles kept dumping my entire snid_tid table, since most of the users should have matched fine (indeed, I can see valid UIDs for most of the rows in the subscriptions table).
Anyway, no time to post mortem further. I have dropped sn_roles and all is good.
Thanks for the clue!
Comment #4
sutharsan commentedComment #5
sutharsan commentedChanging state and title to solve this for future cases.
This may be realized by preventing the node from being deleted using hook_node_access(). I investigated this before, but only recently I discovered this hook.
Comment #6
miro_dietikerSutharsan, could you please tell me why preventing the node from being deleted would improve the situation described?
I can't find any relation in the issue above.
Comment #7
simon georges commented@miro_dieteker, Sutharsan, should we do something about this subject ?
Comment #8
miro_dietikerSimon
I don't know of any other module that does something like that.
We could also output a warning.
In Drupal 6 there's no clean way to implement this. Moving this to D7 where we can implement the hook cleanly.
Please try ;-)
Comment #9
simon georges commentedPlease review ;-)
Comment #10
simon georges commentedThe patch above has been committed to 7.x-1.x.