Ready to get started?Download WordPress


[Plugin: Search Unleashed] PHP error when deleting a menu (3 posts)

  1. annihilate
    Posted 4 years ago #

    Whilst seeing what the new menus options does in wordpress 3, I created a new one, then deleted it straight away and all works ok.

    I then created another one, this time selecting all the categories and adding them to the menu. I then saved the menu. When deleting this menu, the following php error occurs:

    [19-Jun-2010 05:17:36] PHP Warning: implode() [function.implode]: Invalid arguments passed in /home/xxxxxxxxx/public_html/wp-content/plugins/search-unleashed/engines/indexed.php on line 115

    Whether this is an issue with wordpress 3 or the plugin I don't know, but just thought I'd let you know about the error. I realise the plugin is only listed as compatible up to 2.9.2 so just a heads up that this may be something that needs looking at to be compatible with 3.



  2. mtg169
    Posted 4 years ago #

    It's the plugin. I have a whole punch of errors and warnings in my PHP logs related to search unleashed after WP3 upgrade on all the numerous sites I'm using it on. Author doesn't seem willing to update it though.

    That specific error only seems to happen if you use "Indexed WordPress" as the search engine. If you use "Default WordPress" you may get a PHP fatal every once in awhile when you first try to add a new post related to search-module.php. You'll just get a blank page in the admin panel...refresh and it's fine.

    I believe the implode warning happens because the array it passes is empty. Change the code in search-unleashed/engines/indexed.php to only run the implode function if there are values in the array and you'll eliminate the warnings in your logs or from showing on your site if you have them displaying (really shouldn't for security).

    Change line 115-117 to this:

    if (isset($this->terms)){
    			$this->terms = implode( ' ', $this->terms );
    			return str_replace( 'WHERE', 'WHERE 1=2 AND ', $request );

    That may or may not prevent the warnings. I have yet to test. There also appears to be numerous other problems with SQL injection too. I'm probably just going to dump it if author doesn't update.

  3. duckonwater
    Posted 3 years ago #

    Im also getting random errors since WordPress 3.0 upgrade. Hope the plugin author can fix this soon!

Topic Closed

This topic has been closed to new replies.

About this Topic