Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Fatal error: Cannot use string offset as an array in /usr/home/www/sites/all/modules/antispam/antispam.module on line 1013
I get this error when I try to post a comment to a node.
Comment | File | Size | Author |
---|---|---|---|
#12 | antispam-1483796-11-FAIL.patch | 994 bytes | tim.plunkett |
#12 | antispam-1483796-11-PASS.patch | 2.82 KB | tim.plunkett |
#4 | antispam-1483796-4.patch | 2.27 KB | Dmitriy.trt |
Comments
Comment #1
Everett Zufelt CreditAttribution: Everett Zufelt commentedI cannot reproduce this, can you please provide steps to reproduce?
Comment #2
joey1911 CreditAttribution: joey1911 commentedI just enabled the Module, went to a node and tried to post a comment.
It's using TypePad as the antispam module if that helps.
Comment #3
intropedro CreditAttribution: intropedro commentedIn my drupal the line where the error is:
I have read in this web http://informationideas.com/news/2006/06/14/fatal-error-cannot-use-strin... that the error is produced by try use a vector when it is not a vector.
I do not know if this will help someone to solve the problem
Comment #4
Dmitriy.trt CreditAttribution: Dmitriy.trt commentedSteps to reproduce:
Causes:
Patch for the latest code from git is attached. It also resolves problem that conditions are joined using AND operator, while description on the settings form says "If a request to send content matches any of these rules, the actions defined below will be triggered". Also, when "body" rule is enabled together with other rules the query should use LEFT JOIN, e.g. to check email in nodes detected as spam too.
Comment #5
Dmitriy.trt CreditAttribution: Dmitriy.trt commentedComment #6
intropedro CreditAttribution: intropedro commentedI have apply the patch and it has solved the error:
Comment #7
spolaorso CreditAttribution: spolaorso commentedThanks a lot! The patch solve the error!
Comment #8
maestrojed CreditAttribution: maestrojed commentedThis seems to be a duplicate of http://drupal.org/user/328606
Two different solutions. The solution here is nice because its an actual patch. It would be great to get a little review so we know which solution to use.
Comment #9
alexpsfti CreditAttribution: alexpsfti commentedThanks it fixed my issue as well.
Comment #10
daryand CreditAttribution: daryand commentedthis patch fixed my error and problem as well.
thanks,
d
Comment #11
jemond CreditAttribution: jemond commentedPatch fixes the issue which I could reproduce. It's running in production. This is ready to go.
Comment #12
tim.plunkettI've written an automated test for this.
Comment #15
tim.plunketthttp://drupalcode.org/project/antispam.git/commit/3a681d8
Comment #17
Routh CreditAttribution: Routh commentedI am getting this with Version 7.x-1.5
Since I assume this patch was included with the 1.5 release, it seems that the issue was not resolved.
Comment #18
tim.plunkettI don't know why you would assume that, as it shows on the project page, 7.x-1.5 was released in July and this was fixed in November. You can use the dev version until 7.x-1.6 is released.
Comment #19
Routh CreditAttribution: Routh commentedWhoops, missed that. I saw that the error was originally posted with 1.4, and assumed the fix had been patched in with 1.5 - On dev now and working. Sorry.
Comment #20
maxrossello CreditAttribution: maxrossello commentedPlease publish a new official version ASAP as the plugin is unusable and I do not want to link my production site to dev version.
Thanks!
Comment #21
Anonymous (not verified) CreditAttribution: Anonymous commentedI also am using 7.x-1.5 and get this exact error in exactly the same use case as originally documented (several years ago).
It is disturbing that a new "recommended release" addressing this and other reported critical/major bugs has not been released.
7.x-1.5 is almost 2 years old, and I also do not want to employ a dev release on my production site.
Pretty please...
Comment #22
DamienMcKennaPlease do not reopen issues for bugs that have fixes already sitting in the dev release. Due to priorities in our lives we (the module's maintainers) just haven't gotten to do a new release that includes this fix. Until we do, it is recommended to try out the dev release, it should work.
Comment #23
Anonymous (not verified) CreditAttribution: Anonymous commentedIMHO, the module in question loses its integrity when critical known problems in the official release exist and are at least not pointed out on the module's main Drupal page. I also have a very busy life, and wasted a large amount of time due to this and my other reported error.
If the module's maintainers truly want people to use the dev release as if it was the official release, the module's Drupal page should state as much, in a manner that is highlighted.
Comment #24
DamienMcKennaI've updated the project page to suggest using the dev release, thanks for the suggestion.
Comment #25
mssqldestination CreditAttribution: mssqldestination commentedHi,
I am facing same problem on my Site http://www.mssqldestination.com
I have hosted it on Cpanel.
Can someone tell me which is the latest patch to apply and how can I apply it.
Many thanks in advance
Comment #26
DamienMcKenna@mssqldestination: i suggest just using the -dev version.
Comment #27
Anonymous (not verified) CreditAttribution: Anonymous commented@mssqldestination
IMHO, you will be wasting your time with the -dev version.
I switched to Mollom and have not looked back.