Well, it says it on the tin. Is it a nice to have, or essential that you don’t have?
I think it would be really nice to have - all modern editors have some forms of it.
I think it’s essential.
1 Like
THIS ^^ 
cu, w0lf.
Not at all important to me. I’d prefer a conservative approach. Cut the ties with WordPress, fix known issues that never got solved.
Which “issues never get solved"? If you’ve been following ClassicPress for any length of time, you’ll know we’ve addressed a ton of them, with more to come. If there’s something specific you’d like done, say so. Sweeping generalizations are both inaccurate and unhelpful.
I think you misunderstood me.
I wrote fix known issues that never GOT solved 
in WordPress
No, I have not been following ClassicPress. I just found it. And it’s a relief to just pull open the old editor and have it quick to load, quick to save.
I am not aware of what bugs you already solved. I just knew there are/were a bunch, including one that got reintroduced when the customizer was built, I’ll see if I can dig it up later.
1 Like
…ok, let me quickly recap: CP is way faster and works better, because first and foremost some of WP old bugs were indeed solved (GitHub is a great place to see which ones). Also it got a makeover in the old JS libraries like JQueryUI and bacnone.js that we are very near to get completely rid of (Tim is reworking the customizer engine completely in PHP so that we can get rid of backbone.js completely since it was already removed in all other parts of core. that will make customizer more easy to maintain in the future). Next we will work on the editor, and the question here was pertinent to it because undo/redo is in all modern ones.
It’s not all but it’s a general idea of how far CP has gone in terms of improvements.
3 Likes
Hi Anand,
Which issues? I’d like to understand everyone’s point of view.
I have this idea of selectable tabbed templates. But there’s no need to force everyone to have a gigantic plugin if they really just want simplicity and also any fixes I might include in that concept. And, I could start “small” and target a specific super light-weight plugin, that delivered just that minimal concept with a very minimalist button design, and one of two options, perhaps?
I was stunned when, for the first time ever, I had a server that hit 100% on my hosting platforms speed test. Love at first sight and a target to keep.
1 Like
You know, to me the biggest strength of WordPress was and still is the hooks and actions system. And the fact that, thanks to it, I can enable/disable what I want. Downside is of course that you have to search for a plugin in the ocean of available plugins but upside is I don’t have to configure CPT unless I have it installed. Same for WP Super Cache, Yoast, Nginx Cache, Post List, etc etc.
Then WP started merging plugins into core.
ClassicPress has rejected the Gutenberg editor. Agree big time but: Is that it’s sole raison d’être? In that case, what’s stopping you from merging Elementor into your core? Don’t get me wrong, you can do with ClassicPress whatever you like, I just have these tiny plugins that don’t matter much to the ecosystem anyway, who am I to say what is wrong or right. But I was wondering what the deeper philosophy is.
Personally I would say: “If it could be a plugin then it should be a plugin.”
I’d be interested to know your perspectives on this, and the consequences it could have. Will functionality that should in hindsight have remained a plugin be moved back out of CP core? Mind, WordPress 1.0 didn’t even have Pages, those were added in 1.5. Could have also stayed a plugin, especially after custom post types and taxonomies were introduced. (Not saying it should, just could.) How “classic” should ClassicPress be?
PS my ticket from 11 years ago was closed as duplicate and the other was created 8 months ago and last updated with a patch 8 months ago. Not merged into WP yet.
ticket/32918
@Venutius your original post didn’t mention the word “plugin”. I had therefore read it as “do we need it in core”.
@anaid he was asking about editor because one of the next thing CP will tackle is changing editor to one with modern Vanilla JS instead of TinyMCE if possible, that editor will be WYSIWYG so no blocks since CP promise is no blocks ever. Various community members are exploring the feasibility of using one editor or another (there are many that might fit CP’s needs), while @Venutius and others if I am not mistaken are testing what it would take to code CP’s own editor to use instead of TinyMCE. TinyMCE is going proprietary and towards a paid system, CP has a very outdated version of it exactly for that reason.
That is why they were asking about undo/redo. they are building a proof of concept and wanted to know if that feature is needed since it obviously requires some code to manage the state of the editor/saving to db and all the other CRUD needed to make it happen (like a way to memorize things you did and be able to revert them).
You can see some people answered that undo/redo in editor for the future is a great feature to have, this means whatever type of editor we will use we will have to take into account that preference because people feel it is needed.
what is going to happen probably is that the new editor will start as a plugin, stay as such for a while and then will be gradually ported in core. Since CP was born many things were changed - as I already mentioned for example backbone.js was removed. everything in the UI is the same but that was changed to use something else instead. or JQueryUI Sortable, that was removed and changed to Sortable.js. You do not see the change, but there is change.
that will probably happen with editor, will stay basically the same but the underlying code will change for the better. that means if you have ideas for it you can expose them and they will be taken into account.
I’m not sure that there is any platform available to us today that has a truly working undo/redo.
I’m now firming up a design that will truly fix it, and, I’m going to add the ability to roll back to a save point. undo that one error, then still be able to roll what was undone forward.
@anaid CP’s raisin d’être is certainly not No Gutenberg. That’s just a product of our mission, which is to use modern, lightweight, efficient code in a productive manner. So lots of bloat and obsolescent code and libraries have been or are being replaced (which is why CP is so much faster than WP), while some new features have been added, especially in terms of accessibility, in the media library, and for post/page revision management.
The next thing to be rewritten is the Customizer, after which we’ll be looking, as @ElisabettaCarrara says, at adopting a new editor.
1 Like
Yes, I think I understand the situation now.
No, it does need to be in core. For sure. I’ll have it as a plugin, for sure. It guarantees the integrity of my data, and the minute I started using it to automatically strip the AI and other platform injected tags, my AI did a u-turn and I got two completed plugins, I am happy to have started being over-productive again.
But, nothing needs to be in core, in fact that is a big part of one of my projects - I’ve split Classic Press into modules and aim to have a version that will run in a 10Mb footprint, including the theme and plugins. Similarly, I’ve a project to do that with libraries. - Just strip out what is needed depending on the context of the specific server configuration in question.
But, it’s not worth the effort, if that innovation has no adopters, and that does seem to be the nature of the world. WP’s latest bundled theme, is 50% larger than the previous two, so they doubled their impact, and spread it to a million servers overnight, then claim to be concerned about the environment. I spot such incongruences at 1000 yards. That difference between what is said, and what is actually done.