I have moved the discussion related to reporting bugs to a new thread 
2 Likes
I don’t use Elementor or BB, but I use other plugins, and I’m sure we all have plugins that we are attached to. A possibility may be to support ClassicPress v1 as an LTS that will always be compatible with WP. As in, regardless of whether the plugins officially support, they should always work. Sort of like Drupal 7 is still in wide use, even though the latest is Drupal 8.
The less complicated plugins can be forked and adapted by us or the ones supporting CP will move forward into further versions as well.
I think if we plan features on further versions of CP that are desirable but absent on WP, it will be motivation for plugin developers to intentionally support.
For example, properly supporting plugging more customizations into tag and category pages as well. SEO related optimizations, featured images, custom fields to support linked data making the site way more accessible to AIs… Instead of all the semantic plugins doing half baked jobs of linked data or very expensive paid alternatives, linked data could be a reality with existing tags and categories. BOOM. No more having to recreate endless terms and so on. Can’t imagine any future conscious developer not wanting to support that.
3 Likes
This is mentioned in the roadmap - ClassicPress | Stable. Lightweight. Instantly Familiar.
Preamble: The first version of ClassicPress will be a long-term support (LTS) version. If you choose to, you can stay on this version for years to come. We won’t introduce any changes that could break compatibility with themes or plugins that support WordPress 4.9.x.
When I read that paragraph it gave me the confidence to move everything over to CP. 
3 Likes
I hope Elementor will be forked. I have issues with the latest updates which are not being addressed by the plugin authors because I use ClassicPress, even though other people are having the same problems. 
This would not inspire people to make the jump…
2 Likes
@NyssaTheHobbit this seems like sub-par support. Have you told them that the issues you’re having are also reproducible with WordPress?
I told them it was essentially the same as WP 4.9. Also, there were a lot of “me toos” in the thread. But they said they don’t support ClassicPress, so I figured there wasn’t anything I could do. I’ve been hoping they pay attention to one of the other people with the same complaints. You can see the thread here.
They definitely shouldn’t have marked that thread as Resolved with all the other people commenting that they have the same issue. It’s up to you but I think it would be worth another reply pointing out that other people running WordPress are experiencing the same thing.
2 Likes
In any case it shows that a fork of Elementor may be essential to convince some people to use ClassicPress. Not just because they won’t support it, but because it sounds like Elementor will be keeping up with the changes in Wordpress over time.
I’ve never used Elementor (or any other page builder), but I do have one client who wanted to install it on their site.
So, it’s basically a “better Gutenberg”? Is that right? Given that CP is a business-oriented CMS, I’m just wondering if page-builders might not be very high on the list of priorities. Don’t know… just speculating.
1 Like
I’m not too familiar with it, having just recently installed it and used it for only one page. But it and Beaver Builder are popular plugins, basically page builders from what I can see, and yes, better at it than Gutenberg. The OP says he needs them to build client sites.
Yes, would be good to get ONE page builder that supported CP. I think if just one of them gets on board, and is known as the one that works with CP, then they will get all our business. Same with a security plugin. They all do much the same job, so if WordFence won’t come to the party, I’m happy to go with whoever does.
It would be interesting to start a list of categories of plugins we feel are important, and then see if we can get at least one CP-friendly version in each. Might just do that.
4 Likes
@NyssaTheHobbit I’m using Elementor with ClassicPress Beta 2 in my site redesign and I don’t have any issue till the moment.
I can have a look to see what might be going on. Do you have any staging site where that situation is replicated?
I’m not having any problems either. Maybe a plugin conflict?
No, my account doesn’t allow staging. My site is here; I can update Elementor to 2.4.3 for a bit so you can see.
A little testing just now revealed that Autoptomize is conflicting somehow. Now to narrow down how…
Found it! I had to exclude Elementor from Javascript optimization in Autoptomize.
2 Likes
Great. Good to know it was just a plugin conflict. 
1 Like
Yes, it seemed you had a conflict. I have had problems with Autoptomize myself that broke things.
1 Like
@NyssaTheHobbit Glad you sorted it.
If someone needs to check if the problem is in Autoptimize they have a flag that will let you turn off the plugin only in that request. This way it’s easy to see if the problem is related to the Autoptimize settings.
Just add this to the url
?ao_noptimize=1
It will look like: www.yoursite.com/?ao_noptimize=1
If the url already has parameterers it should look like this: www.yoursite.com/?param1=aaa&ao_noptimize=1
Hope it helps.
2 Likes
Regarding the Autoptimize issue noted above: it was a configuration error, rather than a bug. I’ve tested it pretty extensively, and it works as expected.