garrettzucker

There is at least one other option not discussed above, called Classic Press. It is on our radar for future use if/when WordPress stops being usable for our company.

Also, right now we use Disable Gutenberg and our website works just like it used to before Gutenberg came along. We are trying not to invest in a new website, but if we do, it will either be on Classic Press or some other platform–not WordPress.

Just last night I helped someone who was facing the same issue. They could not understand or use the block editor, and nothing on their site loaded so they could see the posts and pages. I brought them here, we downloaded and installed Disable Gutenberg, and they were so happy! I was shocked at how Gutenberg had basically locked up their site and did not work at all. It was like staring at a blank page with no instructions…typical Gutenberg!

@hristo-sg I am wondering if you were able to address this issue? I have not heard anything from you on this. Do you need anything else from me?

I did not want to put the link to our admin page, but don’t know how else to show you the notice.

@hristo-sg I am confirming that it is okay for you to edit that incorrect code and then enable the minification.

Provided that if you enable the minification and the site again breaks, you will restore the backup.

Please let me know if you need anything else from me. I believe I have provided everything you and Siteground need in order to assist with this issue.

Thank you very much for your assistance. If all goes well, I’ll revise my review up to 5 stars.

@hristo-sg, I am not a programmer and am not able to understand what you are asking me to do, or where to get this fixed. We use off-the-shelf WordPress and plugins. I have not customized any of the software myself, but it is possible that others did so before I inherited this website.

Is there any way you call provide more support and information on your suggestion? Such as where this code might be found? I have no idea even where to look or how to approach trying to fix what you are suggesting.

@hristo-sg, Here is the most recent ticket: Ticket 2968808

The latest answer I received is this:

“It seems that the issue was caused by the HTML Minification option of the plugin which doesn’t appear to work as expected with your current theme. I disabled the feature and the site is working as expected.

You can continue to use the plugin for caching but leave the minification options disabled so they don’t break the layout.”

I have not tested this yet or seen it in action. But I would appreciate if you look into this ticket and provide any help you can for us as we would prefer to use this plugin. I am not a developer or coder, but I do “manage” our company’s website and am responsible for the content as well.

Thank you.

@manzwebdesigns, you might also look into the Disable Gutenberg plugin by Jeff Starr. It has many helpful features, and does not expire in 2022 like the Classic Editor plugin does. I hope this is helpful for you.

@grimmag, there are some good options for you. One is to install the Classic Editor plugin, but that is a temporary fix. The other is to install Disable Gutenberg plugin by Jeff Starr–this has many more features and is noted to extend beyond Classic Editor’s cutoff date. Finally, a fork called ClassicPress might be worth looking into.

I have been examining all of these options, while we have held off any any upgrade to WordPress 5.0. My current thinking is that our best option is the following:

1. Install Classic Editor Plugin (done!)
2. Install Disable Gutenberg Plugin (done!)
3. Sometime in January 2019, upgrade to WordPress 5.0 after performing full backup
4. After the upgrade, verify site is still working as normal
4a. If NOT, downgrade to previous version of WordPress/restore via backup
4b. If YES, deactivate Classic Editor plugin to let Disable Gutenberg take precedence
5. After letting Disable Gutenberg take precedence, verify site is still working as normal
6. [ Removed sales pitch ]
7. Continue following ClassicPress fork and determine within one to two years if our website should migrate to ClassicPress–unless our internal programmers come through with a custom site (as they would like to) in order to completely get away from WordPress

I hope this helps.

• This reply was modified 6 years, 2 months ago by Jan Dembowski.
• This reply was modified 6 years, 2 months ago by Jan Dembowski.

@hristo-sg, sorry, but our website is loaded with plugins. How am I supposed to know which plugins your SG Optimizer now won’t work with, when it had been working prior to December 3, 2018? Is there anyone at your organization who can look at our website and tell me exactly which plugins are no longer compatible with your plugin? And honestly, I’m having a hard time trying to understand why I would disable plugins that seem to be working well, when it actually appears that SG Optimizer has now been causing all kinds of errors and issues for our website, and for other websites as well as noted here in the Support forum?

@hristo-sg, actually, Siteground did post a ticket. So at this point, I believe they are working on all the issues. We had conflicts with caching programs, A3 Lazy Load, notices at the top that would not go away, and basically whatever SG Optimizer was doing was breaking our website so it would show a black screen or a white screen or just garbage. At this point it is deactivated, and I’m not a programmer, so for now we are avoiding this plugin. I don’t know how else to help you all. It worked fine for us up until December 3, 2018, when you went to your latest update. Then I see a flurry of fixes and none of them helped our website at all.

There were so many errors and issues, even with several phone calls and tickets in for support, that Siteground itself deactivated this plugin for our website, and I also deactivated it at my dashboard. I don’t know what is causing all the issues. So many of them including cacheing, error messages, etc… So for now, we are not using this plugin. It used to work prior to 12/3/2018.

I had to rollback again today because this plugin keeps breaking our website. I called Siteground and got nowhwere. I don’t know what your’e doing, but clearly this plugin has not been tested thoroughly. I have now rolled back to Version 3.3.5. Will you please fix this plugin so it stops breaking our website? Thank you!

@jetxpert, yes, I experienced the same thing. A persistent warning, ours was about A3 Lazy Load. Apparently SG Optimizer conflicts with a lot of other plugins now. I had to rollback SG Optimizer to an earlier version in order to fix our website. At one point the website was completely broken, and everything fixed when I rolled back SG Optimizer, so I know that is the issue. I am not planning to update SG Optimizer for quite some time, until I can be sure they have looked into and fixed all of the issues that appear to be erupting today for users who did update. I am glad I could rollback and fix it in the short term.

• This reply was modified 6 years, 3 months ago by garrettzucker.

@hristo-sg, when I updated to version 5.0.2 on our website, I received several errors and finally the website broke, showing nothing. I had to rollback to a previous version of SG. I noted this in another comment here. The issues were solely related to SG Optimizer, no other plugin as when I rolled back everything fixed itself back to working correctly. Is there any way you can look into this? I had gotten an error notice before everything broke that SG Optimizer conflicted with A3 Lazy Load, and then everything seemed to not work, eventually breaking site until I rolled back to previous version of SG Optimizer. Currently back on 3.3.5.