Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Got a similar issue but no solution. Pagespeed doesn’t error on all checks but only on the image checks. Very frustrating, only happens on one site. Images load fine and are correctly converted to webp. Did you ever find a solution?

    @gkahr78 thanks for the more detailed explanation. We’re on the same page here. I myself do have to learn new tools everyday. But how or why should someone else decide what these tools had to be? They don’t know the problems I need to solve.

    I chose WordPress for a number of reasons, one being that it’s a PHP framework. I could have chosen a Node-, JavaScript or any other framework or language. This developer somewhat implied that us peasants blindly overlook what great tools are out there. A bit like baptizing. This makes no sense, there were over 1000 proogramming languages out there last time I checked. And countless frameworks for each. I know a lot of them, have major programming experience in 6 and minor in some more.

    WP-Devs need to learn Kobol, Go and BF if you ask me. And write the new API in Assembly, it will run 4500% faster.

    I also don’t get this “deal with it” attitude. No, why would we? We’re more. We made you successful. We don’t want this. They’ll learn to adapt. 😉

    @gkahr78 not sure what you call “condescending”, please elaborate.

    Well classicpress has been around for a while. I sincerely hope it will be “the” fork. But atm I find it too early to put my client’s sites all on that one card. I definitely hope there will be an official rollback with Gutenberg and furthermore Node.

    Not trying to “talk you out of this” but I see a chance this is not related to Gutenberg (if you see my other posts and ratings you’ll know my opinion about “Gutengurg” as you called it 😉 ).

    May it be that you’re using Firefox? We’ve tracked a very similar issue down to Firefox (or a conflict with WP Core <> Firefox) and found that it goes away completely if you try the same with Chrome, Opera or Edge.

    I wonder if Askimet really represents the number of *active* WordPress installations because it ships with WordPress. I alone have 10+ inactive WP installations hovering around all of the time, used for development and experimentation.

    Classic Editor on the other hand has to be installed manually, that means 2+ Million buttons have been pushed to get it and to get rid of Gutenberg.

    It might be we’ve already passed the 50% or even 90% mark of ACTIVE WordPress installations opting out of Gutenberg.

    Classic Editor Installations: Overs 2 million right now! Last time I looked before xmas it was 1 million.

    https://wordpress.org/plugins/classic-editor/

    @pbarthmaier Why are you guys so much in denial? We do not want this thing. You can go back to make Gutenberg a plugin and remove it from the core. What do you expect to happen, that users & devs will just stop complaining and accept it? It’s not going to happen. The persistence which the WP Team has about Gutenberg makes me wonder if a deal behind the scenes with a big player is going on.

    What I really find fishy is the fact that core team members started to contact plugin devs to tell them they should make their plugins compatible with Gutenberg. If you search around you’ll find what I mean.

    I find their acting strange as well. They cannot ignore the whole community. Reading some of their answers to the massive downvote of Gutenberg tells me they weren’t prepared for this to happen. We shouldn’t stop to speak up. Do not just install Classic Editor and call it a day, take action. Write to them. Write your opinion here. Post about on your blog.

    bortran

    (@bortran)

    Thanks for some insight, @talldanwp

    As I said, I can do JavaScript pretty well, on top I’m working with JQuery and REST on a regular basis.

    But here’s the thing: The “advertisement” for Node and React made by WordPress claims that things would be way easier for programmers, I can’t see how that’s supposed to be true. Node and React introduce an amount of overhead I haven’t seen in a while. Let alone the need to compile* and pack stuff each and every time opposed to modifying a few lines of PHP within the WordPress Editor.

    And the promise that “beginners just have to learn a bit JavaScript”, pop open a text editor and code away with Node and React is purely made up fantasy. That’s not how any of this works. These frameworks* are complex and take a very long time to understand in it’s whole, to be able to make sense of it.

    Besides: No one of us asked for that. If we wanted to use Node, React, Django or whatnot we could have done so. Please forward my suggestion that the Node-lovers in the team make their own WordPress. I already suggested the name WordNode. It’s catchy.
    If you asked me on what other language to bring into WordPress I would have said Python. JavaScript is horrible for serverside code.

    Can you tell me more on what’s the roadmap? I’ve read up next there’s the widget area going to be removed, meaning it will be brought into Gutenberg. That makes again no sense to me, cause widgets / sidebars are global settings and I cannot see how a site-wide sidebar should make it’s way into a single post or page.

    (*speaking in common language)

    • This reply was modified 10 months ago by bortran.
    Forum: Plugins
    In reply to: [Gutenberg] THIS IS AWFUL
    bortran

    (@bortran)

    Or are you on WordPress.com?

    I’m sure she’s talking about that. No clue actually about the state of things over there, never used it, cause I’m coding sites myself. It must indeed be horrible to be forced to use Gutenberg just for posting itself (we coders have our own objection to it).

    I think most of us didn’t yet realize that there’s people who can’t just install “Classic Editor” and forget the Gutenberg-catastrophy for another year or two.

    @elleinad7 Maybe try to self-host your site then you can deactivate Gutenberg. I can help you a bit in this thread. Not sure though if you can export your existing content away from WordPress.com. But if you can, I’ll have a way to import it back to your self-hosted WordPress. Same goes for the domain, if WordPress.com is giving it away I can guide you through registering at any hosting plan you like and move it there.

    • This reply was modified 10 months ago by bortran.
    bortran

    (@bortran)

    @djcowan 100% what you wrote.

    Although I never expected WordPress to be an enterprise CMS, that’s a bit extreme end of the spectrum. My clients are small to medium biz and I’m the one providing a better product than the usual “here’s your visual builder theme that takes 3 seconds to load, deal with it”. All custom made, lean, fast. I sense the people with “enterprise” in mind may be found in dev-team Gutenberg.

    I had exactly the same thoughts as you after I posted my last reply: 10 years of deployed websites, how could I possibly rewrite these in a year? Same with the training: I’m doing exactly the same thing, it’s part of my product.

    Security risk of outdated sites will fall back on us, hard. We’ll have to deal with it, the clients only make the call. Not an option for me.

    I’m not even sure where to go with the sites I’m making right now. Add a “best before 2021” label?

    I think the WordPress devs have their heart in the right place but didn’t think their descission through on all ends.

    My xmas wish: I hope some people will see the issue as we’re seeing it and will continue to support the WordPress / Classic Editor (and what maybe become “classic” anytime soon) on their own basis. I’m willing to pay for it, but still, branching usually isn’t good.

    bortran

    (@bortran)

    These foundational elements will pave the way for stages two and three, planned for the next year, to go beyond the post into page templates and ultimately, full site customization.

    https://wordpress.org/plugins/gutenberg/

    […]So if you’ve written a plugin in PHP and want to update it for compatibility with Gutenberg, then it’s not going to be a simple task.

    https://premium.wpmudev.org/blog/future-of-wordpress/

    So I have a full year to rewrite each and every custom website and plugin I ever made? How on earth am I supposed to do that? With a new API that isn’t even developed yet? Who made this genious plan? Customers gonna sue the crap out of me once my sites are no longer supported.

    Best case: Schism – there’s gonna be a WordNode and a FreePress GNU version.

    bortran

    (@bortran)

    @djcowan Can you explain some more how this all went down? I obviously didn’t realise what Project Gutenberg is until it’s too late now, cause I was envolved in bigger project and same time study for my Linux Engineer exam.

    Node.js.. (c) Google Inc.
    React.js.. (c) Facebook Inc.

    Suddenly unstoppable in the most successful CMS. How did it happen? Nobody cared? Cannot believe it.

    • This reply was modified 10 months ago by bortran.
    bortran

    (@bortran)

    Yep. If they kept Gutenberg as a plugin nobody would have ever cared. But this “in your face” approach was prone to get feedback like mine and thousands of others.

    But now I’m really worried about the future of WordPress. What’s on the roadmap? Move to Node.JS / React entirely, because “it’s better for you peasants, you clueless folks”??

    See, it’s not only the editor, it’s the entire development and therewith my own future. And I’ve seen a lot of these “hipster” frameworks come and go, Django, RoR, younameit. All “so much better, build a whole CMS in 10 minutes from scratch”, remember? Now look in the job listings, still any Django or Rails jobs? Not in my Country. These things are awesome for big companies that develop their own stuff in big teams. But no good for average-Joe haircutter that needs a good custom website built for less than a $500.

    On top, I’m not anti-Node.js per se. I – not like that I’m maybe forced to use it in the future. From my admin point-of-view: I like what we established, a fast and lean Linux with Reverse Proxy, Apache2 and a ton of optimizations, also for the “not so optimized” PHP code – a lot to learn for me to understand and maintain, but now I can configure everything like the client wishes. Toss it all for all-in-wonder Node.JS webserver? Not gonna happen, like ever. LAMP is a world-wide established, super-stable and standardized platform every Linux admin can maintain. Node.JS is the cool new kid in town right now and maybe forgotten tomorrow.

    2cents as usual.

    Thanks Frank,

    I found it now, you might want to look into this. It’s been Yoast SEO that stopped Autoptimize from working. I think it came with the last update of either.

    I have also AMP support via a Plugin & Yoast / AMP Glue. Deactivating these two however didn’t do the trick but it may be related.

    Cheer,
    Bernard.

Viewing 15 replies - 1 through 15 (of 27 total)