When I try to mark and email address in active, I receive these two errors:
* warning: implode() [function.implode]: Invalid arguments passed in /home/sdoud/public_html/sites/all/modules/simplenews/simplenews.module on line 1658.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1 query: UPDATE simplenews_subscriptions SET a_status = 0 WHERE snid IN() in /home/sdoud/public_html/includes/database.mysql.inc on line 174.
Any help would be appreciated.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | simplenews.350531_1.patch | 1.16 KB | sutharsan |
| #1 | simplenews.350531.patch | 1.6 KB | sutharsan |
Comments
Comment #1
sutharsan commentedIts a bug, the attached patch fixes it. Please test and report back.
Comment #2
andypostSuppose better to check is there parameters at all... and only then try to modify data!
Comment #3
sutharsan commentedThat's what the patch does. Tested it?
Comment #4
ridolfidesigns commentedHi,
I don't know if I am doing something wrong but I can never get patches to take. I always get an error. I follow the "how to patch" tutorial on here but I always seem to get an error.
Is there another place that tells how to patch so I can test to see if this works?
Thanks,
Eric
Comment #5
sutharsan commentedThis is the handbook page which explains it: http://drupal.org/patch/apply
However with a small patch like this you could also do it by hand.
Comment #6
ridolfidesigns commentedHow would I do it by hand?
Thanks,
Eric
Comment #7
sutharsan commentedOpen the patch and the target module in a plain text editor. Remove the lines of code marked with - add the lines marked with + The patch lists line numbers and preceding code to help you locate the right lines. Save the module.
Comment #8
ridolfidesigns commentedThank you very much, I patched the module and it fixed it.
Comment #9
sutharsan commentedFixed is not the right state for a bug report, it has not been committed yet. (If it was a support request it was Ok for you to marked it fixed.)
Comment #10
sutharsan commentedBy mistake the patch contained an other fix too. The attached patch is correct and is now committed.
Comment #11
ridolfidesigns commentedThe problem is fixed.