robscott
Forum Replies Created
-
v8.4.3 worked for me, after I cleared out wp_options as described. 8.4.4 also works. Going straight to 8.4.4 will most likely “just work” for anyone who never updated (could test on the live site, but actually outside of our remit in this case 🙂 )
Marking this resolved – well done with fast fix.
So I can confirm that Version 8.4.3 works with the SG Optimizer. In this case, deleting the plugin and reinstalling after the failed update did not work. What I needed to do was take out the entries in wp_options (I expect it was
shareaholic_settingswhich was causing our issue) and THEN install the plugin from fresh.I copied all the information, and updated the “version” part of
shareaholic_settingsto be 8.4.3 and re-inserted the following:shareaholic_has_accepted_tos 1
shareaholic_review_dismiss 1
shareaholic_settingsWhile leaving out the option
shareaholic_perform_update– this allowed the plugin to install successfully, retaining all the previous settings. Obviously, I could have reverted to a previous state, but I wanted to actually see where this issue lived and post a resolution, as I had licence to break things here!Hope this helps someone out of a situation.
Actually plugin won’t delete from WP Admin, so there’s something else happening entirely…
Looks like the initial error, which was borking things, is gone, but then again, if the plugin never installs, we don’t know! Will try to see what I can see on this one. Your original error may well be gone.
Hi,
I’m sorry to say that it does not. Initial upgrade made error (which pointed to Siteground optimizer), now still timing out after upgrade, even with all other plugins deactivated and on Twenty Seventeen theme.
I’m wondering if the failed upgrade left some issue? Will try remove and reinstall too.
okay – I suspected this was an immediate incompatibility! Good luck.
Which is to say SG Optimizer https://en-gb.wordpress.org/plugins/sg-cachepress/
Yeah its the staging site on siteground, and the siteground cacher is the error which caused server go away.
Forum: Reviews
In reply to: [Gutenberg] Very restrictive functions, and poorly thought outPerhaps contribute to the development of this plugin – and also contribute to core by weighing in at make.wordpress.org?
This is Open Source software, so if you use it, you are free to contribute.
If you have insight into how this plugin can be better, then that’s what beta testing is *for*.
Nobody is going to put a “not finished” visual editor into WordPress core.
Forum: Plugins
In reply to: [WooCommerce] Remove Cart and $ from storefront headerHi,
In fairness to Caleb, he’s trying to point in the right direction, and this isn’t a WooCommerce question, its a theme question as he said.
No, obviously, if the snippet is wrong, there’s not a lot we can do… except there is something! There’s a premium extension to Storefront called Storefront Powerpack.
If you buy that extension, you can edit the stuff in the header using the Appearance > Customizer > Powerpack options for this.
Forum: Fixing WordPress
In reply to: Theme Customizer Stuck on "Saved" (can't save!)@periago – in my case, above, this was not an issue with WordPress, but with my theme & PHP settings. The customizer should change to “save & publish” after you make a change, if this does not happen, then you may have an issue – post a new item into the forum, and describe what’s happening!
Forum: Fixing WordPress
In reply to: Theme Customizer Stuck on "Saved" (can't save!)Hi @anthum1 – your issue sounds like *something else* – I recommend you post a new item into the forum. Mine was from memory a php issue – I was custom coding my own customizer options in a theme.
It sounds like you have a different issue – you’re describing the post edit screen (not the customizer).
If you post your issue as a new forum post here, and describe it, you’ll get some help!
Forum: Plugins
In reply to: [Mailgun for WordPress] Plugin Fatal ErrorOkay I can see what this error is – PHP version on this site needed to be updated > 5.6. That works.
Forum: Plugins
In reply to: [WooCommerce] database table does not existOkay I have further info – the site in question is hosted on IIS (Windows) and probably (maybe, perhaps) it is that + the non standard database prefix which causes this.
I cannot confirm with my sample size of 1, but I have not seen this before in sites hosted in Linux.