Whenever I submit content to my test D6 site, I get this series of error, and yes, I realize it's the same error 4 times.
* warning: mb_ereg_replace() expects parameter 3 to be string, array given in /var/www/pathtositeroot/sites/all/modules/pathauto/pathauto.inc on line 165.
* warning: mb_ereg_replace() expects parameter 3 to be string, array given in /var/www/pathtositeroot/sites/all/modules/pathauto/pathauto.inc on line 165.
* warning: mb_ereg_replace() expects parameter 3 to be string, array given in /var/www/pathtositeroot/sites/all/modules/pathauto/pathauto.inc on line 165.
* warning: mb_ereg_replace() expects parameter 3 to be string, array given in /var/www/pathtositeroot/sites/all/modules/pathauto/pathauto.inc on line 165.
The node is saved successfully but the path is the same as it would be without the pathauto module installed.
This happens with various content types, this one was for a blog entry. If you need additional information and/or testing on a different install, I can do that, just let me know.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | mb_eregi_replace-warning.patch | 695 bytes | muldos |
Comments
Comment #1
gregglesAre you using freetagging? Does this error still happen if you disable all the taxonomies for the node?
I think this is related to taxonomies and a duplicate of http://drupal.org/node/222637 but I'm not sure.
Comment #2
jscoble commentedThis may have its roots somewhere else. I added a term to taxonomy and received these errors:
warning: array_merge_recursive() [function.array-merge-recursive]: recursion detected in /var/www/pathtositeroot/includes/module.inc on line 473.
warning: mb_ereg_replace() expects parameter 3 to be string, array given in /var/www/pathtositeroot/sites/all/modules/pathauto/pathauto.inc on line 165.
Comment #3
jscoble commentedYes, I'm using freetagging. The problem does not exist if I disable freetagging for that content type.
BTW, I had noticed the more terms I had in freetagging, the more times that error occurred.
Sorry about the duplicate issue, I must have missed that somehow when reviewing the issue queue. I will monitor that issue from here on out.
Thanks.
Comment #4
gregglesYeah, I'd say it's a duplicate of that issue then.
Comment #5
nrauni commentedi give this erro too..
when i go to save a new node, my pathauto not created a new alias, but the node is save correct.
Comment #6
muldos commentedHi i experienced this bug too and wasn't using advanced blog !
I experienced the bug when uploading multiples files to a node or when viewing / editing a node with a multiple files field
I have done a patch for the current stable version (6x-1.3).
Basically if an array is passed, it just take the first element of it (and it's safe because, if an array is passed it's a not wanted behaviour, and it's something that should not be passed to pathauto, so nothing unwanted will be done).
It will just makes mb_eregi_replace happy in case an array has lost his way through pathauto_cleanstring , and do not produce warning anymore.
Comment #7
dave reidI think this actually is a problem caused when multiple modules define the same token. Can you please try upgrading to token 6.x-1.x-dev and confirm if this is still a problem or if you see any 'token' watchdog messages?
Comment #8
muldos commentedHi Dave, as you suggested I tried the 6.x-1.x-dev version of token and revert my code of pathauto.inc to the original 6.x-1.3 version, and the warning message is gone.
Thanks for pointing me there :)
David
Comment #9
dave reidThanks for the follow-up. Marking this as fixed.