• Resolved gruppo3millennio

    (@gruppo3millennio)


    Hi,
    unfortunately I have noticed that on my site ‘palermoviva.it’ the plugin conflicts with others (Matomo? Complianz?).
    The site goes into error:
    1. Showing at the top of all pages the words: tds_category_module_7
    2. The site’s favicon disappears
    3. The image in facebook posts is not loaded.
    By deactivating the AIOSEO plugin the site is back in order.

    Does anyone know what this is about?
    thanks for your support

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support MM Aurangajeb

    (@aurangajeb)

    Hi @gruppo3millennio,

    Thanks for reaching out!

    There are no known conflict issues between All in One SEO and the “Complianz | GDPR/CCPA Cookie Consent” or “Matamo” plugins.

    On my local site, I also tried to replicate the issue, but it appears to be operating normally here.

    It looks like you’re using the “Newspaper by tagDiv.com” theme (https://a.supportally.com/i/nc1888).

    Could you please follow these steps to troubleshoot the issue:

    1. If you’re using any caching service or plugin, then please clear all caching and deactivate any caching or performance plugins. This also includes server caching such as Varnish and CDNs such as Cloudflare. You’ll need to clear your caches after any changes you make in the steps below.
    2. Now deactivate and reactivate All in One SEO and see if this resolves the problem.
    3. Next, temporarily deactivate all plugins except All in One SEO. If the problem goes away, then you know it was caused by one of the plugins you deactivated. Reactivate each plugin one at a time until the problem reoccurs. This identifies which plugin is causing the issue.
    4. However, if the problem doesn’t go away after temporarily deactivating all plugins, then it might have something to do with your theme. Switch to the default WordPress theme (like- Twenty Twenty-One). If the problem goes away, then you know it was caused by your theme.

    Alternatively, you can use the Health Check & Troubleshooting plugin to debug possible conflicts by following these steps:

    1. Go to Plugins > Add New and install and activate the Health Check & Troubleshooting plugin.
    2. Go to Plugins > Installed Plugins and click on Troubleshoot below the All in One SEO plugin.
    3. This will temporarily disable all the plugins and switch to a default theme only for your user ID without impacting what your visitors see.
    4. Check to see if you’re able to reproduce the problem.
    5. Once you’re done troubleshooting, deactivate and delete the Health Check & Troubleshooting plugin.

    Regarding the Showing at the top of all pages the words: tds_category_module_7 error.

    Could you please go to All in One SEO > Search Appearance > Advanced and check whether “Run Shortcodes” is enabled or disabled?

    As seen here –
    https://a.supportally.com/i/tamfXb

    If you have that option disabled, please enable the “Run Shortcodes” toggle and let me know if you still have the same issue.

    Some shortcodes cause issues when they are parsed by AIOSEO. For this reason, we have a setting called Run Shortcodes that lets you control whether AIOSEO should parse shortcodes in your content.

    We have also covered this in our documentation here –
    https://aioseo.com/docs/running-shortcodes/

    Let me know how it goes or if you may need further assistance, and I will be happy to help!

    Thread Starter gruppo3millennio

    (@gruppo3millennio)

    Hi,
    Thank you for your support. I followed all the directions you gave me, unfortunately without success.
    Then, I looked in the general settings of the plugin and found “tds_category_module_7” in the Miscellaneous Verification box on the “Webmaster Tools Verification” page.
    Once this code was removed, the site started working correctly again.
    The problem has therefore been resolved, although I do not understand what could have happened and how this wording, which also appears several times when inspecting the page source, could have set itself.
    The important thing is that everything is working fine for now.
    Thank you for your assistance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘plugin conflicts’ is closed to new replies.