Support » Everything else WordPress » Guternberg — Please Don’t Do This

  • I have just “upgraded” to the latest wordpress, and I must say — I had to immediately install the plugin for the older editor so I could continue creating content. I understand that not everyone knows, or wants to use, css/htnl, but — honestly — making it impossible to do so is utterly beyond me.

    I have specific css classes I use for specific things, and specific snippets of code I use for specific kinds of content. I’m certain I could figure all of this out with these new “block” things, but — really — why???? Give me back a text editor mode, and allow me to use my own custom css classes without being forced to jump through the “simple hoop” that turns out to be more complex than it’s worth.

    This is a horrible interface. When wordpress stops supporting my ability to see the actual html in the post, then I will switch off wordpress entirely. I know most people want to publish without understanding the underlying stuff, and I understand that wordpress wants to separate the world into content creators and developers, in order to grow the developer market as much as possible — but — just stop this. Now.

    • This topic was modified 11 months, 1 week ago by  Steve Stern.
Viewing 15 replies - 1 through 15 (of 18 total)
  • It’s an official part of WordPress 5.0 and isn’t going to ‘stop.’ But you can install the Classic Editor plugin to return to the editor you’re familiar with.

    It might not “stop,” but it will, ultimately, make wordpress into a medium look-a-like, which will destroy the user base. Which just means wordpress will stop being a widely used platform for anyone who actually cares about what their blog look like. So, in a sense, it will “stop,” because wordpress will no longer be a platform anyone cares about.

    That may or may not turn out to be true. Meanwhile, this is a support forum for technical questions, and if we can help, let us know.

    Ummm… I’m already working on dumping wordpress, and I know a ton of other people who are, as well. Beyond that, this is not “just a technical forum…” It specifically says “complaints” at the top.

    I am complaining. A lot of people are complaining. Apparently wordpress does not want to listen — and we know what happens to companies that stop listening.

    Really, people are complaining?! There’s been a full year of discussion by hundreds of thousands of people on this change to WordPress, but I haven’t heard a single person say anything except that they absolutely adore the new Gutenberg Editor, and that they are 100% committed to using WordPress for the rest of their lives. The reaction across the entire WordPress community has been to embrace Gutenberg with open arms with a sense of complete and utter agreement.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Plugin Review Team Rep

    People are allowed not to like things, and they’re certainly allowed to complain. Everyone’s experience is different. Don’t berate each other for being different.

    @riw Have you tried using the classic editor for now? Adding in custom css and styling is going to improve, but you’re right, it’s not as flexible as raw HTML would be.

    I agree, Mika. I certainly wasn’t berating anyone, and I don’t think that was your intent either.

    @ipstenu — I am using the classic editor plugin for right now, while I work out what platform to move to. I have read the statements on the part of wordpress about discontinuing support for the classic editor over time, and forcing people to use the new page builder interface, which also means being forced to use react, and hence putting a full development process in place for simple changes.

    I understand wordpress is trying to “move into the big time,” and compete with simpler platforms. In the process, however, it is becoming more of “me too,” and less of an interesting platform. It is becoming more of a place for site developers, and less of a place for individuals who like to build a blog that is both simple and unique. In essence, it is moving away from being a local boutique to being mcdonald’s — serving up bland overcooked (but pretty) junk instead of real products.

    I’m certain there’s a lot of money to be made in this change. But making lots of money is not the same thing as building and supporting a community. Whether or not this is good for wordpress as a company — and that is part of the problem here — a company who wants to takes what they perceive to be a captive audience down a path that will extract more money from them — is one question.

    However, it’s clearly bad for the community, it’s bad for the ‘web, and, it’s ultimately going to be bad for wordpress. There is money to be made in exploiting the platform, but once people get sick of being exploited, they will move on to something different that does support a real community, rather than just professional developers.

    I would suggest you both brush up your resumes, or save the tons of money you’re going to make in the transition. This is a train that will eventually crash, and is going to harm a lot of people while you’re driving it down these tracks. But, whatever — people don’t matter, just the money, right?

    You want to support the community? Instead of creating a forcing funnel that turns the temp up on the pot slowly, give people who don’t agree with your vision the tools they need to smoothly move to another platform. This, at least, would be honest to the community you are exploiting for monetary gain.

    Could you explain why I should brush up my resume? I’m just a WordPress user.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    @riw Let’s keep the topic here, OK? I’ve archived your reply, you do not need to bring other people’s web site into your conversation.

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    This, at least, would be honest to the community you are exploiting for monetary gain.

    WordPress is offered for free, developed and supported entirely by volunteers. Your suggestion that there is something to be monetarily gained or lost, or that people need to “brush up their resumes” is very off base and verging on the line of personal attacks. Do not continue that.

    These are support forums. If you need support with something, please let us know. As for concerns over the editor, I’m afraid that ship has sailed in public development discussions (that everyone was welcome to be a part of) over the past year and a half.

    I understand you’re upset, but there’s really nothing to do at this point expect all work together to make WordPress even better. You can follow along and participate with development at https://make.wordpress.org/core/ and join other efforts at https://make.wordpress.org/

    Everyone is entitled to their own opinion, but not seeing all the negative comments about Gutenberg during this year – wow, that must have been fake news then.

    At the time I gave my comment about the plugin I said that WP clearly thinks it is too big to fail. And even though you replied, on the contrary that is not the case why we are doing this, you certainly have acted like it.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Well, conversation aside:

    Give me back a text editor mode

    In the new editor, if you click the three-vertical-dots icon in the upper right hand corner of the page, in this menu you will find a Code Editor. This will give you the straight HTML view of the post.

    Alternatively, you can use the Classic Block, or the HTML Block.

    and allow me to use my own custom css classes without being forced to jump through the “simple hoop” that turns out to be more complex than it’s worth.

    On any given block, select it, then select the Block option in the right hand sidebar. At the bottom, under “Advanced”, you will find a field for “Additional CSS Class”. You can type in whatever classes you want here, and they will be added to that block, and you can use them as references for your styling.

    People tend to judge the “Bebo” update. Well, you can still edit the WordPress post/page using HTML/CSS codes.
    Personally I like the new update, but yeah…this is my opinion.

    Cheers

    Thanks for the tip on finding the rather well hidden source code. Note that since a long time ago, if you switch to the visual editor, any custom css/html you place in the post while in the text only mode will be removed by wordpress. I tried your suggestion with the “block editor” (which needs to be renamed, because it’s not an editor), and it does the same thing.

    For now, I’m going to leave off this thread and focus on finding another solution, as it’s obvious those who care have already left the conversation. I will begin by canceling my wordpress.com professional account, and I will urge everyone I know who uses wordpress to do the same. If wordpress.com dies, perhaps the original project will be returned to the community, where it can be brought back to its original principles.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Guternberg — Please Don’t Do This’ is closed to new replies.