Closed (fixed)
Project:
Simplenews
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
1 Jul 2006 at 10:29 UTC
Updated:
16 Mar 2007 at 14:17 UTC
Hi,
When using admin (which has all rights on the site) - simplenews works fine. However, when using moderator role for log in, i get the following error message:
array_shift(): The argument should be an array in [local_path]/includes/form.inc on line 469.
Location:[URL]?q=user/2/edit/newsletter
Referrer:[URL]?q=user/moderator
Has anyone else run into this?
| Comment | File | Size | Author |
|---|---|---|---|
| simplenews.JPG | 55.63 KB | sbrattla |
Comments
Comment #1
jphelan commentedI'm having the same problem, any ideas anyone?
Comment #2
Joseph Dunn commentedThis is happening to me as well.
Comment #3
MartinSfromB commentedI think it will happen on all sites .... think it's time to set it critical because no users can edit their newsletter settings.
Comment #4
jphelan commentedDoes anyone know whats going on here? I can't do anything with the module it very frustrating.
Comment #5
Ignas commentedSOLUTION
This error happened to when I moved site to other server.
I found, that that simple news created dublicate newsletter vocabulary (function simplenews_get_vid). Check your categories. If so, return your 'simplenews_vid' variable to original value by variable_set('simplenews_vid', YOUR_original_variable_vid); somewhere in PHP code and delete dublicate vocabulaty. Not nice, but solution for fast fix :(
Comment #6
igorik commentedI have this weird thing with subscription too, It started after I replace taxonomy with category module.
Comment #7
igorik commentedyes, This is showed after migrating from taxonomy into category module,
but after set appropriate category for node type newsletter it is works fine.
Comment #8
iedude@remote.insidetheie.com commentedI'm having this same problem, also shortly after migrating to a new server.
I can find/change my 'simplenews_vid' variable, but what/where "duplicate" vocabulary are you referring to??
Comment #9
jphelan commentedComment #10
icstars commentedmy apologies if this is posted incorrectly, this is my first post. i'm attempting to add to the comment thread for node/71776...
this issue also arose for us, specifically when we installed the taxonomy_access module.
we solved this issue by setting the proper permissions on the specific newsletter category.
/admin/access/category/5
where 5 is the group id of our registered users
specifically we needed to give LIST permissions for the users for our newsletter vocabulary and term. so our permissions are:
view:a | udpate:i | delete:i | create:off | list:on
hope this helps.
Comment #11
sutharsan commented