Home Forums Weaver Xtreme Theme WeaverXtreme Theme Support: problem with "Disable Schema.org Structured Data"

Topic Resolution: Answered

This topic contains 6 replies, has 2 voices, and was last updated by  Dom 9 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
  • #53786



    Weaver Xtreme 3.2
    Weaver Xtreme Theme Support 3.2.2 (note: download from WP includes previous versions)

    When Advanced Options / Site options / Disable Schema.org Structured Data option activated, all schema.org data still visible in browser view-source window and with Google dedicated testing tool

    WP 4.9.4 + PHP 7.1.10/7.2.2 Local Host

    Same behavior with a new install:

    ### Weaver System Info ###

    — WordPress Configuration —

    Site URL:
    Home URL:
    Multisite: No
    Version: 4.9.4
    Language: en_US
    WP_DEBUG: Disabled
    WP Memory Limit: 40M
    Permalink: /%year%/%monthnum%/%day%/%postname%/
    Show On Front: posts
    Page On Front: n/a
    Page For Posts: n/a
    Current Theme: Weaver Xtreme (3.2)
    Post Types: post, page, attachment, revision, nav_menu_item, custom_css, customize_changeset, oembed_cache

    — Weaver Xtreme Configuration —

    Weaver Xtreme Version: 3.2
    Theme Support Version: 3.2.2

    — Server Configuration —

    Operating System: Linux
    PHP Version: 7.2.2
    MySQL Version: 5.7.21
    jQuery Version: 1.12.4
    Server Software: Apache 2.4.29

    — PHP Configuration —

    Local Memory Limit: 256M
    Server Memory Limit: 128M
    Post Max Size: 40M
    Upload Max Filesize: 40M
    Time Limit: 120
    Max Input Vars: 1000
    Display Errors: N/A

    — WordPress Active Plugins —

    Weaver Xtreme Theme Support: 3.2.2

    — WordPress Inactive Plugins —

    Akismet Anti-Spam: 4.0.2
    Hello Dolly: 1.6

    ### End System Info ###




    That option does not seem to be working. I will not be able to post any fix until later the week. I don’t have access to the master code at the moment, and don’t know if the problem is in Weaver Xtreme 3.2, or in the Theme support plugin. The option is missing from the Customizer interface, so I suspect it might be a 3.2 issue.



    The problem has been fixed in the just released Weaver Xtreme 3.2.1.

    Private Reply

    This reply has been marked as private.


    Those elements are deeply embedded into Weaver Xtreme and most other WP themes, and it would not be possible to remove them if for no other reason that it is certain that other existing users have used theme for custom CSS rules.

    Best Answer


    This reply has been accepted as the best answer.

    Just a follow up. There is no class ever used by the theme called hcard. Instead, it is vcard. And hentry is rarely used.

    BUT – both of these classes are added by core WordPress, and NOT the theme. So apparently the WordPress development team think these two classes are essential.



    Thanks for the explanation.

    Problem solved.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.