Meta Data Conflict with Time.ly Calendar Plugin

  • Resolved mikemesseroff

    (@mikemesseroff)


    7 years, 12 months ago

    Hello – When I share an event page via facebook, certain og meta data is appearing twice. I’ve determined through a lot of trial and error that the first instance of meta data is served from Yoast and the second is from Time.ly events calendar plugin.

    I’ve already contacted support at Time.ly og to ask them how to prevent their meta data from auo-generating, however, they have not been helpful. Is there anyway to FORCE the yoast meta og tags to be read over any others on the page? Here’s a screenshot of how the event is being shared now: https://www.screencast.com/t/lIGjcAu745).

    Screenshot of 1st instance in my code: https://www.screencast.com/t/R3lgDd1Kv
    Screenshot of 2nd instance: https://www.screencast.com/t/pFbKqR3F5

    Thanks a lot,
    Mike

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter mikemesseroff

    (@mikemesseroff)

    Perhaps there’s a way to ensure that the Yoast SEO tags appear below the Time.ly tags in the code?

    Hello @mikemesseroff,

    I’ve experience related to remove_action / add_action. I know solution how to remove/customize Yoast og tags. It isn’t possible to Yoast uses Time.ly tags. Time.ly plugin adds action wp_head with default priority (Yoast uses priority 1 and Yoast has action wpseo_head for customization). My opinion is that Time.ly should detect Yoast plugin and if Yoast is active then they can use Yoast hooks instead WP hooks. But you said that their support isn’t open for it.

    If you have experience how to add PHP script (in mu-plugins for example), I can try to see how Time.ly add_action wp_head and we can find way to remove their meta tags.

    Thread Starter mikemesseroff

    (@mikemesseroff)

    Hello @stodorovic – Thank you for your response. I was able to fix this (I hope). I removed this code from time.ly’s front.php:

    $dispatcher->register_action(
    ‘wp_head’,
    array( ‘view.event.single’, ‘add_meta_tags’ )
    );”

    Yes, this code adds WP action wp_head. If you remove this code, it’s fine. Only trouble is because each update overrides your changes.

    I just checked and I see that they use Ai1ec_Event_Callback_Action instead standard WP function add_action. We can use code to get object, but I’m not sure can we remove this action:

    
global $ai1ec_registry;
$callback_action = $ai1ec_registry->get( 'event.callback.action' );

    It’s only idea for more checking, if I find some better way in next days, I’ll write here.

    • This reply was modified 7 years, 12 months ago by Sa?a.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Meta Data Conflict with Time.ly Calendar Plugin’ is closed to new replies.