SSO Notices don’t go away

  • Resolved an52

    (@an52)


    4 years, 2 months ago

    SSO Notice Plugin conflict detected — please uncheck the Add article:published_time to Posts? option in the The SEO Framework > Social Meta Settings metabox.
    SSO Notice Plugin conflict detected — please uncheck the Add article:modified_time to Posts? option in the The SEO Framework > Social Meta Settings metabox.
    SSO Notice Plugin conflict detected — please uncheck the Output Authorised Presence? option in the The SEO Framework > Schema Settings metabox.
    ForeverSSO Notice
    At least one of your theme header templates does not offer a recognized way to modify the head HTML tag attributes. Adding the document Schema item type to the head HTML tag attributes is important for Pinterest.

    The <head> HTML tag in your header template(s) should include a function, action, or filter for its attributes. WPSSO Core can update your header template(s) automatically and change the existing <head> HTML tag to:

    <head <?php do_action( ‘add_head_attributes’ ); ?>>
    Click here to update header template(s) automatically (recommended) or update the template(s) manually.

    This notice can be dismissed permanently.

    For the first three notices, I have unchecked the items, deleted the cache, but the message does not go away.

    For the last one, I am using a child theme of Neve, but SSO seems to edit the parent theme, which might be the issue.

Viewing 1 replies (of 1 total)
  • Plugin Author JS Morisset

    (@jsmoriss)

    I’ve just tested the latest version of The SEO Framework plugin, and WPSSO is able to detect when those options are checked (shows conflict notices) and unchecked (no conflict notices). Perhaps your hosting provider is using very aggressive caching for the options table? WPSSO reads The SEO Framework settings from the options table, where they are stored, and when The SEO Framework saves its settings, the settings in the options table should be updated. Are you using the W3TC cache plugin? The W3TC plugin has a history of bugs related to the WordPress object / transient cache, so if you’re using W3TC, you might try clearing its cache.

    WPSSO checks both child and parent theme header*.php files – I haven’t heard of any issues with WPSSO checking and updating header files, but I guess it’s always a possibility. Have a look at your header*.php files and make sure the <head> tags have been updated.

    js.

Viewing 1 replies (of 1 total)
  • The topic ‘SSO Notices don’t go away’ is closed to new replies.