• Resolved Jan

    (@janerio)


    Hallo all,

    I’m testing blocksy as theme at the moment. Somehow I do have “n/a” shown as text below the footer on the left. Already deativated all other plugins. Any idea what this is?

    Thanks a lot in advance
    Jan

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hey @janerio

    Have you, by chance, edited any theme files? I have looked at the DOM and it seems that not everything is working correctly, with even the body tag not inheriting the default WordPress classes.

    Would you be able to get back to us with a little bit more detail on this one?

    Thanks

    Thread Starter Jan

    (@janerio)

    Huhu @cteduard ,

    thanks for your reply. I have not edited any files or configuration manually. Just cloned my wordpress installation and replaced oceanwp with blocksy.

    
    ### wp-core ###
    
    version: 5.8.3
    site_language: de_DE
    user_language: de_DE
    timezone: Europe/Berlin
    permalink: /%year%/%monthnum%/%postname%/
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 0
    default_comment_status: open
    environment_type: production
    user_count: 1
    dotorg_communication: true
    
    ### wp-paths-sizes ###
    
    wordpress_path: /var/www/vhosts/hosting144774.a2e8e.netcup.net/httpdocs/jan-staging
    wordpress_size: 111,51 MB (116930966 bytes)
    uploads_path: /var/www/vhosts/hosting144774.a2e8e.netcup.net/httpdocs/jan-staging/wp-content/uploads
    uploads_size: 432,99 MB (454024523 bytes)
    themes_path: /var/www/vhosts/hosting144774.a2e8e.netcup.net/httpdocs/jan-staging/wp-content/themes
    themes_size: 26,61 MB (27900028 bytes)
    plugins_path: /var/www/vhosts/hosting144774.a2e8e.netcup.net/httpdocs/jan-staging/wp-content/plugins
    plugins_size: 68,64 MB (71973396 bytes)
    database_size: 11,77 MB (12337152 bytes)
    total_size: 651,52 MB (683166065 bytes)
    
    ### wp-active-theme ###
    
    name: Blocksy (blocksy)
    version: 1.8.16
    author: CreativeThemes
    author_website: https://creativethemes.com
    parent_theme: none
    theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, responsive-embeds, html5, title-tag, custom-logo, lifterlms-sidebars, boostify-header-footer, fl-theme-builder-headers, fl-theme-builder-footers, fl-theme-builder-parts, editor-gradient-presets, editor-color-palette, post-thumbnails, menus, align-wide, customize-selective-refresh-widgets, header-footer-elementor, widgets
    theme_path: /var/www/vhosts/hosting144774.a2e8e.netcup.net/httpdocs/jan-staging/wp-content/themes/blocksy
    auto_update: Deaktiviert
    
    ### wp-themes-inactive (1) ###
    
    OceanWP: version: 3.1.2, author: OceanWP, Automatische Aktualisierungen aktiviert
    
    ### wp-plugins-active (9) ###
    
    All in One SEO: version: 4.1.6.2, author: All in One SEO Team, Automatische Aktualisierungen deaktiviert
    Blocksy Companion: version: 1.8.17, author: CreativeThemes, Automatische Aktualisierungen deaktiviert
    Classic Editor: version: 1.6.2, author: WordPress Contributors, Automatische Aktualisierungen deaktiviert
    Contact Form 7: version: 5.5.4, author: Takayuki Miyoshi, Automatische Aktualisierungen deaktiviert
    EWWW Image Optimizer: version: 6.4.0, author: Exactly WWW, Automatische Aktualisierungen deaktiviert
    Getwid: version: 1.7.8, author: MotoPress, Automatische Aktualisierungen deaktiviert
    Monetization Code plugin: version: 1.0, author: aerin Singh, Automatische Aktualisierungen deaktiviert
    OneSignal Push Notifications: version: 2.2.3, author: OneSignal, Automatische Aktualisierungen deaktiviert
    WP-Matomo Integration: version: 1.0.26, author: André Br?kling, Automatische Aktualisierungen deaktiviert
    
    ### wp-media ###
    
    image_editor: EWWWIO_Imagick_Editor
    imagick_module_version: 1687
    imagemagick_version: ImageMagick 6.9.7-4 Q16 x86_64 20170114 https://www.imagemagick.org
    imagick_version: 3.6.0
    file_uploads: File uploads is turned off
    post_max_size: 128M
    upload_max_filesize: 128M
    max_effective_size: 128 MB
    max_file_uploads: 20
    gd_version: bundled (2.1.0 compatible)
    gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
    ghostscript_version: 9.26
    
    ### wp-server ###
    
    server_architecture: Linux 4.9.0-16-amd64 x86_64
    httpd_software: Apache
    php_version: 8.1.1 64bit
    php_sapi: cgi-fcgi
    max_input_variables: 4000
    time_limit: 180
    memory_limit: 512M
    max_input_time: 60
    upload_max_filesize: 128M
    php_post_max_size: 128M
    curl_version: 7.52.1 OpenSSL/1.0.2u
    suhosin: false
    imagick_availability: true
    pretty_permalinks: true
    htaccess_extra_rules: false
    
    ### wp-database ###
    
    extension: mysqli
    server_version: 8.0.25
    client_version: mysqlnd 8.1.1
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /var/www/vhosts/hosting144774.a2e8e.netcup.net/httpdocs/jan-staging/wp-content
    WP_PLUGIN_DIR: /var/www/vhosts/hosting144774.a2e8e.netcup.net/httpdocs/jan-staging/wp-content/plugins
    WP_MEMORY_LIMIT: 40M
    WP_MAX_MEMORY_LIMIT: 512M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: false
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_LOCAL_DEV: undefined
    DB_CHARSET: utf8mb4
    DB_COLLATE: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    
    ### aioseo (2) ###
    
    noindexed: Paginierter Inhalt, Autor-Archive, Datumsarchive, Suchseite, Attachments (attachment), Schlagw?rter (post_tag)
    nofollowed: Paginierter Inhalt, Attachments (attachment)

    Is there a way to “reset” the files / configuration? Maybe this is more efficient than searching a the script which echoes “n/a”. By the way: noticed the same behaviour on an other testing website: staging.vita-oeconomica.de (here “n/a” is above the header).

    Any hint is welcome. Thanks

    Hey @janerio

    Do you have any custom code inserted anywhere? This looks like some custom code that hasn’t had its tags properly closed and it is breaking other stuff.

    Like I said, something is definitely weird as you do not even get the normal classes for the main body tag, that are supposed to come with WordPress itself, so this is very unlikely to be an issue coming from the theme.

    Thanks

    Thread Starter Jan

    (@janerio)

    Hey @cteduard ,

    was able to figure out that “WP-Matomo Integration” Plugin is causing this DOM change.

    Thanks

    Hello @janerio

    Ah, glad to hear. It was impossible for Blocksy to be outputting this. ??
    I think it would be best to contact the plugin’s developers and see if they offer a resolution.

    Take care!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘“n/a” shown below footer’ is closed to new replies.