When I want to create a Newsletter issue I get this message:
"Content type simplenews requires to be assigned to vocabulary Newsletter. Please change the vocabulary settings."
But in Taxonomy I have a vocabulary Newsletter and I selected Newsletter issue in Content types.
Can somebody help me? What did I do wrong?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | grab_simplenews_3.gif | 8.3 KB | As If |
| #5 | simplenews.275491.patch | 2.99 KB | sutharsan |
| #4 | grab_simplenews.gif | 12.24 KB | As If |
| #4 | grab_simplenews_2.gif | 5.14 KB | As If |
Comments
Comment #1
sutharsan commentedNew, but important it is: Simplenews settings. You can assign the vocabulary (and content type) Simplenews uses.
path: admin/content/newsletters/settings - general settings.
Comment #2
siril commentedIn admin/content/newsletters/settings - general settings under Newsletter content types I selected Newsletter issue and under Newsletter taxonomy I selected Newsletter. But I still get the message when I try to create a new newsletter.
Comment #3
sutharsan commentedPlease send a screen shot of your newsletter vocab settings.
Are you using category module?
Comment #4
As If commentedSame error here. Screenshot attached. Using 6.x-1.0-beta3 and also Simplenews action. [UPDATE: Turned it off. No difference.]
What I find really weird is that even though the message implies no relationship exists between SN and the taxonomy, the proper dropdown *does* appear, as shown in grab 2.
Did Siril's problem get fixed? Where can I find the solution?
Comment #5
sutharsan commentedI gone over simplenews use of vocabulary and tried to further simplify the code and use. Please try the 6.x-1.x-dev version. It should remove your message, if not go to Simplenews general settings (admin/settings/simplenews) and (re)save the content type and vocabulary settings.
Attached patch is committed.
Patch attached for documentation purpose.
Comment #6
As If commentedSorry. It created a second "Newsletter" vocab (as shown in attached grab). This second one had more complete info than the first (it was already assigned to the "Newsletter issue" type on the Vocabularies page), so I deleted the other one. Then I went back to the Simplenews settings and there was only one "Newsletter" vocab in the dropdown. So far so good. But after I selected it and re-saved the settings, I tried to create a new newsletter issue and I got the error message again.
UPDATE: I went through the entire process again. Uninstalled SN, then DELETED the Newsletter vocab, then cleared all my caches, then re-installed SN (this is the current dev version). It created the proper vocab and assigned the simplenews content type to it on the vocab page, but once again I got the error message when trying to create a Newsletter issue.
This issue is not fixed. Are there any differences between your patch and the current dev version?
Comment #7
sutharsan commentedYes, there is a difference. A development snapshot is created every twelve hours. The _current_ dev does not include the patch yet. You have wait untill the next is available or apply the patch or download the simplenews.module and simplenews.admin.inc file from cvs
Comment #8
As If commentedPatch applied, error gone. Looks like you nailed it. Thank you!
Comment #9
kilrizzy commentedI applied the patch and it works as far as sending but now when I try to subscribe or unsubscribe the following error arises:
Fatal error: Call to undefined function: _trigger_get_hook_aids() in /home/kilro2/public_html/aifunction/main/modules/simplenews/simplenews.module on line 1606
Thank you
Comment #10
sutharsan commentedThis is due to: missing requirement setting for simplenews_actions.
1. enable trigger module
or
2. disable simplenews_actions.
This bug as been reported before and fixed in 6.x-1.x-dev.
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.