WordPress.org

Support

Support » Plugins and Hacks » [Resolved] Plugin conflict detected with Twitter card

[Resolved] Plugin conflict detected with Twitter card

  • MasterJuan
    Participant

    @masterjuan

    Hello!

    Your plugin is simpliest and working very well!

    But, I have manually insert Twitter card meta data and I am receive the message “Plugin conflict detected with Twitter card”.

    I have to avoid this message, can occur any problem with my twitter meta data, is any way to disable something from the code in order not to receive that message?

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

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author JS Morisset
    Participant

    @jsmoriss

    Could you cut-and-paste the exact error message?

    Thanks,

    js.

    MasterJuan
    Participant

    @masterjuan

    NGFB Warning :
    Plugin conflict detected — Please uncheck the ‘Twitter Card meta data’ Twitter option in the Yoast WordPress SEO plugin Social settings.

    The truth is that I want to keep the setting for my Twitter card from Yoast Plugin!

    However, I am wondering if there will be problem with this conflict!

    Plugin Author JS Morisset
    Participant

    @jsmoriss

    The free version of NGFB does not provide Twitter Cards, so you should not see that error. Thanks for letting me know – it’ll be fixed in the next version. You can ignore the error until then – sorry, I know it’s not great to look at, but the next version should be out early next week.

    BTW, WordPress SEO only provides the Summary and Large Image Summary Twitter Cards – the Gallery, Photo, Player, and (for some) the Product Cards can be quite useful to drive traffic. 😉

    js.

    MasterJuan
    Participant

    @masterjuan

    Fine, no problem!

    Your plugin helps me to solve a few things and to avoid displaying shortcodes when I was sharing to facebook.

    Together with Yoast SEO working like a charm!

    Plugin Author JS Morisset
    Participant

    @jsmoriss

    Yes, NGFB (or WPSSO) and WordPress SEO are a good combo. If you ever use the WordPress [gallery] shortcode, or embed videos from Youtube etc., you might want to look at the Twitter Cards from NGFB (or WPSSO) — they’ll give you much nicer results on Facebook and Twitter. 😉

    js.

    MasterJuan
    Participant

    @masterjuan

    Hello again Morisset,

    I am seeing another warning right now:
    “Media Library image id 1210 rejected – 798×800 too small for ngfb-opengraph dimensions (800×800 cropped). Upload a larger image, or adjust the ngfb-opengraph image dimensions setting.”

    I understand the warning but even if I want to avoid this mention I can’t close the message.

    You could consider to put a close function to that message.

    Regards!

    Plugin Author JS Morisset
    Participant

    @jsmoriss

    That’s a real warning that must be fixed – closing the warning would not fix it. Either upload a larger image, or reduce the image dimensions in the plugin settings.

    js.

    MasterJuan
    Participant

    @masterjuan

    Yeah, however inside a post i have small icons in .svgz format or other pictures which I don’t want to display on Facebook and of course I don’t want to have all my images with huge size apart from my featured image.

    May be I don’t understand the functionality besides that.
    Let’s say I reduce the dimensions from 800×800 to minimum, what will be the changes in fact?

    Plugin Author JS Morisset
    Participant

    @jsmoriss

    WordPress uses image size names to create smaller versions of larger images uploaded (thumbnail, medium, large, etc.). Sounds like you’re not using those features.

    js.

    Plugin Author JS Morisset
    Participant

    @jsmoriss

    MasterJuan
    Participant

    @masterjuan

    I am using Simple Image Sizes plugins to create custom sizes!

    So, I am using a few custom sizes instead of default. Is any way to force NGFB to consider them as smaller versions of my images?

    Regards!

    Plugin Author JS Morisset
    Participant

    @jsmoriss

    Ah, so if you’re using image size names (custom sizes), and not showing the originals, then you can have much larger originals. Although the defaults for the Open Graph Image Dimensions is 800×800 cropped, you’re much better off with 1200×1200 cropped. If you don’t want to upload larger images, you’ll have to reduce the Image Dimensions.

    js.

    MasterJuan
    Participant

    @masterjuan

    Thank you JS!

    I’ve deal with it!

    I preciate your info!

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘[Resolved] Plugin conflict detected with Twitter card’ is closed to new replies.