Pro Features No Longer Working After Using WPEngine Migration Tool

SJF_me · November 7, 2019, 3:08pm

#Main Issue:
We are in the process of migrating to WPEngine and are having issues with using the Pro theme’s main features and editor.

The following Pro features are not working:

Headers [/pro/#/headers]
Content [/pro/#/content]
Footers [/pro/#/footers]
Templates [/pro/#/template-manager]

Clicking any of these four sections produces these same 2 JavaScript warnings

cs.js?ver=3.5.4:3143

Failed to inflate gzip data SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at r.uncompress (cs.js?ver=3.5.4:3143)
    at cs.js?ver=3.5.4:3103
    at Array.forEach (<anonymous>)
    at cs.js?ver=3.5.4:3103
    at y (cs-vendor.js?ver=3.5.4:2834)
    at H (cs-vendor.js?ver=3.5.4:2842)
    at w (cs-vendor.js?ver=3.5.4:2840)
    at e.invoke (cs-vendor.js?ver=3.5.4:1053)
    at e.flush (cs-vendor.js?ver=3.5.4:1046)

cs.js?ver=3.5.4:31

Transition Error TypeError: Cannot read property 'type' of undefined
    at r._pushInternalModel (cs-vendor.js?ver=3.5.4:4177)
    at cs-vendor.js?ver=3.5.4:4176
    at e._run (cs-vendor.js?ver=3.5.4:1112)
    at e._join (cs-vendor.js?ver=3.5.4:1111)
    at e.join (cs-vendor.js?ver=3.5.4:1078)
    at r._push (cs-vendor.js?ver=3.5.4:4171)
    at cs-vendor.js?ver=3.5.4:4110
    at y (cs-vendor.js?ver=3.5.4:2834)
    at H (cs-vendor.js?ver=3.5.4:2842)
    at w (cs-vendor.js?ver=3.5.4:2840) e {state: e, intent: r, router: e, data: {…}, resolvedModels: {…}, …}

Global Blocks [/pro/#/global-blocks]

Clicking to edit a Global Block produces this error & warning

cs.js?ver=3.5.4:3143

Failed to inflate gzip data SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at r.uncompress (cs.js?ver=3.5.4:3143)
    at cs.js?ver=3.5.4:3103
    at Array.forEach (<anonymous>)
    at cs.js?ver=3.5.4:3103
    at y (cs-vendor.js?ver=3.5.4:2834)
    at H (cs-vendor.js?ver=3.5.4:2842)
    at w (cs-vendor.js?ver=3.5.4:2840)
    at e.invoke (cs-vendor.js?ver=3.5.4:1053)
    at e.flush (cs-vendor.js?ver=3.5.4:1046)

cs-vendor.js?ver=3.5.4:4177

Uncaught TypeError: Cannot read property 'type' of undefined
    at r._pushInternalModel (cs-vendor.js?ver=3.5.4:4177)
    at cs-vendor.js?ver=3.5.4:4176
    at e._run (cs-vendor.js?ver=3.5.4:1112)
    at e._join (cs-vendor.js?ver=3.5.4:1111)
    at e.join (cs-vendor.js?ver=3.5.4:1078)
    at r._push (cs-vendor.js?ver=3.5.4:4171)
    at cs-vendor.js?ver=3.5.4:4041
    at y (cs-vendor.js?ver=3.5.4:2834)
    at H (cs-vendor.js?ver=3.5.4:2842)
    at w (cs-vendor.js?ver=3.5.4:2840)

Editing With Pro [/pro/#/content/123]

Clicking "Edit With Pro" produces these 3 Warnings and 1 TypeError

cs.13a2f57.js:5396

Failed to inflate gzip data SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at e.uncompress (cs.13a2f57.js:5396)
    at Object.attempt (cs.13a2f57.js:4477)
    at cs.13a2f57.js:4479
    at Array.forEach (<anonymous>)
    at resolve (cs.13a2f57.js:4479)
    at d (cs.13a2f57.js:4485)
    at cs.13a2f57.js:4497

cs.13a2f57.js:1451

TypeError: Cannot read property 'type' of undefined
    at r.<anonymous> (cs-vendor.13a2f57.js:4854)
    at r.t [as _pushInternalModel] (cs-vendor.13a2f57.js:4854)
    at cs-vendor.13a2f57.js:4854
    at e.r._run (cs-vendor.13a2f57.js:3327)
    at e.r._join (cs-vendor.13a2f57.js:3326)
    at e.r.join (cs-vendor.13a2f57.js:3292)
    at r._push (cs-vendor.13a2f57.js:4849)
    at cs-vendor.13a2f57.js:4608
    at g (cs-vendor.13a2f57.js:3718)
    at k (cs-vendor.13a2f57.js:3728)

cs.13a2f57.js:5396

Failed to inflate gzip data SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at e.uncompress (cs.13a2f57.js:5396)
    at Object.attempt (cs.13a2f57.js:4477)
    at cs.13a2f57.js:4479
    at Array.forEach (<anonymous>)
    at resolve (cs.13a2f57.js:4479)
    at d (cs.13a2f57.js:4485)
    at cs.13a2f57.js:4497

cs.13a2f57.js:50

Transition Error TypeError: Cannot read property 'type' of undefined
    at r.<anonymous> (cs-vendor.13a2f57.js:4854)
    at r.t [as _pushInternalModel] (cs-vendor.13a2f57.js:4854)
    at cs-vendor.13a2f57.js:4854
    at e.r._run (cs-vendor.13a2f57.js:3327)
    at e.r._join (cs-vendor.13a2f57.js:3326)
    at e.r.join (cs-vendor.13a2f57.js:3292)
    at r._push (cs-vendor.13a2f57.js:4849)
    at cs-vendor.13a2f57.js:4608
    at g (cs-vendor.13a2f57.js:3718)
    at k (cs-vendor.13a2f57.js:3728) e {from: null, to: {…}, isAborted: false, isActive: true, urlMethod: "update", …}

##Things We’ve Tried:

Completely removed Pro theme and reinstalled
Updated everything:
Pro Theme from 2.5.5 to 3.0.4
WordPress Plugins (including those included with Pro)
WordPress Core from 5.2.3 to 5.2.4
PHP from 7.2.7 to 7.3
Clearing Cache (both server-side and client-side)
Confirming CDN is disabled (was never enabled)
Reattempted the site migration multiple times (in case there was a hiccup)
Reset .htaccess and re-saved permalinks to reset .htaccess file.
Checked allocated memory is sufficient (was already at 256M)
Asking WPEngine for Support — 3 different times — and it was suggested to contact the theme author.

Similar Issues in the apex forum:

Current Setup vs. WPEngine:

Current            WPEngine
• Windows (IIS)    • Linux (Apache)
• PHP 7.2.7        • PHP 7.3
• Pro v.2.5.5      • 3.0.4
• WP 5.2.3         • WP 5.2.4

I will provide the URL and credentials through a secure note.

ruenel · November 8, 2019, 12:34am

Hello @SJF.me,

Thanks for writing in!

I have checked your site and I am seeing this JS error:

Failed to inflate gzip data SyntaxError: "JSON.parse: unexpected end of data at line 1 column 1 of the JSON data"

We highly recommend you to contact your WPEngine provider to check gzip compression settings or if you can disable any caching from your hosting control panel temporarily and test this issue further.

Please let us know how it goes.

SJF_me · November 11, 2019, 1:47pm

@RueNel - As previously mentioned, we are aware of the JavaScript error, and have contacted WPEngine multiple times…

I’ve reached out to them again for additional comment, to which they replied:

Thanks for the details and sorry to hear you’re having issues with the theme features. When you’re logged into the wp-admin, there’s actually not any caching on the site. If you have a particular page on the front end, I’ll be happy to exclude it from cache though.

Regarding gzip compression, it’s built into the platform as well.

As the middle-men, between Web Host and Theme Author… pointing fingers at one another, we are at a complete loss on what to do.

We would just like to move our existing fully functional website to a new host and have it fully functional there as well.

Is there perhaps built-in cache of some kind from Pro? Or maybe something that — when migrating from one host to the other — may have gotten lost in the shuffle? Sometimes error messages aren’t always exactly the reason something is broke, but rather a sign of a bigger issue. Meaning… maybe gzip isn’t broke, but a reference to that which it is trying to inflate via gzip is broke? Not sure. Just spit-balling ideas.

SJF_me · November 11, 2019, 1:55pm

From WPEngine’s Support Center (source: https://wpengine.com/support/platform-settings/#gzip)

WP Engine automatically uses GZIP compression to optimize performance of static files (like images, text files, JavaScript, and CSS) on your web server. As a result, GZIP directives are typically not needed in your .htaccess file. The following file types are automatically compressed by WP Engine with GZIP:

application/vnd.ms-fontobject
application/wasm
application/x-javascript
application/x-web-app-manifest+json
application/xhtml+xml
application/xml
application/xml+rss
font/otf
image/bmp
image/svg+xml
image/x-icon
text/cache-manifest
text/calendar
text/css
text/javascript
text/log
text/markdown
text/plain
text/richtext
text/vcard
text/vnd.rim.location.xloc
text/vtt
text/x-component
text/x-cross-domain-policy
text/xml
text/xsd
text/xsl```

is it possible there are additional GZIP directives which are needed in our .htaccess file? If so, what?

SJF_me · November 11, 2019, 7:24pm

Just an update: A senior tech at WPEngine is currently reviewing this issue. I’ve given the green light for them to do what they need to in order to fix it. So, for the time being, I’ve removed both WP and SFTP access from themeco to avoid any potential conflicts. I would still greatly appreciate any support, feedback, suggestions, anything. I’ll reenable the accounts once they’re out of there if they still haven’t fixed it. Thanks.

christian · November 12, 2019, 9:54am

Hey @SJF.me,

Thanks for letting us know. I’m sorry I currently don’t have an idea as to what is the exact cause of this but a quick way to determine if the issue is coming from WP Engine is to test migrating your site to another web host. If migration works in other web host, there could be a problem with the migration system of WP Engine.

This might be quite technical but if you’re interested, you can try creating a fresh WordPress install in WP Engine and just migrate the database. That’s just a workaround idea though for a chance to make your previous site setup work with WP Engine. We don’t have the details and exact steps here. WP Engine support might be able to assist you with this.

Let us know what the senior tech of WPEngine says and we’ll post this case in our issue tracker so our developers will be made aware of the conflict.

Thanks.

SJF_me · November 12, 2019, 2:27pm

Thank you @christian_y for the suggestion. I did exactly as you suggested and the errors seem to no longer be there. I’d like to keep this thread open for the time being in case anyone else runs into this issue, and I’ll add more information as I discover it.

The steps I took:

Exported SQL file from current site and uploaded it via SFTP so WPEngine support could import it into a blank install of WP
Took just the mu-plugins, plugins, themes directories from our current site and uploaded them via SFTP to WPEngine.

That’s it! Rather than using their migration tool, I simply manually migrated, and it worked. I still haven’t moved over the site in its entirety yet, so I’ll report back once the entire site is up to confirm that’s all it was.

christian · November 13, 2019, 9:27am

You’re welcome, @SJF.me. And, thanks for the details and future info you can provide.

system · November 23, 2019, 9:27am

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