Pro 2.0.3: Problems loading builder previews

[JvP]

Just upgraded to Pro 2.0.3 and now the preview in the builders won’t load anymore.

Found this in the console:

invalid regular expression flag s
    generateIframe/<@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs.js?ver=3.0.3:6783:34
    tryCatch@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:51261:14
    invokeCallback@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:51276:15
    publish@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:51244:9
    @http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:40727:16
    invoke@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:1335:9
    flush@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:1399:11
    flush@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:1207:11
    end@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:521:9
    createAutorun/backburner._autorun<@http://playground.local/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.0.3:1087:7
     cs-vendor.js:19500:7

Sending before port is ready request Object { action: "preview:observe-start", data: "bf645e27-b527-4499-87f8-fe755218b545", noreply: true } cs.js:77298:9

Sending before port is ready request Object { action: "preview:observe-end", data: "bf645e27-b527-4499-87f8-fe755218b545", noreply: true } cs.js:77298:9

No other plugins active, caches cleared, etc.

[GDM_Pixel]

Hi Support,

I have the very same bug, with the very same message in the dev console.

Maybe a hasardous and too early release ?

Best regards

Charles

[alexander]

Hi there,

Thanks for pointing this out. This has been corrected with a hotfix. The bug itself was introduced by a change in 2.0.3 meant to address a conflict with W3TC. Aside from this incident we’ve been getting reports of successful updates and the 2.0.0 major update itself has gone rather smoothly.