Wordpres sucks!

Gutenberg is the future. I will definitely switch to it later in a few months, but for now, I’ve installed the classic editor. I think many people have a similar rationale.

@justatest47 You’d think so, wouldn’t you? But it appears we’re not dealing with a rational entity; we’re dealing with supreme arrogance and a cult-like adherence to The New Orthodoxy which leaves no room for admitting fault.

Wordpress is deaf.

It is that arrogance and refusal to listen to reason that, I think, is what galls people the most — the feeling that the WordPress autocrats are sitting on high pronouncing “Soon enough, the rabble will see the light.”

Then you have the dutiful drones turning up in these forums asking people to reiterate their problems with Gutenberg, as if a thousand people haven’t given a thousand reasons why it is a disaster. It’s insulting.

As many reasonable people have written, this Classic Editor should be the core default. Offer Gutenberg as a plugin for masochists.

• This reply was modified 5 years, 11 months ago by VeloVet.

Wonder why www.ads-software.com itself is not using the Gutenberg block editor? When i post a reply here i do that via what looks like a form of TinyMCE to me.

People, people, chill.

First, you are way outside the forum code of conduct.

Second, the core team is made up of people who give their time and talent for free and truly care about user experience. They make mistakes, sure, but that’s no reason to abuse them.

Third, I could see this coming a hundred miles out, so I … haven’t upgraded live sites. I have upgraded test sites, and when WP 5 is stable enough, and my tests all show that specifically for my sites, I will upgrade live sites. So you could avoid much of your own strife with good administrative practices.

They obviously do not care about our user experience, or they would at least listen before making all of our websites almost unusable for us. After this update, its obvious the people running WordPress do not care about users.

None of what you say is obvious. You can contribute to discussions in many ways (see https://make.www.ads-software.com/) and when you do, you will find out more and be kinder, I’m sure.

Also, you can restore the classic editor until you learn more about the new one, so what’s the problem?

I have come here to say that this plugin is the best I have seen so far. I use it on all my WordPress website. If there is some petition to make this plugin hardcoded in the WordPress core show me the link so I sign it.

Keep up the good work!!!

and thanks.

I appreciate that the WP team is working to make progress on a more advanced editor for users who want more features out of the box. But as I already use and am fully committed to a very advanced paid editor I have no plans to entertain Gutenberg.

Also, the new backend layout is very annoying as it is not what I’m used to. I believe they should have promoted the Gutenberg plugin rather than making it the standard install.

Anyway… I quickly found a plugin that will disable the editor if you are having any issues with it. https://www.ads-software.com/plugins/classic-editor/ or https://www.ads-software.com/plugins/disable-gutenberg/

Cheers!

So After testing, I found that only https://www.ads-software.com/plugins/classic-editor/ work for my install. Also, My gravity form shortcode generator will not work now.

The fact I have to install an un-necessary plugin to avoid the editor and that it could potentially break parts of my site is not cool.

Wow.. so after trying the disabler plugins I found that they left many of the classic elements un-operable. This is totally fxxked up. I will be reverting back to the previous version, luckily I made a back up right before the update.

Can anyone tell me what I should do to avoid this forced situation and still keep up with Security Patches?

• This reply was modified 5 years, 11 months ago by jeremybooze.
• This reply was modified 5 years, 11 months ago by jeremybooze.
• This reply was modified 5 years, 11 months ago by jeremybooze.

Every bit of new technology requires adjustment, and the block editor is no exception. Still, progress is a good thing and with the new editor, many things become possible, and many become simpler and can be delegated to non-developers.

Other layout editors cost money and TinyMCE was developed by another company, so the move to this new editor as the default is beneficial both for new users and for the WordPress community in general.

Also, existing layout editors can adapt (have adapted, actually) in various ways. Being plugins already, anyone can just keep using them as before, so what’s the issue?

The issue is that it forcibly rearranges the back end data fields.

As I stated some of the functions that worked before I can no longer locate or simply don’t work, such as the Gravity form shortcode generator.

If I use a disabler plugin it completely makes classic elements un-operable.

And we all know the more plugins we use the greater risk of conflict.

As I said… I support the advancements but it is my opinion that we shouldn’t be forced into using it as the default, especially in today’s age when there are many other solutions to use and this clearly makes some advanced changes to the WP core.

I just think there should be an option, in other words, a separate plugin rather than having it built into the default setup.

Make it as a pre-installed plug-in, but not build into the framework.

I’m sure third-party plugins will adapt and function properly in the future with updates as with my gravity form issue… But this may require me to purchase a new paid subscription, hopefully not.

In the meantime I will have to type out all my GF shortcodes or revert back to an outdated version of WP with out of date security measures, I’m not sure which is best.

• This reply was modified 5 years, 11 months ago by jeremybooze.
• This reply was modified 5 years, 11 months ago by jeremybooze.

Will https://docs.gravityforms.com/gravity-forms-gutenberg-block/ help?

Gal –

Thanks for the link. As I predicted I would be required to purchase a new business license which isn’t in my budget at the moment and not good news. But thank you for the follow-up information.

I can only hope that this is my only issue. Unforatnly the “Classic Editor” option plugins are conflicting with one of my many other current plugins so that is not a workaround for me.

I guess I will either compromise my WP version security for usability or update WP and type out all my GF shortcodes… lol. Not ideal when in the middle of development.

Thanks again. I understand there are many people calling these shots. I just would have presumed it best to leave things barebone with the classic WYSIWYG and leave the building blocks editor as an optional plugin.

Cheers.

Full disclosure: I have installed Classic Editor on all my sites and kept them on 4.9. Security and stability updates have been applied to 4.9.9, so there should be no risk remaining on this version until 5.0 stabilizes enough.

To resolve compatibility issues, it’s good to inform the authors of both sides of the issue. Good authors should respond within a few days with a fix and even communicate directly with “the other side” for best outcome.

Seems to be that GF should ensure backward compatibility of their plugin and as a licensed product, you should get a quick fix for this. Strangely, they already have a doc page for this (https://docs.gravityforms.com/adding-a-gravity-form-using-wordpress-5/classic-editor-add-form-button/), but no information.

This is how a community works. We share information and strive for a good outcome TOGETHER.

This post has gone a bit off the rails.

It’s okay not to like Gutenberg. It’s okay to prefer the Classic Editor. It’s okay to disagree with the direction of WordPress. Conflicts with other plugins is inevitable. It’s not good, but it happens.

If you have specific issues with specific plugins and WordPress 5.0, I urge you to open a polite support post for each plugin and let that community help you.

Since this post is no longer helpful to anyone, I’m closing it. I encourage you all to blog about your issues and if possible file bug reports so we can make it better for all.