WordPress.org

Forums

NextGEN Facebook - Complete Meta Tags for Facebook, Google, Pinterest, Twitter & More
[resolved] Conflict to Subscribe to Comment Reloaded (13 posts)

  1. 3tonine
    Member
    Posted 1 year ago #

    Just here to report this conflict, to both authors.

    The plugin has a virtual management page which would stop working once NGFB Open Graph+ is activated (Latest version).

    Before with 6.16.1, everything was fine... that was a simplier time lol

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

  2. JS Morisset
    Member
    Plugin Author

    Posted 1 year ago #

  3. 3tonine
    Member
    Posted 1 year ago #

    Thanks for the prompt reply & sorry if I didn't provide enough info, guess that's not best practise, please accept it from a rookie :)

    I tried a couple of things, the silence debug option came with the UI, which didn't show me much except things like how NGFB disabled some social buttons on my bp_activity page. I don't see any error term.

    With the WP debug and log included option, I got a couple of these (actually a very long list), but they're about the same so let me sum up:

    [05-Dec-2013 ...] PHP Catchable fatal error: Object of class WP_Error could not be converted to string in .../wp-content/plugins/nextgen-facebook/lib/opengraph.php on line 42

    [05-Dec-2013 ...] PHP Warning: htmlentities() expects parameter 1 to be string, object given in .../wp-content/plugins/nextgen-facebook/lib/head.php on line 195

    So it turned out, if I kept the debug mode on, the other plugin (Subscribe to comments reloaded) starts back to work. I assume it's because NGFB's cache function is off in debug mode.

    My option is to turn on debug mode all the time and try to install some other cache plugin which includes the option to exclude folder/plugin, in order to get everything to work together, or there's somehow other method to get NGFB to get along with other plugins?

    Any advice will be much much appreciated, and anyway, thanks for the great plugin.

  4. JS Morisset
    Member
    Plugin Author

    Posted 1 year ago #

    LIne 42 of opengraph.php is this:

    $cache_salt = __METHOD__.'(lang:'.get_locale().'_sharing_url:'.$sharing_url.')';

    The $cache_salt is a pointer to the information stored in the cache. It looks like you have have a problem with the WordPress get_locale() function. Do you have a WPLANG constant defined in your wp-config.php file? If not, maybe you should...

    Do you have a URL to the webpage with an issue?

    js.

  5. 3tonine
    Member
    Posted 1 year ago #

    Yeh I should? I thought it functions with a default value, cause I found WP doesn't work bilingually (I don't mean several versions of one site for different readers from different countries... that's not bilingual right? :-)

    Anyway, I surely will follow your instruction, just did give it back its value.

    Here's where I test all the plugins I gathered, that's alot, so I didn't dare to let people have a look...

    http://3tonine.com/dev/preview/gallery-1/comment-page-1/

    Post a comment and choose a subscription type, then try to unsubscribe from the link at the bottom, hopefully you can replicate the issue, a blank page.

    You're like the serious serious developer I ever run into, man you rock!

  6. JS Morisset
    Member
    Plugin Author

    Posted 1 year ago #

    Normally get_locale() should return 'en_US' if nothing has been defined, but something in your installation is causing WordPress to return an error. If you've made any language related changes and/or installed language related plugins, you may want to review those changes / settings.

    The 'object' error in the head is an odd one - I can't see how an object would get there. I've added an extra check in the code, just in case, but I'll need you to turn on debug mode and provide a URL to an example page to investigate further.

    js.

  7. 3tonine
    Member
    Posted 1 year ago #

    Nope, nothing language related, the core is untouched too, just in case, I'm going to switch it to default theme to get rid of any custom functions in the child theme.

    Debug is on now, but then the problem can't be shown too. I don't see where are we going now but will try my best to cooperate... Just pls speak to me in layman's terms lol.

  8. JS Morisset
    Member
    Plugin Author

    Posted 1 year ago #

    Well, let's start with the other problem then -- a meta value that is an object. That shouldn't happen, so maybe it's related.

    Would you mind installing the DEV version from http://downloads.wordpress.org/plugin/nextgen-facebook.zip? I've added an extra check of object values, which will at least tell us which tag has that object value, and then maybe I can trace it back to its source.

    Uninstall and install instructions are here: http://wordpress.org/plugins/nextgen-facebook/installation/

    Thanks,

    js.

  9. 3tonine
    Member
    Posted 1 year ago #

    Uploaded and activated, with debug on.

  10. JS Morisset
    Member
    Plugin Author

    Posted 1 year ago #

    Looks good. No report of any object value.

    NgfbHead                  :: show_html                : 11 meta_tags to process
    	NgfbHead                  :: get_meta_html            : meta og:locale = "en_US"
    	NgfbHead                  :: get_meta_html            : meta og:site_name = "3tonine – Dev"
    	NgfbHead                  :: get_meta_html            : meta og:url = "http://3tonine.com/dev/preview/gallery-1/"
    	NgfbHead                  :: get_meta_html            : meta og:title = "Gallery #1 – 3tonine - Dev"
    	NgfbHead                  :: get_meta_html            : meta og:description is empty (skipped)
    	NgfbHead                  :: get_meta_html            : meta og:type = "article"
    	NgfbHead                  :: get_meta_html            : meta article:tag = "preview"
    	NgfbHead                  :: get_meta_html            : meta article:published_time = "2013-12-04T01:33:24+00:00"
    	NgfbHead                  :: get_meta_html            : meta article:modified_time = "2013-12-05T00:26:45+00:00"
    	NgfbHead                  :: get_meta_html            : meta og:image = "http://3tonine.com/dev/files/2013/12/Forest-1024x630.jpg"
    	NgfbHead                  :: get_meta_html            : meta og:image:cropped is disabled (skipped)
    	NgfbHead                  :: get_meta_html            : meta og:image:height = "630"
    	NgfbHead                  :: get_meta_html            : meta og:image:width = "1024"
    	NgfbHead                  :: get_meta_html            : meta description is empty (skipped)

    js.

  11. 3tonine
    Member
    Posted 1 year ago #

    Yeh, I have never experienced problem with the plugin's open graph function, expect not sure what to do with buddypress's activity stream feature, where site activities will be automatically included, post previews, excerpts, etc, alot there to grab, hard to give hints to NGFB.

    Back to this post subject, if there's another plugin conflicts with NGFB's cache function, is there a work around to help with the compatibility? If I choose to run NGFB in debug mode the whole time, would that be a problem?

    I'm going to test the two plugins with some major cache plugins to see what happen, if "subscribe to comments reloaded" not just having problem with NGFB but also other pplugins, I'll mark this as resolved right away.

    Thank you so much for your time js, cheers!

  12. JS Morisset
    Member
    Plugin Author

    Posted 1 year ago #

    The Pro version of 6.17.0 will add support for BuddyPress. There are some integration issues though because BuddyPress does not use many of the WordPress features. See http://surniaulula.com/codex/plugins/nextgen-facebook/notes/buddypress-integration/ for more info.

    You can selectively disable some caching features using constants. See http://surniaulula.com/codex/plugins/nextgen-facebook/notes/constants/ for more info. Other caching plugins will not help NGFB Open Graph+, but may help your website performance as a whole.

    If you see additional errors from NGFB in your debug.log, please let me know.

    Thanks,

    js.

  13. 3tonine
    Member
    Posted 1 year ago #

    Thanks to the help from js and the flexibility NGFB comes with, I'm able to avoid this conflict by disabling the TRANSIENT CACHE function. Just here to leave a note and close the case :)

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.