VegasWill

Temp domain so I can leave it as is for now…

Both Menu and Wine worked before.
https://willp9.sg-host.com/menu/ (2.8 broke it). Pod name: “Dinner Food Item”
https://willp9.sg-host.com/wine/ Still works (in toggles) Pod name: “Wine”

Same code on both.
I had previously placed the Wine on the Menu page without the toggle and it worked fine. Just an issue with the “Dinner Food Item”

I hope this helps.
Will

Thank you!

Thank you.
But it’s the redirect that I want gone. I still want the page indexed.
How do I get rid of the redirect in the sitemap?

Thank you!

Thank you!

I must say I love this plugin as well, but this happens to my clients websites all the time. Usually after an update. The last update, I just went to all of my clients websites that were using it and I’d say 4 out of 5 had to be purged to fix this issue.

The site looks like all text, no background images, sometimes no images at all. It just needs to be “purged all”. But it’s very frustrating when a client calls me that their website isn’t looking right. I have uptime software checking it, but it doesn’t always work as some only check for text.
Is there a way to purge nightly?
Thank you
Will

Thanks

Thank you!

Closed

Forget it. User error! I fixed it.
Thanks

@clorith
Sure. Not sure how you want me to handle it. If you’d like, you can speak about it on my review.

Hi @clorith and thanks for jumping in.

Many who contributed stopped posting here last week.

I will remark that out of tens of millions of sites, only a handful have expressed public dismay (at least here on www.remarpro.com

How many of those 10’s of millions know they can complain on this plugin page? How many have actually upgraded?

Have you checked how many are using the Classic Editor plugin? 1+ million and rising fast.
Disable Gutenberg is over 50k.
Don’t you think that says something about how the community feels?

If they aren’t complaining, they probably don’t know where to go, and it doesn’t mean they’re happy.

Where is the official place to vent concerns that you’re checking? When this was a plugin, did you see the horrible reviews it had then?
It’s at 2.1 and falling.

Again, nothing personal Marius. You seem very nice. But if you guys think people are happy, you’re simply not looking in the right place.

Check the Classic Editor plugin. Over 1 million downloads.
I wish they would just admit Gutenberg was a mistake.

@designsimply Sure.

You’re exactly right @todorchristov
I’ll bet someone supporting Gutenberg will jump on here to tell you how easy it is to do what you want.
All you have to do is: Hover in the place you’d never think you’d need to hover on, then click, you’ll then see a 3 dot menu, then click it to be surprised on what it does/doesn’t contain as you might need to click something totally outside of the block, then click the 2 rotating arrows, click the…..AHHH.
“See? It’s easy and makes more sense than the old editor, right?!?!!”

Try floating an image left or right in that text and you’ll have a blast.

Same issue if you have to put those paragraphs in a div and they cross blocks.

This is absolutely terrible.
They’ve said they used User Testing, but clearly it was flawed, they ignored it, or thought they knew better, or we’d all love it.

@designsimply You seem like a sweet person and I’m sorry you have to take the brunt of this, but (haha)…..

You posted above:

It’s interesting about the code editor because there is some thinking around the idea that it’s nice for developers

Yet in a the past post “Neither intuitive nor ergonomic.” you commented:

One of the main goals for Gutenberg is to work better for users without computer skills such as knowing how to code HTML.

WordPress’ popularity is with developers AND newbies already. It that it was as easy or as technical as you wanted it to be.

There is a ton of frustration with the old editor

Really? Where were they last? WordPress being 32% of the whole Internet? The editor being the primary thing people use. If it was so frustrating, how did it hit that 32%? There are plenty of alternative Open Source projects out there yet people and developers flocked to WP over the years.
Also, the classic editor plugin already has over 700k installs.

Keyboard Shortcuts
You’ve also responded to people about keyboard shortcuts. Do you know the % of people who prefer keyboard shortcuts over the mouse? It’s not even close.
Remove the back button off a browser and you’ll see a revolt. People don’t want to use the back key to go back a page in their browser. Most of us have a mouse and would like to use it without going through hoops to achieve what we used to be with one click.
The main problem with keyboard shortcuts is that they are not visible. The old editor had both. Now you have to hover correctly, then click the right area.

If it were that intuitive, why do we still have buttons for the WYSIWYG in the comment box I’m writing right now? Why not get rid of the “b”, the “i”, the “link”, and the rest? Why not just make keyboard shortcuts?

People are busy writing and coding, now we have to forget what we’re doing and think about the editor, or remember keyboard shortcuts (which beside copy, cut and past, I never use).

To delete a paragraph, you can also simply press the backspace or delete key exactly the same way you would in the classic editor.

You didn’t read my post. When you only have <p></p> showing in the text html (nothing in between as it’s been deleted). You can’t simply use the backspace to delete it along with the block. It won’t. You have to switch back to visual, then delete, or go through the steps I’ve outlined above.

User testing was done, and is ongoing, for both editors.

So why do you still need examples of why people don’t like it? WordPress should have already have known they’d get this response and what the issues were if the proper Usability testing was done.
This is your testing right now.

I hope this isn’t a case of “being right” is more important than “doing what’s best”.

Again, nothing personal @designsimply, you’re very nice to put up with some of the attitude here (including mine).
Thank you.