-
Posts
-
Hosting provider WPEngine provides a tool to create a staging environment for each Live instance(see create staging image).
Once user selects the option to create a staging environment, using their WPEngine Plugin, the page is not visible, following (see Page Not Visible image).
This action also creates a item in the local storage (see local storage image).
Once the storage item is created user is not able to use the AVIA tools. User get a spinning wheel(see AviaNoLongerWorking Image).
In order to get Avia to work, user must delete the local storage item Active Tab.
There are 2 issues to solve,
1) why does AVIA become unusable?
2) why is the Create Staging page not visibleAccording to WPEngine, they claim this is Enfold Theme conflict because their tools work perfectly on the standard WP Theme. They may be correct, when we turn off the Enfold theme on the test Platform is the Staging tools work as expected.
Hi idonate!
It looks like you have 3 different copies of Enfold in your WordPress theme directory (they are all outdated). Go ahead and upload a fresh copy of Enfold and do not rename the folder or do any customizations and then activate that (the latest version is 3.0.8) and let us know when your done so we can take another look.
Also let us know if we can deactivate your other plugins while testing.
Cheers!
Elliott@idonate
I’ve been running several wpengine installs for a long time. These installs will happily copy back and forth between ‘live’ and ‘staging’ most of the time. I did experience one Enfold installation failing to be copied correctly, and when investigated, a lot of it’s tables were missing. I was never able to get a straight answer as to why that was the case, and I remain convinced it’s the wpengine process that isn’t work well, so I haven’t raised it with the team here. wpengine’s copying mechanism also fails from time to time on other installations I have that are not using Enfold. Sometimes I’ve never gotten to the bottom of it, but sometimes I’ve been able to pin it down to specific installed plugin. Personally I’m finding that their copy back and forth mechanism can not be relied upon, and in particular if you copy from Staging to Live, you can then find it’s hours before you can get them to fix the site, and for the premium price you pay for the hosting, they now frequently suggest that you go ahead and fix it yourself.I’m also finding that restore points are failing, and they’ll insist it can’t possibly have happened. Then when you review the backup that was supposed to have been restored you’ll be able to point to the fact that the full restore actually hasn’t restored the database from the requested backup – it fails silently.
So, they may be correct, but in all the investigations I’ve been through with them over issues on my sites, they’ve never told me that the theme is incompatible with their hosting.
Hey!
Maybe you should try another plugin such as WP MigrateDB or WP MigrateDB PRO. The transition is manual and may not be as easy as the wp engine’s migration process.
Best regards,
IsmaelHi!
We do not supply any copies of jQuery. We use the WordPress wp_enqueue_script function to include the version of jQuery that gets shipped with WordPress, http://codex.wordpress.org/Function_Reference/wp_enqueue_script.
This is how all themes and plugins should be adding jQuery to make sure there are no conflicts. You can see where we enqueue it on line 279 in the functions.php file.
wp_enqueue_script( 'jquery' );Though we do include the LayerSlider with Enfold and it has an option to include a copy of jQuery from the Google CDN in Dashboard > LayerSlider > Troubleshooting & Advanced settings so make sure that is turned off.
Cheers!
Elliott
- You must be logged in to reply to this topic.