WordPress.org

Ready to get started?Download WordPress

Forums

NextGEN Facebook: Open Graph, Rich Pin, Twitter Card, SEO, and Schema Meta Tags
[resolved] Widget page broken. Javascript issue? (4 posts)

  1. J
    Member
    Posted 8 months ago #

    Hi,

    It seems the plugin is causing this strange issue where if I am on the Widgets page, it doesn't show the sidebars area at all (so i can't update or change widgets) and it doesn't show all the possible widgets in the main box.

    In additional to that, while on that page, hovering over the left side menu bar does not prompt the dropdowns.

    This feels like a javascript issue but console shows no errors. once I deactivate the plugin everything works again.

    Any thoughts?

    (this happens both on the latest published version and the 6.4 dev2)

    Decided to check one more thing before posting. went to the plugin settings page and got this error:

    Fatal error: Out of memory (allocated 47972352) (tried to allocate 311296 bytes) in .../wp-includes/SimplePie/Misc.php on line 843

    Went ahead and increased the memory but still getting this error with different numbers.

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

  2. JS Morisset
    Member
    Plugin Author

    Posted 8 months ago #

    I'm very careful about loading jQuery/Javascript/CSS code, and only load it when necessary -- which is on the Post/Page and NGFB-specific settings pages. When on the widget pages, there's no CSS or jQuery/Javascript loaded, so it must be something else...

    I could ask you to turn debug mode on, etc., but NGFB is effectively NOT running on the widget page, so the only debug info available will be NGFB loading it's classes (as WP loads all plugins)...

    If you define the following in your wp-config.php file:

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

    You should only see this when reloading the widget page:

    [26-Jul-2013 00:01:27 UTC] NGFB ngfbDebug                 :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbUtil                  :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbGoogl                 :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbNotices               :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbOptions               :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbUser                  :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbMedia                 :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbWebPage               :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbPostMeta              :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbStyle                 :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbScript                :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbCache                 :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbMessages              :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbAdmin                 :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbForm                  :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsGeneral       :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsAdvanced      :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsSocialSharing :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsFacebook      :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsGooglePlus    :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsTwitter       :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsLinkedIn      :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsPinterest     :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsStumbleUpon   :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsTumblr        :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsSocialStyle   :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsAbout         :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbAddOnPro              :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbTwitterCards          :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbPostMeta              :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbRewritePro            :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsGeneral       :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbSettingsAdvanced      :: __construct              : mark
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbPlugin                :: setup_vars               : NGFB WP debug mode is ON
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbPlugin                :: setup_vars               : File cache expiration set to 5 second(s)
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbPlugin                :: setup_vars               : NGFB HTML debug mode is ON
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbPlugin                :: setup_vars               : WP object cache expiration set to 3 second(s) for new objects
    [26-Jul-2013 00:01:27 UTC] NGFB ngfbUpdate                :: __construct              : mark

    This is from the Pro version, so your output may differ, but it should be close, and should *not* show any errors. I'm very meticulous about NGFB generating any kind of error or warnings in the debug log files, so the output should be nice and clean. ;-)

    js.

  3. J
    Member
    Posted 8 months ago #

    Thanks for the debug instructions. when I went now to try it the issue is gone.

    My best guess is that is was a memory issues and it just took time for my host to update my memory (1and1 doesn't allow adjusting memory on shared hosting via config file or php.ini so I had to do it through them).

    Thanks again.

  4. JS Morisset
    Member
    Plugin Author

    Posted 8 months ago #

    Excellent. Glad to hear things worked out -- I like to make sure NGFB is as bug-free as possible. ;-)

    Thanks,

    js.

Reply

You must log in to post.

About this Plugin

About this Topic

Tags