I had this module running with our site with no error prior to this new version. Now we are getting SQL errors with the Porter Stemmer module and the new forum update. (SEE BELOW) If we turn it off it goes away but this was an important module for us to use. Any ideas?
Thanks
Shannon
* warning: preg_split() expects parameter 2 to be string, array given in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 15.
* warning: Invalid argument supplied for foreach() in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 19.
* warning: implode() [function.implode]: Bad arguments. in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 27.
* warning: preg_split() expects parameter 2 to be string, array given in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 15.
* warning: Invalid argument supplied for foreach() in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 19.
* warning: implode() [function.implode]: Bad arguments. in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 27.
* warning: preg_split() expects parameter 2 to be string, array given in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 15.
* warning: Invalid argument supplied for foreach() in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 19.
* warning: implode() [function.implode]: Bad arguments. in /home/x/html/sites/all/modules/porterstemmer/porterstemmer.module on line 27.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | adfv_preprocess_blacklist.patch | 746 bytes | neclimdul |
Comments
Comment #1
michelleI don't know a thing about Porter-Stemmer and all the errors you're getting are in that module. AF doesn't use it directly in any way so I haven't the foggiest idea what it might be complaining about. Moving to their queue as they might have some better idea of what the errors mean.
Michelle
Comment #2
greggles@shannon - when do you get this error? On every single page load? When cron runs?
Comment #3
mkrakowiak commentedI get the same error (http://drupal.org/node/316963). I emptied cache and ran cron. If I turn off the PorterStemmer, everything is back to normal.
Comment #4
greggles@mkrakowiak - does it happen on every page load? Only on forum pages? Only when inserting a new forum post?
Comment #5
mkrakowiak commentedOnly on forum page(s). It won't display anything, but Drupal errors. However, after uninstalling Advanced Forum, forum works fine...
Comment #6
michelleOk, I've tracked this down to the code that lets people add to the author pane via include files. Unfortunately, I didn't write this code and it's a bit beyond me so I need to get the author involved.
Michelle
Comment #7
michellePulling this back to my queue because it's definitely AF at fault here. Still working on a solution.
Michelle
Comment #8
neclimdulSorry, I don't know why i didn't notice search had a search_preprocess function in d5. This was in turn calling porterstemmer_search_preprocess and triggering these errors.
Michelle's tested this and will probably be committing soon but attached is the patch to fix it.
Comment #9
neclimduland apparently committed :)
Comment #10
gregglesThanks to you both!
Comment #11
mkrakowiak commentedThanks to you all!
Comment #12
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #13
venusrising commentedComment #14
venusrising commentedHi Michelle-
Is there any way to alter the original top post here I made. In error, I added our path and it is showing up in the mother of all search engines. Sorry to bug you about this but it would be so appreciated is possible.
Thanks
Comment #15
michelleI took them all out.
Michelle