Error when trying to create a WC Archive Layout

In Pro 4.0.5, when trying to create a WC Archive Layout, I get the
“The preview could not load due to the iframe response being incomplete. This is most often related to a plugin conflict, or customizations introducing a PHP error” message. Other types of layout are fine - it’s just the WC Archive that is giving me problems.

If it helps, these lines show up in the debug log (I’ve removed part of the path)

[17-Dec-2020 22:26:37 UTC] PHP Notice: A non well formed numeric value encountered in /httpdocs/wp-content/themes/pro/framework/functions/frontend/generated-css/renew.php on line 247
[17-Dec-2020 22:26:37 UTC] PHP Notice: A non well formed numeric value encountered in /httpdocs/wp-content/themes/pro/framework/functions/frontend/generated-css/renew.php on line 248
[17-Dec-2020 22:26:37 UTC] PHP Notice: A non well formed numeric value encountered in /httpdocs/wp-content/themes/pro/framework/functions/frontend/generated-css/renew.php on line 249
[17-Dec-2020 22:26:37 UTC] PHP Notice: A non well formed numeric value encountered in /httpdocs/wp-content/themes/pro/framework/functions/frontend/generated-css/renew.php on line 249

Hi @devilman,

Thanks for reaching out.

To better help you with your issue, please give us the following information in a Secure Note and steps on how to replicate your issue.

  • WordPress Login URL
  • Admin level username and password

You can find the Secure Note button at the bottom of your posts.

Thank you.

Thanks, Marc. I’ve added a secure note now. To replicate the issue, it’s just a case of going to Pro>Layouts and trying to either edit my ‘Test’ layout or creating a new one of the type WC Archive.

Hi @devilman,

I narrowed this down to a conflict with WP Rocket which we were able to solve for the next update. I’ve installed a development build of Pro on your site containing the fix. You can safely update to the next version when it’s available.

That being said, there’s one more issue. Your site is doing a 301 redirect for /shop to the homepage, and the preview iframe isn’t setup to resolve redirects like that. I’ve confirmed this to be an issue in Pro because we should still be able to run the preview if the shop is the home page. We’ll see what we can do to make this possible.

Meanwhile, you can use the preview switcher (icon next to save) to preview your WooCommerce archives for other contexts like categories

Thanks, Alexander. I appreciate you taking the time to look into the issue for me.

You are most welcome @devilman!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.