The preview was unresponsive after loading > only in header and in Safari

Hi support. I have the «The preview was unresponsive after loading. This is most often related to a plugin conflict or aggressive page cacheing.» problem but only in the Header builder on Safari and Firefox.

I can edit the header in Chrome so this is not critical but my preferred tool is Safari.

I can edit all the other parts of PRO (footer, content global blocks…)

I have already done the wp-config.php edit to define( ‘WP_MEMORY_LIMIT’, ‘512’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512’ );

Server is running WordPress 5.3.2 | PHP 7.3.14 | LiteSpeed | MySQL 10.3.22-MariaDB

OS Linux Database Data Disk Usage 18.1 MiB
Server LiteSpeed Database Index Disk Usage 3.0 MiB
PHP v7.3.14 MYSQL Maximum Packet Size 26.0 MiB
MYSQL v10.3.22-MariaDB MYSQL Maximum No. Connection 500
GD bundled (2.1.0 compatible) MYSQL Query Cache Size unknown
Server Hostname mrck.ecommunication.ca PHP Short Tag On
Server IP:Port 209.172.32.68:443 PHP Max Script Execute Time 180s
Server Document Root /home/ecommuni/public_html/mrck PHP Memory Limit 512.0 MiB
Server Date/Time 24 February 2020 @ 14:24 PHP Max Upload Size 80.0 MiB
Server Load 6.66 PHP Max Post Size 64.0 MiB

Hey Philippe,

The Header Builder works in Safari and Firefox in my test site and the fact that it works in Chrome on your end means the issue is neither with the server nor Pro.

There could be something in your Safari and Firefox browsers, probably an extension or configuration, that conflicts with the Header Builder. Would you mind reinstalling the latest version of Firefox and Safari?

Please also give us access to your site and the name of the Header so we could test it.

Thanks.

I have many sites made with Pro and I can edit their headers in Safari. This is the only one with that problem

Hi Philippe,

Unfortunately, the given URL does not redirect to the Admin page for me and it goes to not found page. I used the normal wp-admin URL and that is also not working. Would you please kindly double-check the information that you shared in the Secure Note?

Meanwhile. I’d appreciate that you check the point below and get back to us with the result:

Please go to Pro > Headers and add a new header, see if it works with no problem in Safari. If it works with no problem it shows that there is something on your specific header that is causing the issue.

Then, I would try to recreate the header using Safari and see what was the problem cause and which step would trigger the error that you have mentioned.

Thank you.

Hi Cristopher. I have just created a new header named «test» with the Starter Hero template and I can see ans edit it. So the problem is within the MRC header.

Hello Philippe,

The preview of the MRC header did not load because there is a JS error on the page coming from Slider Revolution. I went ahead resolve the issue by disabling the “Include libraries globally” option in the general settings.

Please go ahead and edit your MRC header now.

Hello Philippe,

The preview of the MRC header did not load because there is a JS error on the page coming from Slider Revolution. I went ahead resolve the issue by disabling the “Include libraries globally” option in the general settings.

Please go ahead and edit your MRC header now.

Thank you Ruenel. The header is loading but now the slider do not display anymore.

Hello Philippe,

You have added multiple slider on the page. You must specify the pages in the global settings then;

You can revert the settings and you will experiencing the preview issue again. As an alternative, you may temporarily deactivate the Rev Slider plugin whenever you edit the header, footer or the content.

Hope this makes sense.

This is a global header so this is on every page of the website. Also, the «multiple» slider is the same but the container/bar display more height on mobile. This is why I have activated the Include libraries globally in the RevSlider global settings.

Strangely, even if the Include libraries globally is activated, the header is now editable in safari. Problem solved.

We’re glad that the problem is not resolved, Philippe.

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