Our installation of simplenews is not showing the dropdown list of newsletters when we go to the post newsletters page. We did an upgrade of the simplenews modules a while back so I'm wondering if something happened with that.

I tried installing simplenews on another drupal system using the same modules and it worked, so I'm guessing there is something in our simplenews tables or files that is causing problems that is causing the problem. We have tried uninstalling and reinstalling, but no luck.

What would I need to do to completely clean everything from the simplenews installation and start from scratch? Any other thoughts on how to solve this problem?

Comments

dougpetch’s picture

dougpetch commented

Having the same issue w/ 5.x-1.1 Any thoughts on how to fix?

pixelcort’s picture

pixelcort commented
Category: support » bug
Priority: Normal » Critical

We're also having the same problem. When creating a new content, we can't choose which newsletter to send using.

dougpetch’s picture

dougpetch commented

Pushed to the top, because my project is at a standstill until this issue is resolved. Does anyone have any ideas on what to try to fix this?

sutharsan’s picture

sutharsan commented

I may be able to help, but please supply more details!
When did it happen, what have you checked, what is right, what is wrong, do you use Category module (known incompatibility)?

pdjohnson’s picture

pdjohnson commented

We also have the same issue.

warning: Invalid argument supplied for foreach() in *****/httpdocs/sites/all/modules/simplenews/simplenews.module on line 365.

when a newsletter is created and the newsletter gets assigned to the orphaned newsletters category

grahamgilchrist’s picture

grahamgilchrist commented

Exact same issues here. At first I thought it was the 'Taxonomy Access: permissions module' interfering, but I disabled that and the dropdown still doesn't appear. Newsletters get created but are put into drafts or the orphaned newsletters list and I get the:

Invalid argument supplied for foreach() in *****drupal/modules/simplenews/simplenews.module

error.

grahamgilchrist’s picture

grahamgilchrist commented

Wait, I realised I was just being a dummy. For some reason the vocabulary turned itself off for this content type. I just went to Administer-> Categories then Edit Vocabulary (for newsletter) and ticked the newsletter box.
Hope this helps someone else!

pdjohnson’s picture

pdjohnson commented

Indeed this seems to be the case. Visit the administration page (admin/content/taxonomy) and select content type Newsletter Issue for the Newsletter vocabulary. That fixed it for me too.

Thanks for the pointer Graham ;-)

dougpetch’s picture

dougpetch commented

Thanks, Sutharsan, but Graham's tip to make sure the vocabulary was properly set did the trick for me. It just goes to prove that I do, in fact, know just enough about drupal to be dangerous......

With that said, it might be an idea to add a bullet to the readme.txt file as a reminder to check the vocabulary....

sutharsan’s picture

sutharsan commented
Status: Active » Fixed

I have the impression the problem is related to the upgrade and not to simplenews alone.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

eric.verhulst’s picture

eric.verhulst commented

I had the same problem when using the website in another language; The vocabulary had been translted (the field cn be edited) into Dutch. When I set it bck to the original "newsletter", the orphanisation stopped.
(tid was always set to 0 in the database table). I am now having a similar problem with the translated submit on another webiste. I guess i18n and taxonomy give problems becuase some of the terms are hardcoded in the modules.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

FWIW, I had this problem as well. I followed the steps in #6 to make the Newsletter vocab associated with the newsletter content type, but it already was. I changed it to be "Required" and my newsletters no longer look like they are orphaned on the list at admin/content/newsletters

Perhaps this is an upgrade issue and the fix is to just edit the vocab? Either way - works now.