Beep Beep Boop screen is a joke. Is this a glitch?
-
In the “Classic editor” it was easy to decide and modify what to post to Twitter and whether to post to social media at all. The new editor defaults to pushing content to all of them. NOT what I want.
The new editor makes me seek out “advanced” options like setting my own slug, the excerpt, etc. These were easy and put on the screen in an condensed and easy way in the classic editor.
I could edit information about images easily in the old editor. I could schedule posts easily in the old editor. Ditto for tags and categories. I could try different search terms in Zemanta in the old editor.
So far, all I have seen are features that are either gone or made much harder to access — and an irritating slow Beep Beep Boop image in the new editor.
Why is WordPress making the large number of people who do have a full computer live with all the limitations of a tablet?
I have used WordPress for college teaching for years, and was planning to do so for Fall Semester 2014. All my lesson plans are out the window, and things the students need to learn are now harder to find. I can’t believe this stupid change was made with so little warning or input.
-
Please note, clicking “New Post” in the upper right-hand corner will continue to link you to the new editor.
WHY?
Also – what about editing posts? I don’t want to edit in the new editor and don’t want to wait for 20 seconds before I can switch to the old one?
Btw I challenge the people behind the new editor to try and edit a 2000+ words post in it… or just type a 2000+ words posts.
Like this one for example – http://strangera.com/2014/08/21/games-in-2014-part-2/
Try editing something like this in the new one, then go back to the old one and come back here to give me your honest opinion about the new vs the old editor. -
@jeremeylduvall, this is referring to your note above, asking bloggers to go to Inspect Element.
I am now getting really concerned about the state of affairs at WordPress.com. Are you really serious, asking bloggers to go to Inspect Element?
9 out of 10 people blogging as publishers, would not be technical enough to be poking around such advanced settings of the browsers. Let alone, they’d want to even follow the technical directions of such types, instead of concentrating on their work. I am somewhat technical, and even I would not want to follow such type of technical troubleshooting nightmare.
What you and your team, as developers, have not been able to follow, is very simple from our perspective: we seek simplicity and we seek non-intrusive, clean environment. The TinyMCE compose editor which you are tinkering with, has been working fine across the board everywhere. But it is only here at WordPress.com, where it is being made to complicate, to supposedly accommodate some unknown goals.
As developers, with much technical powers, you are alienating your average user-base with not just this anguishing thread, but also by making us go through your experiments of trials and errors.
-
All the arguments in favour of the classic editor, all the objections to what the developers ask of us, will be in vain. since first named follow a fata morgana called “progress” – which means: “we fix it even it ain’t broke“.
-
No, mabelamber, they ONLY ‘fix’ it if it ain’t broke! I call it disimprovement, my word for when something which claims to be an improvement is actually making things worse. It is a trend which seems to be sadly on the increase.
-
Hey, Happiness Engineers: This thread can’t be any fun for you. Even if you’re all convinced that we’re the ones who are wrong because we don’t appreciate the brilliant new Beep Beep Boop editor, do yourselves a big favor so you don’t have to listen to our continuous griping. Just tell us that the “classic” editor will not be removed. Just leave it alone. Besides solving our problem, you’ll have less work to do.
-
Beep Beep Boop goes hand in hand with the “Hello Dolly” plug-in that comes with every WordPress.org installation: annoying and unprofessional.
-
@ travelgalcindy
The cookie is there, but the browser keeps defaulting to the new one (whether I’m creating a new post or editing an existing post, although I’m guessing you are going to tell me that there isn’t any way to change the default for editing existing posts).
Editing existing posts should be defaulting to the classic editor as well if you’ve chosen the opt out. The only thing that will consistently default to the new editor is clicking “New Post” on the right-hand side of the admin bar.
I’m using Firefox. I don’t use other browsers (I have someone check for format problem in others). My cookies seem to be turned on.
You can check under Firefox -> Preferences -> Privacy. Please make sure “Accept cookies from sites” is checked.
I also have the issue with all the pictures loading small, even though the default I have set for my template, which works in classic mode, is set to load them full size.
Could you clarify a bit more? If I understand correctly, when you insert an image into the new editor, it’s inserting at a much smaller size regardless of whether you choose thumbnail, medium, or large when inserting. In the classic editor, inserting that same photo gives you a larger image. Is that correct? Could you point me to a post on your site that you recently editing/added where this occurred?
I’ve checked in both Chrome (Version 36.0.1985.143) and Firefox (Version 31.0). The cookie is shown in both. Nevertheless, in Chrome, when I start on my home page as I always do, go to the drop-down menu and click New > Post, I’m still sent to the BBB screen and new editor. (If I only click New, I’m sent to the old editor.)
That’s certainly frustrating! Both of those links should be going to the classic editor. The only link from your Dashboard going to the new editor consistently is the New Post on the right-hand side of the admin bar. I’m not entirely sure why “New” and “New -> Post” are going to different places. I’ll see if I can figure this out for you!
I can’t duplicate this in Firefox because since the new editor was introduced, the admin bar does not show on my home page.
Just to clarify, when you say “home page”, are you referring to WordPress.com or your Dashboard at mysideaddress.wordpress.com/wp-admin? Sorry! Those are just used interchangeably and I want to be sure we’re on the same page.
My biggest gripe is still that there’s no bypassing the BBB screen when I want to edit a published post, and it takes longer for BBB to load than it does to do a quick edit.
From the descriptions here, it sounds like the cookie isn’t getting properly set for whatever reason. The “Edit” links should take you to the classic editor if you’ve opted out. I’ll keep digging!
In short, using Markdown with the new editor is simply unworkable. The old editor worked well enough as long as you stayed in the Text tab. The new one will even do things like wrap your post up in fresh HTML tags, thus changing its formatting and meaning.
Thanks so much for the detailed post here including screenshots. I was able to reproduce this on my side and will be reporting this issue!
Yes, 675px wide images inserted at ‘full size’ get squished to 660px wide in BBB on both http://geotopoi.wordpress.com and http://lustrebox.wordpress.com/ This does not happen when editing posts on those blogs with the classic editor.
I was able to reproduce this as well. The new editor added a w=660 to my image. However, when the image was opened in a preview, it appear full size (well, it was truncated based on content width). Are you experiencing this as well or is the image only appearing 660px?
-
I was able to reproduce this as well. The new editor added a w=660 to my image. However, when the image was opened in a preview, it appear full size (well, it was truncated based on content width). Are you experiencing this as well or is the image only appearing 660px?
Yes, BBB creates the following in ‘Text’ view when a 675px wide image is added ‘full size’
[caption id="attachment_9124" align="aligncenter" width="660"]<a href="http://geotopoi.files.wordpress.com/2014/08/portmeirion-20140820-18-traeth-bach.jpg"><img src="http://geotopoi.files.wordpress.com/2014/08/portmeirion-20140820-18-traeth-bach.jpg" alt="Traeth Bach" width="660" height="432" class="size-full wp-image-9124" /></a> Traeth Bach[/caption]and on preview this is rendered as:
<div id="attachment_9124" style="width: 670px" class="wp-caption aligncenter"><a href="http://geotopoi.files.wordpress.com/2014/08/portmeirion-20140820-18-traeth-bach.jpg"><img src="http://geotopoi.files.wordpress.com/2014/08/portmeirion-20140820-18-traeth-bach.jpg?w=700" alt="Traeth Bach" class="size-full wp-image-9124"></a><p class="wp-caption-text">Traeth Bach</p></div>So on preview the image is rendered full size but overspills the undersized Caption background.
-
@eremeylduvall
By “home page” I mean the home page or front page of my blog. That’s my starting point for everything. With the admin showing at the top of the page, I’m ready to work. But for whatever reason now, the admin bar does not show on my home page in Firefox. Not an emergency because I always work in Chrome, but it needs to be fixed eventually.
Just to clarify RE the edit screen for a published post — I can get to the old editor by going to Dashboard > Posts > All Posts, looking through 2,400 posts to find the one I want, and then clicking “Edit” under its title. However, if I click on the edit button while viewing the published post (the normal way to edit something), instead of the classic edit screen instantly appearing, I get the BBB screen and new editor. Both approaches are slow and tedious and neither is acceptable when all I want to do is a simple tweak like adding a comma.
-
-
WordPress, why don’t you just admit defeat and scrap this thing you’ve created and let us all start posting again without any of these frustratingly slow screens and faults.
Or is there something deeper going on behind the scenes.
-
I moved my blog (and taken my business) to Blogger. I’m not the smartest cookie in the bag, especially when it comes to editing code. I just can’t do that.
I’m finding that Blogger is simple, you can drag and drop photos and edit to your heart’s content. It stays the way you want it, and you aren’t treated as if you are five years old.
The one problem I have with Blogger is that it’s difficult to find the dashboard, but once you have it, you’re in.Thank you, Word Press, for making me get off my lazy butt and move to a far more responsive team. No more angst, no more stupidity foisted on me.
Oh, and I’m taking my money with me. -
wildhairyhaggis, there is something deeper going on behind the scenes.
It’s called ‘change for change’s sake’. I also smell a lot of Developer Ego.
They aren’t listening to us.
There’s a proverb: “The more you over-tech the plumbing, the easier it is to stuff the drains.”
I just flushed Word Press. I feel so much better. -
-
I can only add to the disappointment expressed above with this “improvement”.
I always delete cookies when closing Firefox. Setting a cookie for defaulting to classic is therefore meaningless.
The bleep bloop also rotates endlessly unless you allow Google, googlemaps and gtstatic to run scripts. But you *have* to reach the new editor to be able to change to classic. So every time you have to first allow all Googles works just to disallow them again after finally reaching the classic editor.
Well, as a makeshift solution I have set the classical editor as my starting page which leads me directly to it after logging in. I wonder for how long.
-
One thing at a time.
You can check under Firefox -> Preferences -> Privacy. Please make sure “Accept cookies from sites” is checked.
Not sure what version of Firefox you have or where you would go to check that other than the menu bar at the top, but I don’t have a “Preferences” tab/menu or an “Accept cookies from sites.” I do have a “tracking” tab, which is on and all my logins and such are being saved, which SEEMS like cookies should be on and I can see cookies have been saved in Firefox, so I have to think they are. Has something changed where Firefox is not reading whatever type of cookie WP has embedded?
I thought maybe this was linked to the fact that, for whatever irritating reason, I have a different “default” blog address listed than my primary domain. However, that seems to be a separate problem for another day, as I went into my other blog (that doesn’t have any weird naming issues) and I can’t get that one to hold the classic editor as the default either.
For what it’s worth, both blogs use my own domain name.
My main blog is http://explorationvacation.net – I also have a new blog I’ve started at http://playingwithphotography.com which uses a different template. As I noted, neither will hold the default setting.
I’ll come back to the photo issue after my next post so I can track what it is doing.
-
Not a bug report (for once), I just wanted to add that for me (on FF 31 and Win 7 Pro), after opting out of beepy-boop, clicking on a post’s “edit” link does take me to the classic editor . So it isn’t that opting out doesn’t work for editing, period, it is working for some – but obviously not for all, which to me is just more proof that cookies really aren’t a good solution for this.
-
isn’t this all a crashing bore? Other companies release properly orchestrated updates that are actually welcomed.
-
Thanks for that info. I’m glad to know the edit link works for some people and takes them directly to the classic editor. But now I’m even more unhappy knowing that I’m one of “jinxed” for whom it doesn’t work. Of course, we’re talking about a workaround that will eventually go away and leave us with only the new editor. And that’s the saddest thing of all.
- The topic ‘Beep Beep Boop screen is a joke. Is this a glitch?’ is closed to new replies.
WordPress.com Forums 