• Resolved wordfiend84

    (@wordfiend84)


    We updated the plugin and the Yoast display broke in the back-end, blowing up an icon to the size of the entire page, hiding the meta description and displaying multiple console errors. After contacting the host, they adjusted something on the server to remove caching, which unfortunately slows our site down but in the process, fixed the issue with your plugin. Here is what they wrote:

    Not that I am aware of, you can put these settings on individual sites, but if this is the issue, removing it fixes yoast and putting it in place breaks it. Here is the code:

    When this is added to the Pre_virtualhosst include file, this is causing Yoast to break:

    <IfModule mod_expires.c>
    # turn on the module for this directory
    ExpiresActive on
    # set default
    ExpiresByType image/jpg “access plus 1 month”
    ExpiresByType image/svg “access plus 1 month”
    ExpiresByType image/gif “access plus 1 month”
    ExpiresByType image/jpeg “access plus 1 month”
    ExpiresByType image/png “access plus 1 month”
    ExpiresByType text/css “access plus 1 month”
    ExpiresByType text/javascript “access plus 1 month”
    ExpiresByType application/javascript “access plus 1 month”
    ExpiresByType application/x-shockwave-flash “access plus 1 month”
    ExpiresByType text/css “now plus 1 month”
    ExpiresByType image/ico “access plus 1 month”
    ExpiresByType image/x-icon “access plus 1 month”
    ExpiresByType text/html “access plus 600 seconds”
    ExpiresDefault “access plus 2 days”
    </IfModule>

    These settings allow the browser to cache the above perimeters and helps pages load faster. If there is a way around this please let me know.

    ______________________

    Can you please investigate and fix the issue with your plugin so we can turn this back on and speed our site back up?

    Thank you,

    Ashley Sargent

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Same problem here!

    When I activate the plugin after the new update (7.5.1.) I receive the following error:
    “Warning: strpos(): Empty needle in /wp-content/plugins/wordpress-seo/admin/class-database-proxy.php on line 44”

    Also the website is not accessible when activating the plugin, so I had to deactivate the plugin. Could you please have a look on this issue?

    Installed theme: Newspaper by tagDiv

    Looking forward to your answer!

    Thanks,
    Benjamin

    Going back to the 7.4.2 version of Yoast SEO fixes the problem until the developers fix this.

    https://github.com/Yoast/wordpress-seo/releases/download/7.4.2/wordpress-seo.zip

    Also using Newspaper by tagDiv, but theme or other plugins aren’t causing the issue, it is the Yoast SEO update doing it.

    Plugin Support Michael Ti?a

    (@mikes41720)

    @gooma2 @benle1111 @wordfiend84

    Can you try and gather as much information for us as possible? Please perform the following:

    1. Make sure the issue doesn’t persist when Yoast SEO is disabled.
    2. Check for conflicts.
    3. Check for JavaScript errors with your console.

    If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers. Please report the issue to a third party developer as well.

    If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.

    Thread Starter wordfiend84

    (@wordfiend84)

    This ticket has not been resolved.

    I reached out and did as you asked and no one has responded whatsoever on GIThub. Here is what I wrote.

    Please give us a description of what happened.
    We updated the plugin and the Yoast display broke in the back-end, blowing up an icon to the size of the entire page, hiding the meta description and displaying multiple console errors. See screenshot for what we see and the console errors are listed below.

    After contacting the host, they adjusted something on the server to remove caching, which unfortunately slows our site down but in the process, fixed the issue with your plugin. Here is what the rep at the host wrote:

    _Removing this fixes yoast and putting it in place breaks it. Here is the code:

    When this is added to the Pre_virtualhosst include file, this is causing Yoast to break:

    # turn on the module for this directory ExpiresActive on # set default ExpiresByType image/jpg “access plus 1 month” ExpiresByType image/svg “access plus 1 month” ExpiresByType image/gif “access plus 1 month” ExpiresByType image/jpeg “access plus 1 month” ExpiresByType image/png “access plus 1 month” ExpiresByType text/css “access plus 1 month” ExpiresByType text/javascript “access plus 1 month” ExpiresByType application/javascript “access plus 1 month” ExpiresByType application/x-shockwave-flash “access plus 1 month” ExpiresByType text/css “now plus 1 month” ExpiresByType image/ico “access plus 1 month” ExpiresByType image/x-icon “access plus 1 month” ExpiresByType text/html “access plus 600 seconds” ExpiresDefault “access plus 2 days”
    These settings allow the browser to cache the above perimeters and helps pages load faster. If there is a way around this please let me know_.

    Console errors:

    snippet-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    metabox-primary-category-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-metabox-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    adminbar-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-wp-globals-backport-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wpseo-dismissible-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-babel-polyfill-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    yst_seo_score-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    metabox-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    commons-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-modal-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-replacevar-plugin-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    admin-global-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    featured-image-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    load-scripts.php,qc=0,aload,P5B,P5D=jquery-core,,jquery-migrate,,utils,,plupload,aver=4.8.2.pagespeed.jm.GJtfgSDSbc.js:9 JQMIGRATE: Migrate is installed, version 1.4.1
    wp-seo-metabox-category-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-admin-media-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-post-scraper-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-help-center-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-admin-global-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-featured-image-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-shortcode-plugin-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-babel-polyfill-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    commons-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-wp-globals-backport-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-metabox-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-metabox-category-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-admin-global-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-modal-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-help-center-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-admin-media-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-replacevar-plugin-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-shortcode-plugin-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-post-scraper-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    wp-seo-featured-image-750.min.js:1 Failed to load resource: the server responded with a status of 404 ()
    chrome-extension://liilchbbmdohoilfeonmdpcbhpekaiac/js/listener.js:6 PV:Chrome: startup
    metabox-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    adminbar-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    metabox-primary-category-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    featured-image-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    admin-global-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    wpseo-dismissible-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    yst_seo_score-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()
    snippet-750.min.css:1 Failed to load resource: the server responded with a status of 404 ()

    Screenshots:

    yoasterror1
    yoasterror2

    Please describe what you expected to happen and why.
    We should be able to see all Yoast fields in the back end and the overly large graphics should be regular size.

    How can we reproduce this behavior?
    I am not sure – if need be, I can provide my login in a private message of some sort so you can see the issue as I have described it.
    Technical info
    WordPress version: 4.8.2

    Yoast SEO version: 7.5.1

    Relevant plugins in case of a bug:

    Akismet Anti-Spam
    All-in-One WP Migration
    Category Sticky Post
    Clicky for WordPress
    Contact Form 7
    CSS & JavaScript Toolbox
    Disable / Hide Comment URL
    Display PHP Version
    Easy Table of Contents
    FD Footnotes
    Genesis eNews Extended
    Genesis Favicon uploader
    Genesis Shortcodes
    Genesis Simple Edits
    Genesis Simple Hooks
    Genesis Simple Sidebars
    Genesis Tabs
    GTranslate
    Limit Login Attempts
    Menu Icons
    Menu Icons: Icomoon
    Monarch Plugin
    Quick Page/Post Redirect Plugin
    Simple Social Icons
    TinyMCE Advanced
    Udinra All Image Sitemap
    Visual Website Optimizer
    Widget Clone
    Yet Another Related Posts Plugin
    Yet Another Stars Rating

    Tested with theme:
    Twenty Seventeen

    Thread Starter wordfiend84

    (@wordfiend84)

    Also we tested with all plugins and themes for conflicts but could find none.

    Plugin Support Michael Ti?a

    (@mikes41720)

    @wordfiend84

    If you’ve already performed a conflict check and were unable to find any javascript errors from a conflict with another theme or plugin, and you’ve already logged a GitHub issue, then we recommend you wait for feedback or further support on the GitHub issue.

    We think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Conflict with PHP module after update’ is closed to new replies.