4 ms·

I understand your disdain for their new editor, but it is not required. The great part about Wordpress is the ecosystem of plugins and customizability of the CM

I understand your disdain for their new editor, but it is not required. The great part about Wordpress is the ecosystem of plugins and customizability of the CMS. You can just add the Classic Editor plugin and you can use the old editor - it is that simple. If the editor is laggy it is because of the server / infrastructure you are using, not the editor. I can guarantee this as a fact. I wouldn't brush off Wordpress. I've used pretty much every CMS on the market with client work and Wordpress is the one that I prefer the most for websites, hands down. For custom applications, I prefer Contentful for the backend CMS. There is a reason that Wordpress is #1 and has the market share it does. It is not flawless, but it is the best once you get to know it. Especially when you know how to optimize and debug problems. If you are just doing a pet project and simple blog and you don't want to spend a few minutes to figure things out, then it might not be for you. There are many options for a simple blog. Like any technology worth knowing, in order to maximize its features you need to learn how it works. Best of luck to you.

dorchadas 6y ago
> I understand your disdain for their new editor, but it is not required. The great part about Wordpress is the ecosystem of plugins and customizability of the CMS. You can just add the Classic Editor plugin and you can use the old editor - it is that simple. You can do this if you pay for hosting or an account on wordpress.com. As this was meant to be a pet project, I really didn't want to pay for it, so went with the wordpress.com free account. > If the editor is laggy it is because of the server / infrastructure you are using, not the editor. I can guarantee this as a fact. I mean, you'd think that Wordpress's own editor wouldn't lag on their free account/hosting, especially if they're wanting people to upgrade and not leave? > If you are just doing a pet project and simple blog and you don't want to spend a few minutes to figure things out, then it might not be for you. I've spent the time trying to figure it out. The bigger issue is I don't want to pay currently, until I'm certain I'm going to stick with this project. Sadly, the only way to fix the problems is by paying.
- photomatt 6y ago
  dorchadas, we haven't been able to track down your account, but if you get in touch with help@WordPress.com and link to this thread, would love to debug the slowness with you, and also happy to comp you a 300/year business account which supports plugins and themes for 3 years.
- wpcomsupport 6y ago
  > You can do this if you pay for hosting or an account on wordpress.com. As this was meant to be a pet project, I really didn't want to pay for it, so went with the wordpress.com free account. A payment is actually not needed in order to use the Classic Editor with a Free site. You can use the Classic block in the Block editor, which you can learn more about here - https://wordpress.com/support/wordpress-editor/blocks/classic-block/ https://wordpress.com/support/wordpress-editor/blocks/classi... There is also a possibility to edit or create any post or page in WP Admin, which will allow you to use the Classic Editor. Navigate to yoursite.WordPress.com/wp-admin and then click on Posts or Pages in the left sidebar. Next you can hover over any post or page title and choose the "Classic Editor" link below the title. If you wish to create a new post or page within Classic Editor, then please click the down arrow next to the Add New button at the top and choose Classic Editor. We are also happy to answer any of your questions and try to understand why the editor is laggy for you if you send us an email via help@WordPress.com. Thank you!
- natenthe 6y ago
  If you want to create a blog without knowledge of code and/or hosting servers then I wouldn't use Wordpress. Something like Wix or Squarespace would be more up your alley. I understand not everyone is in the position to pay money on certain things, but if you don't want to pay then don't expect things to work amazingly well. Hosting servers isn't cheap.
rovr138 6y ago
> If the editor is laggy it is because of the server / infrastructure you are using, not the editor. I can guarantee this as a fact. I would expect that once the editor loads, unless you trigger an option that requires something from the backend, it would just work. Does it actually send data back and forth during the writing process?
- natenthe 6y ago
  When Wordpress is lagging, it is always because of the infrastructure, whether that is client or server side. The editor does not send data to the backend. Without actually having access to the machine, I can almost guarantee that there are issues with the client-side machine or browser which is the reason for the lagging.
tmpz22 6y ago
> You can just add the Classic Editor plugin and you can use the old editor - it is that simple. This is a terrible take from an ops perspective. "Just install plugins" ignores the fact that you're adding arbitrary executable code to your server, hoping whoever maintains it actually maintains it, actually secures it, and actually doesn't sell the plugin to a nefarious party at a later date. Which is to say nothing of how many orgs allow management and marketing to choose which plugins to install. Try prying those access rights from their cold dead hands...
- NeutronStar 6y ago
  It's literally one line of code that you have to add. It's really not that hard to maintain.
- aakkaarr 6y ago
  You are in a wrong comments thread. This is a post about how popular with is WordPress and it is popular because you install plugins there and have site without completely any programming language. There are no ops (or at least they are not a part of wordpress success), there are people who know how to buy shared hosting and that's it.
- natenthe 6y ago
  Wordpress owns and maintains the plugin. Hardly "arbitrary". Please do some research before ranting next time.
