• Resolved L. Campbell

    (@l-campbell)


    I updated the plugin, and my site went down. The message shown when visiting my URL after the update is: Fatal error: Call to a member function get() on a non-object in /home/escporg/public_html/wp-content/plugins/nextgen-facebook/lib/options.php on line 389

    I tried deactivating and reactivating the plugin, but this didn’t resolve the problem. I have deactivated the plugin. I cannot activate the plugin because my site becomes inaccessible (error message is shown in place of my website). My WP-admin page becomes inaccessible as well, preventing login.

    I’m using Photocrati NextGEN version 2.0.33, Photocrati NextGen Pro version 1.0.6, Photocrati Theme version 4.7.3

    http://esc4p.org

    Hope you can help.

    http://wordpress.org/plugins/nextgen-facebook/

Viewing 9 replies - 1 through 9 (of 9 total)
  • I ended up replacing the new updated plugin with the previous plugin version. Let me know if there’s a solution for the current update.

    Plugin Author JS Morisset

    (@jsmoriss)

    Hm. That’s odd. The only get() method in that file is on line 401 in the current version. And right above it is the object creation. It relies on the lib/messages.php file being there. Hm. I’m guessing you upgraded by FTP? Any chance you didn’t update all the files, or some were not readable by the web server?

    Let me know what procedure you used to upgrade – I’d like to figure out how this was possible, so we can fix it for you, and it doesn’t happen to anyone else. 😉

    Thanks,

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    Can I assume this is no longer an issue?

    js.

    Thanks for your feedback. I’m still using the previous version of the plugin, and haven’t attempted to update again with the newest one. Give me a day or so, and I’ll try again and will report back.

    Plugin Author JS Morisset

    (@jsmoriss)

    Are you updating from within WordPress, or by FTP?

    js.

    I’m updating from within WordPress.

    Plugin Author JS Morisset

    (@jsmoriss)

    You may want to add the following to your wp-config.php file to capture additional errors:

    define('WP_DEBUG', true);
    
    if ( defined('WP_DEBUG') && WP_DEBUG == true ) {
            define('WP_DEBUG_LOG', true);
            define('WP_DEBUG_DISPLAY', false);
            @ini_set('display_errors',0);
    }

    Hopefuly the next update will go better – let me know – I like to make sure the plugin is running well for everyone.

    Thanks,

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    L.,

    It’s been 2-3 days now since the last follow-up on this topic. Can I assume everything went well with the update? Any errors in the debug.log file?

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    Closing this ticket for lack of feedback.

    js.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Updated Plugin – Fatal Error’ is closed to new replies.