I'm getting the following fatal error when using the Bio Module 4.7.0 with the 4.7.0 version of drupal. I'm not a programmer but though i should report it.
Fatal error: Cannot use string offset as an array /filter.module on line 842
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | bio.patch | 765 bytes | NNonexistent |
Comments
Comment #1
s0niqu3 commentedwas having the same error, found http://drupal.org/node/53899 and applied the patch listed to filter.module, and it works now. Id suggest applying the patch and seeing if that solves your problem.
Comment #2
s0niqu3 commentedmay have spoken too soon. applying the afforementioned fix to filter.module allowed the bio module to function, however filter.module is no producing warnings all over the place. will research more tomorrow morning.
Comment #3
hectorplus commentedI just installed the bio and when trying to create one, i get this error:
Comment #4
Andrupal commentedShowstopper!
Same here, I get:
I'm using 4.7.1. I tried using the filter.module.patch as recommended above and it allowed the bio page to work, but it broke my ability to edit existing nodes.
Comment #5
jrbeemanI'm still receiving this error. Running 4.7.2. Has any progress been made in resolving it?
Comment #6
NNonexistent commentedBy analogy with http://drupal.org/node/53899#comment-81700 .
Comment #7
Andrupal commentedI've had to apply what I could read of the the patch manually because it "ends abruptly in the middle of the line" as the shell indicated.
I applied the change and I still get an error:
warning: Invalid argument supplied for foreach() in /home/.kearby/username/mysite.com/modules/user.module on line 1455.
Any thoughts...
Comment #8
scott.mclewin commentedMaintainers: the patch in comment #6 works, and this problem still exists nearly a near later in the Drupal 4.7 version of the module. Are you looking for some other feedback before it is accepted? Do you need somebody to roll it up differently?
Comment #9
scott.mclewin commentedRecent Drupal 5.x releases of the bio module don't have this problem. I'm closing the issue as won't fix just to clear it out of the queue. I don't think it is relevant any longer.