Needs review
Project:
Simplenews
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Jan 2013 at 10:22 UTC
Updated:
20 Nov 2015 at 09:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bolecha commentedI have the same problem.
Have you found a solution?
Comment #2
killtheliterate commentedI was able to resolve this by:
Tracing through the errors, it seems like the $category got lost somehow, maybe during a module upgrade, or something.
Comment #3
RKopacz commentedI tried the setps in #2 But no luck. I am still getting that same error. Using version 7.x-1.0. Any further thoughts?
Comment #4
RKopacz commentedGentle bump. Anyone?
Comment #5
Würden commentedthe steps in #2 didn't work for me either.
I have the same issue using 7.x-1.0 on a site where I upgraded from an old version of simplenews (mimemail and mailsystem too). I tried reinstalling all 3 modules completely but to no avail. Curiously though I don't have the issue on new sites with a fresh installation of simplenews so it seems strange it wouldn't work here.
Also the body is empty while the footer is the only thing displayed in the newsletter.
Comment #6
pslcbs commentedDon't know, but maybe my experience helps somebody.
I have two content types to send as newsletters and three newsletter categories.
Now I change the category to the original. Sending results = Newsletter sent ok.
Hope this helps
pslcbs
Comment #7
drewkeller commentedFor me, I tried to make a custom content type a newsletter by manually adding the newsletter category field (bad idea). So now I have two categories: N/A and my actual category. After much digging around and trial and error, I figured out some tables in my database had been emptied. Namely, field_data_field_simplenews_term, field_revision_field_simplenews_term and other pairs for other custom fields I had added. Also, simplenews_newsletter was empty. So I manually added the data back in, once I figured out what the node ids for each node and the term id.
something along the lines of (change 64 to your actual node id and 36 to your term id, and of course 'mydatabase' and 'mycontenttype'):
After getting this data back in the database, the test emails work without bunches of errors.
Comment #8
ajlow commentedGot same problem too...
Tried #2 but no luck either... :(
Comment #9
ajlow commentedOK, here is something I found out.
I installed simplenews, associated simplenews to a content type. Straightforward so far. Now, when I sent a newsletter from a node with content type that is now associated to simplenews and that was created before I installed simplenews, I got this error...
If you created a new node and then send a newsletter, it works!
Strange behaviour as the above steps on my local system (Mac OS X 10.8 with Drupal 7.19 and MAMP 2.0.3) didn't cause any errors whereas the above steps did on my Amazon EC2 instance...
I hope it helps other who have come across this particular problem!
Comment #10
RumpledElf commentedI had the same problem, I had existing content before installing simplenews, set my content type to a newsletter so all my content had no newsletter category set. With that field set, no errors.
Comment #11
alessandro rancati commentedSame problem here.
The error occurs if I add the newsletter category from the taxonomy page (/admin/structure/taxonomy/newsletter/add). Go check into the Newsletter category list in /admin/config/services/simplenews: the category will not be there.
The error can be fixed by FIRST removing all the wrongly inserted categories from the taxonomy list and by THEN adding the newsletter category from the proper page (/admin/config/services/simplenews/add/).
Then you will have to edit the pending newsletter issue(s) to reassign the proper category.
Warning: if you delete the wrongly inserted category (let's say "Customer news") and re-create it from the proper page with the same name ("Customer news"), the newsletter issue(s) will magically show the correct name but still point to the wrongly inserted, non existing category. You'll have to switch the issue's category to a different one, save, then edit and switch it back to the category of your choice.
Comment #12
mediaformat commentedThis was my case:
After associating an exsiting content-type with Simplenews, by default all exsiting nodes of that type were not associated to a newsletter category (unselected radio button).
Comment #13
hanskuiters commentedI think I figured it out. I had the same errors when adding a newsletter category through taxonomy. I removed the term. Then I added a category through admin/config/services/simplenews/add. The errors are gone now.
Comment #14
iainh commentedFor me it was the same as for @ajlow :
Comment #15
sumthief commentedI have the same problem. There are a way to reproduce it:
I have made patch that works for me. If there are will be more information how to reproduce problem in other place I could to finalize patch.
Comment #16
sumthief commentedComment #17
Ives commentedI had the same problem as @iainH and @ajlow.
By resaving (no changes necessary) the nodes created before Simplenews was enabled, the errors went away and the newsletter was sent.