• Resolved touchscreendoc

    (@touchscreendoc)


    Running the latest version of your plugin. Every other product page loads just fine, except for two. They open up to a completely blank page and the developer tools in Chrome did not mention any errors. When I disable The SEO Framework plugin all is back to normal. I am even unable to edit those two products with getting a similar blank page. What could it be?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Hi @touchscreendoc,

    I’m sorry to hear you’re having issues with the plugin.

    Before we start, please always make an unchanged backup of your WordPress installation when you’re performing debugging actions.

    Could you perform the following steps? They’re straight forward, but long for completeness. It’s part of my daily routine as developer ??

    1. Activate The SEO Framework once more.
    2. Connect to FTP of your website.
    3. Create a local backup of the wp-config.php file, which is found in the root folder of your WP installation.
    4. Locate define('WP_DEBUG', false); within that file.
    5. Change that to define('WP_DEBUG', true);
    6. Upload and overwrite that file back to the root folder.
    7. Go to the broken page.
    8. You should see an error popping up, could you copy it and send it to me?
    9. Open the wp-config.php file once more, and set define('WP_DEBUG', true); back to define('WP_DEBUG', false);
    10. Overwrite that file again.
    11. The screen should become white again without errors showing.

    If you’re unsure if you’re up for this task, please consult with your developer first.

    If you wish to keep the error disclosed, feel free to contact me here with the provided details of the error.

    Cheers!

    Thread Starter touchscreendoc

    (@touchscreendoc)

    thanks for the quick reply, I’ve emailed you through your website.

    Plugin Author Sybre Waaijer

    (@cybr)

    Hi @touchscreendoc,

    The problem
    The reason this problem is occurring is because your website is out of memory.

    This is caused by many factors, and when manipulating multiple images for WooCommerce (for Open Graph), this was just a little to much for your website to handle.

    Thus a 500 error: the white screen of death.

    The memory usage of the image manipulation shouldn’t be at such a height: there are many other factors at play. One of which are the many errors being generated by other plugins, which drastically affects performance.

    Let’s get to solving this issue:

    Step 1
    First, please make sure all your plugins are up-to-date. One plugin in particular hasn’t been updated for over 4 years ?? This is where all the errors come from.

    Running outdated plugins are also a major security concern.

    That plugin, in particular, is for HTTPS.

    You can simply force your website to become HTTPS-only in a much more elegant and faster and lighter way. We’re talking about 20000x faster (I tested that conclusion this almost 3 years ago), and 100% fewer memory usage by that plugin – because it’s not active anymore.
    This is what you need to add to your .htaccess file:

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

    You can place this on top of the file. As always, keep a back-up, just in case.

    If “RewriteEngine On” is already set, you can remove the second occurrence.

    Step 2
    An image is being manipulated on that page. This is done by The SEO Framework for Open Graph image editing and processing.
    Now, this is quite a normal process. But your server, especially because of all the deprecation and other errors from the HTTPS plugin, is being overloaded.

    This overloading is done by just 20kB, out of ~256,000kB. So we’ve just overstepped the boundary.

    So step 2… is step 1.

    Moreover
    I see you’re running various plugins that were awesome in WordPress 3.8. But now WordPress covers that lot: much better and without expensive actions.

    One example is “Disable Comments”, this can be handled through the first 3 options of wp-admin/options-discussion.php.

    Another redundant plugin is “Add Admin CSS” – which is nice… but that also might just be another cause for “the last straw that broke the camel’s back”.

    And another is “Simple Custom CSS”, which is now neatly done by WordPress 4.7 through Customizer ??

    Now, there are a few more things that can be improved, but I think I covered the basics of it already.

    Best of luck optimizing! Cheers ??

    P.S. Upgrading to PHP7 will cut the overall memory usage by threefold, but that upgrade might be a little to much work and a great cause of headaches looking at the dated plugins.

    Thread Starter touchscreendoc

    (@touchscreendoc)

    EDIT: The web host increased the memory

    “””
    define(‘WP_MEMORY_LIMIT’, ’96M’);
    define( ‘WP_MAX_MEMORY_LIMIT’, ‘256M’ );

    We have increased the MAX_MEMORY_LIMIT to 512 M.
    “””

    so it appears to be good now.

    ———————————————–

    Thank you for your detailed reply. I’ve taken your advice and removed the outdated plugins, however upon re-activating the SEO Framework plugin the problem persists, albeit without any memory related errors, but still a blank page for certain products with the internal server 500 error. I’ve contacted the web host as well, but is there any other suggestions you might have to fix this?

    Thank you.

    Plugin Author Sybre Waaijer

    (@cybr)

    Hi @touchscreendoc,

    It’s good to see that increasing the memory limit has alleviated the issue; this means there was no “infinite loop” ??

    When images are bigger than 1500px in width/height, Facebook denies them. So TSF converts them to 1500px.
    I still need to figure out a way to cache this…

    …maybe in post meta: Eureka! ??

    Thanks for this ??
    Have a wonderful week and the best of luck with your website!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘I am unable to load 2 product pages while SEO Framework is enabled.’ is closed to new replies.