quantummkv 6y ago
> If the editor is laggy it is because of the server / infrastructure you are using, not the editor. I can guarantee this as a fact. Gutenberg is react based client side thing. The lags while typing in Gutenberg cannot be due to the server.
- natenthe 6y ago
  I said server or infrastructure, meaning server or client-side machine / browser. Essentially, their hosting or local environment. The code loading in their browser which is causing the lag is the same code for everyone else, and this is not a reproducible issue in the WP community. If this person's account of things is accurate, then any lags in Wordpress would be a local environment issue.

dorchadas 6y ago

> I understand your disdain for their new editor, but it is not required. The great part about Wordpress is the ecosystem of plugins and customizability of the CMS. You can just add the Classic Editor plugin and you can use the old editor - it is that simple. You can do this if you pay for hosting or an account on wordpress.com. As this was meant to be a pet project, I really didn't want to pay for it, so went with the wordpress.com free account. > If the editor is laggy it is because of the server / infrastructure you are using, not the editor. I can guarantee this as a fact. I mean, you'd think that Wordpress's own editor wouldn't lag on their free account/hosting, especially if they're wanting people to upgrade and not leave? > If you are just doing a pet project and simple blog and you don't want to spend a few minutes to figure things out, then it might not be for you. I've spent the time trying to figure it out. The bigger issue is I don't want to pay currently, until I'm certain I'm going to stick with this project. Sadly, the only way to fix the problems is by paying.

photomatt 6y ago
dorchadas, we haven't been able to track down your account, but if you get in touch with help@WordPress.com and link to this thread, would love to debug the slowness with you, and also happy to comp you a 300/year business account which supports plugins and themes for 3 years.
wpcomsupport 6y ago
> You can do this if you pay for hosting or an account on wordpress.com. As this was meant to be a pet project, I really didn't want to pay for it, so went with the wordpress.com free account. A payment is actually not needed in order to use the Classic Editor with a Free site. You can use the Classic block in the Block editor, which you can learn more about here - https://wordpress.com/support/wordpress-editor/blocks/classic-block/ https://wordpress.com/support/wordpress-editor/blocks/classi... There is also a possibility to edit or create any post or page in WP Admin, which will allow you to use the Classic Editor. Navigate to yoursite.WordPress.com/wp-admin and then click on Posts or Pages in the left sidebar. Next you can hover over any post or page title and choose the "Classic Editor" link below the title. If you wish to create a new post or page within Classic Editor, then please click the down arrow next to the Add New button at the top and choose Classic Editor. We are also happy to answer any of your questions and try to understand why the editor is laggy for you if you send us an email via help@WordPress.com. Thank you!
natenthe 6y ago
If you want to create a blog without knowledge of code and/or hosting servers then I wouldn't use Wordpress. Something like Wix or Squarespace would be more up your alley. I understand not everyone is in the position to pay money on certain things, but if you don't want to pay then don't expect things to work amazingly well. Hosting servers isn't cheap.

rovr138 6y ago

> If the editor is laggy it is because of the server / infrastructure you are using, not the editor. I can guarantee this as a fact. I would expect that once the editor loads, unless you trigger an option that requires something from the backend, it would just work. Does it actually send data back and forth during the writing process?

natenthe 6y ago
When Wordpress is lagging, it is always because of the infrastructure, whether that is client or server side. The editor does not send data to the backend. Without actually having access to the machine, I can almost guarantee that there are issues with the client-side machine or browser which is the reason for the lagging.

tmpz22 6y ago

> You can just add the Classic Editor plugin and you can use the old editor - it is that simple. This is a terrible take from an ops perspective. "Just install plugins" ignores the fact that you're adding arbitrary executable code to your server, hoping whoever maintains it actually maintains it, actually secures it, and actually doesn't sell the plugin to a nefarious party at a later date. Which is to say nothing of how many orgs allow management and marketing to choose which plugins to install. Try prying those access rights from their cold dead hands...

NeutronStar 6y ago
It's literally one line of code that you have to add. It's really not that hard to maintain.
aakkaarr 6y ago
You are in a wrong comments thread. This is a post about how popular with is WordPress and it is popular because you install plugins there and have site without completely any programming language. There are no ops (or at least they are not a part of wordpress success), there are people who know how to buy shared hosting and that's it.
natenthe 6y ago
Wordpress owns and maintains the plugin. Hardly "arbitrary". Please do some research before ranting next time.

quantummkv 6y ago

> If the editor is laggy it is because of the server / infrastructure you are using, not the editor. I can guarantee this as a fact. Gutenberg is react based client side thing. The lags while typing in Gutenberg cannot be due to the server.

natenthe 6y ago
I said server or infrastructure, meaning server or client-side machine / browser. Essentially, their hosting or local environment. The code loading in their browser which is causing the lag is the same code for everyone else, and this is not a reproducible issue in the WP community. If this person's account of things is accurate, then any lags in Wordpress would be a local environment issue.