The preview was unresponsive after loading - help

[myoshka]

I’ve been getting problems with accessing the console. This problem has happened whilst working on a revolution slider. I got prompted for a login on another open tabs, once I logged back in the console would not load and hasn’t done since.

I haven’t changed any settings and don’t have any cacheing plugin running that I’m aware of.
I get a console warning:

The preview booted, but never requested the loader be removed.

Would you mind checking my CSS incase there’s anything i’ve done to cause an issue. I’m not sure this is the problem tho as I wasn’t editing CSS at the time this happened.

There aren’t any password protection on the directories, but I did have a problem with my PHP being reverted to 5 from 7 - this has been fixed now though and was a problem on my ISP’s side. It did fix problems earlier but they started happening within a couple of hours.

[myoshka]

The problem is occurring when trying to edit the attached page in pro.
I had been working on it all morning so I’m totally lost as to why this has happened.

I get the following warning when editing my HOMEPAGE in the console

WARNING: Binding style attributes may introduce cross-site scripting vulnerabilities; please ensure that values being bound are properly escaped. For more information, including how to disable this warning, see http://emberjs.com/deprecations/v1.x/#toc_binding-style-attributes.

[myoshka]

As this problem was isolated to just this one portfolio item.
I deleted and started again - the problem has gone away on the new page.

I’d still like to know what this could have been that caused the problem in the first place.

Thanks in advance

[myoshka]

Seems I spoke to soon.

The problem has come back on the new portfolio item and I am unable to access the PRO console.

The only thing I changed was the title of a revolution slider that needed to be relinked in the page.

On refresh wouldn’t let me back in.

I only have revolution sliders in the page.

[myoshka]

The preview booted, but never requested the loader be removed. 2
(anonymous) @ cs.js?ver=3.0.4:6827
fn @ cs-vendor.js?ver=3.0.4:841
invoke @ cs-vendor.js?ver=3.0.4:1335
flush @ cs-vendor.js?ver=3.0.4:1399
flush @ cs-vendor.js?ver=3.0.4:1207
end @ cs-vendor.js?ver=3.0.4:521
run @ cs-vendor.js?ver=3.0.4:643
_runExpiredTimers @ cs-vendor.js?ver=3.0.4:1030
Backburner._boundRunExpiredTimers @ cs-vendor.js?ver=3.0.4:490
setTimeout (async)
_installTimerTimeout @ cs-vendor.js?ver=3.0.4:1071
_scheduleExpiredTimers @ cs-vendor.js?ver=3.0.4:1048
run @ cs-vendor.js?ver=3.0.4:639
_runExpiredTimers @ cs-vendor.js?ver=3.0.4:1030
Backburner._boundRunExpiredTimers @ cs-vendor.js?ver=3.0.4:490
setTimeout (async)
_installTimerTimeout @ cs-vendor.js?ver=3.0.4:1071
_setTimeout @ cs-vendor.js?ver=3.0.4:851
setTimeout @ cs-vendor.js?ver=3.0.4:845
run.later @ cs-vendor.js?ver=3.0.4:24334
(anonymous) @ cs.js?ver=3.0.4:6825
(anonymous) @ cs.js?ver=3.0.4:6939
postMessage (async)
setupPort @ cs.js?ver=3.0.4:67010
init @ cs.js?ver=3.0.4:593
superWrapper @ cs-vendor.js?ver=3.0.4:25144
Class @ cs-vendor.js?ver=3.0.4:38222
create @ cs-vendor.js?ver=3.0.4:38482
instantiate @ cs-vendor.js?ver=3.0.4:1848
lookup @ cs-vendor.js?ver=3.0.4:1685
lookup @ cs-vendor.js?ver=3.0.4:1604
lookup @ cs-vendor.js?ver=3.0.4:34633
(anonymous) @ cs-vendor.js?ver=3.0.4:30206
fetchHandler @ cs-vendor.js?ver=3.0.4:48849
get @ cs-vendor.js?ver=3.0.4:49014
applyToState @ cs-vendor.js?ver=3.0.4:50253
getTransitionByIntent @ cs-vendor.js?ver=3.0.4:49218
transitionByIntent @ cs-vendor.js?ver=3.0.4:49332
doTransition @ cs-vendor.js?ver=3.0.4:49909
handleURL @ cs-vendor.js?ver=3.0.4:49375
_doURLTransition @ cs-vendor.js?ver=3.0.4:29951
handleURL @ cs-vendor.js?ver=3.0.4:29947
startRouting @ cs-vendor.js?ver=3.0.4:29812
startRouting @ cs-vendor.js?ver=3.0.4:4267
didBecomeReady @ cs-vendor.js?ver=3.0.4:5248
invoke @ cs-vendor.js?ver=3.0.4:1335
flush @ cs-vendor.js?ver=3.0.4:1399
flush @ cs-vendor.js?ver=3.0.4:1207
end @ cs-vendor.js?ver=3.0.4:521
run @ cs-vendor.js?ver=3.0.4:643
join @ cs-vendor.js?ver=3.0.4:663
run.join @ cs-vendor.js?ver=3.0.4:24110
(anonymous) @ cs-vendor.js?ver=3.0.4:24173
i @ jquery.js?ver=1.12.4:2
fireWith @ jquery.js?ver=1.12.4:2
ready @ jquery.js?ver=1.12.4:2
K @ jquery.js?ver=1.12.4:2

[myoshka]

I also get the following console warning when selecting "edit with pro"from the wp top bar menu

jquery.js?ver=1.12.4:2 Uncaught Error: Syntax error, unrecognized expression: #/content/15941
at Function.fa.error (jquery.js?ver=1.12.4:2)
at fa.tokenize (jquery.js?ver=1.12.4:2)
at fa.select (jquery.js?ver=1.12.4:2)
at Function.fa (jquery.js?ver=1.12.4:2)
at Function.a.find (jquery-migrate.min.js?ver=1.4.1:2)
at n.fn.init.find (jquery.js?ver=1.12.4:2)
at n.fn.init.a.fn.find (jquery-migrate.min.js?ver=1.4.1:2)
at a.fn.init.n.fn.init (jquery.js?ver=1.12.4:2)
at new a.fn.init (jquery-migrate.min.js?ver=1.4.1:2)
at n (jquery.js?ver=1.12.4:2)

[myoshka]

Added the following in the WP-config.php but no change

define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

[myoshka]

I had this already added in following a previous thread:

define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

but have changed this to

define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

I’ve had major issues today and have lost alot of work so will endevour to rebuild it and get back to you once I’ve got everything back.

[myoshka]

Going back through and troubleshooting this problem it was only isolated to this page

I found the following issue.

I was trying to get a slider to be 100% of it’s container.
The method I had been using was a classic section and row, with column container turned off.

This all worked fine until I only had classic containers in the page. When saved it would then cause problems with the console not loading with reloading or re-editing the page.

Is there a better method to achieve 100% container width, without using classic sections?

[ruenel]

Hello There,

Thanks for writing in! Just for future topics, self responding or bumping your post pushes it back in our Queue system so it takes longer to respond to.

Is there a better method to achieve 100% container width, without using classic sections?

• When you insert v2 sections, you may disable the “Inner Container” so that you will have a 100% container width. And this settings is best used when you are using Blank - No Container page templates. To know the different page templates in the theme, please check this out: https://theme.co/apex/forum/t/features-page-templates/50/1

Hope this helps.