Whenever I attempt to approve or delete moderated content i get a message saying that it was successful, but the item remains in the queue. The modr8 log says that it was successful but it was not. This has been the case every time i try it.
any ideas?
how would i be able to pinpoint where it goes wrong?
Once i noticed that the page actually deleted the wrong page (one that wasnt in the queue). This was referenced in the success message. Does this suggest that it is posting the wrong id to the server?
i have experienced this in FF 3.5.2 and chrome
my installed modules are
backup_migrate
captcha
recaptcha
advanced_help
fivestar
modr8
stumble
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | admin-user-captcha.png | 68.38 KB | agileware |
Comments
Comment #1
pwolanin commentedIs the site very busy? Perhaps related to #629776: Mismatch of approvals when new posts arrive after form is loaded
Comment #2
motogirl commentedI'm having the same issue.
I've just installed modr8 and set the content type to be Published and In Moderation. It puts the new content into the moderation list, but when you publish it from that list, it doesn't actually publish, despite the message saying it was successful.
What I've noticed is this - If I go to the node edit screen for that node it still shows the checkmark on "In Moderation". If I manually remove the checkmark, it goes straight to being published. It's just that modr8 isn't removing this node from moderation on approval.
Any ideas on how to fix this?
edited to add:
I've noticed that the site is logging errors for this as below:
Invalid argument supplied for foreach() in site/modules/cck/content.module on line 1244.
Line 1244 is the middle line of this:
I'm not really savvy enough to know what this means.
Comment #3
agileware commentedHad the same issue and it turned out to be the Captcha module and specifically the following options:
* Add CAPTCHA administration links to forms
* Allow CAPTCHAs and CAPTCHA administration links on administrative pages
When these options are DISABLED then modr8 would approve content without error. Screenshot also attached.
With these options ENABLED, the following error "Invalid argument supplied for foreach() ..." would be logged and content approval would not be applied.