Default buttons/controls for the new editor

With the ClassicPress Editor project moving along, I’d like to get some community feedback on the default controls placed in the interface. Here’s an editor to play with – it’s got most features enabled and includes far more than we plan to include in the final editor.

It would be great if you could play with the editor and then post your feedback here. Anything that you love or hate about it; anything you’d change or do differently; your opinion counts. You can even suggest a thing or two that you’d like to see included in the new editor which are not present in the old editor. Let your voice be heard!

6 Likes

I’m using my Android phone right now, and so I can’t yet play with it, but I’m glad that the Source Code < > button and window are still available.

I understand that the new editor might need to reimplement (simulate?) wpautop, but it would be great if this access to the HTML source code is left intact.

1 Like

Awesome work on this!

  1. The only real thing I wish we could add to the editor is “Find and Replace” feature. Countless times I had to do some sort of find/replace on the text. I had to copy it to my computer, do find/replace, and then paste it back into the editor. This would be invaluable to edit the content on the smartphone.
  2. The second thing that would be nice to have is the table of contents. Why add a plugin if the editor is already able to handle ToC? But that’s just me.
  3. I would also like to see UL/OL list selectors kept in the new editor. It’s a nice, quick way to have a bit more control over list styling without writing CSS.
  4. As a suggestion, the word/character count in the bottom right corner is clickable to switch between word and character counts. Who actually knows that just by looking at it? I think this needs some sort of UI change to indicate that it is clickable. Similar to +/- for collapsible content. Maybe a toggle?
  5. Keep the dividers for button groups. It looks nice and easier to understand what’s together.
  6. Lastly, it would be great if we could enable missing buttons with a filter. So we wouldn’t really need Enriched Editor unless the user needs a GUI for the filters.

Do we plan to do anything with TinyMCE templates? I assume not but thought I’ll ask. It’s a powerful feature, so if not the core, it definitely can be extended in a plugin.

Side note: All the dropdowns are very narrow, to the point that it shows 1 or 2 characters per line.

4 Likes

Looks like I got a little aggressive with my CSS rules. All fixed.

2 Likes

I’m currently using the enriched editor on a lot of my sites and I had a look at why I felt I needed it. The main feature that I really, really want (and why I installed it on many sites) is to have tables.

I think if you have nothing else new included in this editor then you should at least include tables. Being able to quickly whip up a table is a basic part of any word processor and it’s really versatile for doing simple layout stuff. I’m just not sure whether there are any theme-related problems that may arise form this.

The second most useful thing I would say is the find and replace button. That is also a very basic feature that we have come to expect as standard and is super useful.

So those two features would get my vote for inclusion by default. There was also talk about having some more features included that could be enabled using a filter (which is a neat idea - not readily available to the average user but can be added by the site admin). Obviously we can’t include every feature or it will be way too bloated. But I do like the code button that displays code (both front and back end) using a syntax highlighter.

I should also mention that I do think it’s important to have some new features included and a new “look”. One of the most common complaints over the years about CP is “But you aren’t doing anything. There is no progress”. People need to see something happening or they think the project is dead.

3 Likes

I’m trying to install (bot from the zip provided and cloning the repo) but all I get is this.

What I’ve done wrong? It’s happening on my bloated staging site and on a fresh install on tastewp.com.
Thank you.

I just pulled the main branch and it’s working on this end. Maybe try a hard refresh to ensure you’re not being served any cached data.

2 Likes

Solved using MAMP.
Thank you and… my plugin is starting integrating :partying_face:

3 Likes

Just tried it on a site with BeaverBuilder installed work as expected but if I try to edit in BB all editing facilities disappear.

1 Like

This thread is for discussion of buttons and controls for the new editor.

Issues can be reported here.

1 Like

Love it!
Paste as text toggle button and remove formatting are very useful and will help a lot with clients writing in word and pasting a ton of s**t!

Not closely related to this thread, but adding compatibility for one of my plugin vars, tiny5 branch has been pretty easy.

3 Likes

Discussion for this issue is here:

1 Like

Both of these exist in the v4.x editor.
Edit Page-classic editor

Tables should only be used for presenting data, not for layout. They are very persnickety to style generically so that they look good on all window sizes. Usually if you have data to put into your post, you would have a plugin that generates it for you or you paste it in from some external source.
Most authors only think of whatever window size they personally use and forget about the rest.

These filters have been in core for a long time, so nothing to do there.

For the styling. The result with no styling looks weird (to me).

It looks like a link to me… The one we already use doesn’t give the option for character count, since that’s not as useful.

1 Like

If I download and install this, will I still have all the basic functions of TinyMCE?

“Allegedly.” :smiley:

However, do note that this should not be installed on a production site.

Any idea when it may be ready for production sites?

There were a number of changes to the TinyMCE codebase from version 4.x to 5.x, so, much of the work is in converting/patching the old WP-specific TinyMCE plugins to work with the new editor code. Since the project is mostly JavaScript (and we’re mostly PHP programmers) there’s a fair amount of doc-surfing and trial-and-error involved. This does slow down progress to some degree, but, we are putting in the work.

1 Like

Will settings for the editor made via your WYSIWYG plugin be retained?

If someone opened an issue for it, I’m sure it could happen. The new editor probably won’t have all those features built-in, though. It will probably be similar to the current editor in functionality, and then someone will either have to port Enriched Editor to work with v5 or create a similar new plugin (both options are a fair amount of work.)

The better approach is to include everything in the new editor and give users a panel to add/remove features, just like Enriched Editor does. I’ve heard one concern that this will add to the download size of ClassicPress, but, other than that, I haven’t heard any other reasons to not include the extras.

I’ll be perfectly clear:

I am strongly against updating the editor only to tell users that they have to install another plugin to get at any of the new features that came with the update. In order to get users to buy-in to the updated editor, we’d have to develop both (the core plugin and the extension plugin) simultaneously – otherwise updating would cost them all their WYSIWYG features. Nobody is going to go for that and it will make this project flop. The Enriched Editor was my most popular plugin when I was managing it, and I think it’s safe to say that the majority are using it.

1 Like

It would be nice if each user could customize their own editor, similar to the option to disable visual editor completely.