WordPress.org

Ready to get started?Download WordPress

Forums

FeedWordPress Advanced Filters
[resolved] Plugin could not be activated because it triggered a fatal error. (12 posts)

  1. cjalas
    Member
    Posted 1 year ago #

    Hello, I am receiving this error when attempting to Active the plugin (v 0.5.5):

    Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/alasemp/public_html/onestopbot/wp-content/plugins/faf/feedwordpress_advanced_filters.php on line 155

    http://wordpress.org/extend/plugins/faf/

  2. Bas Schuiling
    Member
    Plugin Author

    Posted 1 year ago #

    The same as here?

    Let me know if downloading the latest version from here http://plugins.svn.wordpress.org/faf/trunk/feedwordpress_advanced_filters.php fixes the problem.

  3. cjalas
    Member
    Posted 1 year ago #

    Fixed with latest update from the author, along with updating my web server to PHP 5.3 or greater. The plugin will NOT work with PHP 5.2.17 (what I had before).

  4. Bas Schuiling
    Member
    Plugin Author

    Posted 1 year ago #

    I have include the requirement of PHP 5.3 in the description on WordPress now so it is more clear 5.3 is needed.

  5. ted.strauss@gmail.com
    Member
    Posted 1 year ago #

    I have PHP 5.3.3 installed ("5.3.3-7+squeeze15") and still getting this error while trying to activate the plugin.

    Fatal error: Call to a member function getFilename() on a non-object in /var/www/wp-content/plugins/faf/feedwordpress_advanced_filters.php on line 89

    When I tried with the svn linked one above, I get the same error.

  6. ted.strauss@gmail.com
    Member
    Posted 1 year ago #

    The line that triggers the error is this:

    $extension = pathinfo($fileinfo->getFilename(), PATHINFO_EXTENSION);

    I added a print_r($fileInfo); at the point where the error happens and got the following:

    DirectoryIterator Object ( [pathName:SplFileInfo:private] => /var/www/wp-content/plugins/faf//filters/categories_keyword.php [fileName:SplFileInfo:private] => categories_keyword.php [glob:DirectoryIterator:private] => [subPathName:RecursiveDirectoryIterator:private] => )

    So it appears that the object is being handled wrong, not an issue of PHP support.
    Thoughts?

  7. ted.strauss@gmail.com
    Member
    Posted 1 year ago #

    I tried downgrading to the 5.5 version. Now i get this error:

    Fatal error: Call to undefined method DirectoryIterator::getExtension() in /var/www/wp-content/plugins/faf/feedwordpress_advanced_filters.php on line 81

  8. masa720
    Member
    Posted 1 year ago #

    I'm running without a problem in the PHP 5.4.13

  9. Bas Schuiling
    Member
    Plugin Author

    Posted 1 year ago #

    Hum I didn't get any emails notificating me of new posts here, sorry.

    The problem was fixed in version 0.5.8 . If you have this version try to redownload.

    Problem was that the function I'm using is new since version 5.3.6 and I didn't notice that before. There is a check now if you look in the SVN.

    Hope this helps, let me know if not.

  10. ted.strauss@gmail.com
    Member
    Posted 1 year ago #

    Thanks for the tips (and the amazing plugin).
    I was getting the same error with 0.5.8.
    I managed to get the plugin to install by commenting out the offending sections:

    //if (version_compare(PHP_VERSION,"5.3.6","<"))
    //      $extension = pathinfo($fileinfo->getFilename(), PATHINFO_EXTENSION); // compat for 5.3 - 5.3.5
    //else
    //      $extension = $fileInfo->getExtension();
    //if ($extension == "php")
    //{
       include_once($fileInfo->getRealPath());
    //}

    The filters sections are appearing fine on FWP.
    We'll see if the filters work now.

  11. Bas Schuiling
    Member
    Plugin Author

    Posted 1 year ago #

    Thanks for that, I will look into it It just sucks - its hard to test against the other 26 php .3 (in php 5.4 everything is just splendid ) versions with a normal setup so please keep testing and reporting :)

  12. Bas Schuiling
    Member
    Plugin Author

    Posted 1 year ago #

    You can try and get the latest file from the development version SVN. The problem should have been fixed. The lines you commented out are loading in the filters so obviously they should not work unless witchery is involved.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic