November 22, 2018 at 5:04 pm #224530
As I have explained in a comment on Gutenberg, I am not enthusiastic at all about this WP move, and for this reason I am considering the ClassicPress project of creating a WP fork - now in beta.
But since all my WP sites are built with Genesis framework, it is crucial for me to have Genesis working with ClassicPress.
I have installed ClassicPress on a test site, and activated several plugins, as well as Genesis Framework and child themes.
When installing it, I saw that I had saved v. 2.5 of the Genesis Framework (required for Genesis child themes to work) on my desktop - the current version is 2.7.1. I decided nevertheless to install it, along with a standard Genesis theme, in order to see how theme update would work.
I installed it, activated the child theme. Soon after, I received - as expected - the warning that an update was available for Genesis Framework. I launched the update, but it failed, with the warning: “forbidden”. I made several attempts to no avail.
Then I deleted v. 2.5, uploaded directly v. 2.7.1, and I could install it without any problem.
Maybe there are other reasons for this failure to update, but I seize this opportunity for raising what is potentially for me (and for other users, I guess) two important questions:
1) Does Genesis prevent updates on a WP fork?
2) Will Genesis framework support ClassicPress?
Any information about that will be appreciated.November 23, 2018 at 6:38 am #224534AnitaKeymaster
I would say that this is the community forum and representatives of StudioPress do not come here often. This question is better suited for their support so I would suggest contacting them directly.
From all the changes I've seen with WPEngine purchasing StudioPress, I don't think this would be on the front burner for them. But again, you should probably contact WPEngine about what's on their roadmap.
Love coffee, chocolate and my Bella!November 23, 2018 at 10:24 am #224541
Thank you very much for your answer.
I will indeed contact support directly, as you had suggested.
I contacted support a few times in the past, but each time they advised me to go to the forum and said they couldn't help - hence my first reaction was to use the forum. But you are right, if there is one question for support, it is definitely that one.
I had also hoped that my post would encourage other users to share their own experiences and expectations.November 24, 2018 at 9:11 am #224566Victor FontModerator
This is just my opinion, but I doubt WPEngine, the owners of Studio Press and the Genesis Framework, will support anything other than WordPress. The Studio Press devs are making changes to improve the code base and support Gutenberg. Using the Genesis Framework on a fork may work now, but it presents a risk for the future.
November 24, 2018 at 9:49 am #224567
Thank you, Victor. You are right, and this is why I am asking the question. I am very pleased with WP until now, but I do not like Gutenberg at all for editing and publishing content for the type of sites I am in charge of (it will work for some, but not for some other ones), and I am aware that WP support for the Classic Editor probably won't go further than late 2021 or early 2022, i.e. a quite near future.
For those reasons, I am looking for other options, but I have exactly the concern that you have expressed: that at some point plugins and themes would stop working properly on a fork.
Some developers are committing themselves to support ClassicPress, since a number of them are not pleased with Gutenberg, but obviously it is not clear at this point how many of them will.
Anyway, I have sent the question to support, and I am waiting to hear from them.November 24, 2018 at 11:03 am #224568November 24, 2018 at 11:41 am #224569Victor FontModerator
As an FYI, Gutenberg provides a "Classic" block under formatting that allows you to use TinyMCE as normal. There's no need for classic plugins when Gutenberg provides the classic functionality. The classic block is under the formatting area.
Gutenberg by the way is just a shell that sits above TinyMCE. TinyMCE is still the underlying editor.
November 24, 2018 at 11:56 am #224572
WP management has stated that they intend to keep the Classic option only for transition period, and support for the Classic Editor might end in December 2012:
I do not know what will happen to the Classic block in Gutenberg then. And what I like is really the Classic Editor, not a Classic block within Gutenberg.
This is definitely not satisfactory. If the Classic Editor would be kept and improved indefinitely, I would not have such concerns. In fact, I am so much concerned about the future that I am not sure that I will be using WP for future projects, and I have started exploring other CMS. A real pity, since I enjoy WP very much. But Gutenberg is just not what I want and need for writing my content.November 26, 2018 at 6:58 am #224597codableMember
I would not fall in panic mode. I am also not a fan of Gutenberg (kindly said) and have enabled the Classic Editor on all sites I own or maintain, too.
My eyes are also on ClassicPress. As I said, I would not move my site to ClassicPress for now. There is just no reason. I will wait.
The major theme companies will apply Gutenberg and will develop for it. How will ClassicPress adress that? If there will be no compatibilities with major theme companies and page builder, ClassicPress will have a hard life.
You may have noticed the dead of the Headway Theme. There was a fork, Blox Theme, that copied Headway 1:1 and that was it. No more reasonable progress. Now Blox Theme is dead.
Just don't make quick decisions. There is no reason for that. I am also disappointed by the direction WP takes.
Smaller personal projects, I will realize without a CMS in the future. With Grid or Flexbox, we have good tools to do that. We just got to lazy. Just be honest. Lots of projects don't need a CMS.November 26, 2018 at 12:37 pm #224606
Thanks, Codable! Glad to know that I am not alone among Genesis framework users.
By the way, I have received an answer from WP Engine support to my two questions:
1) "No, Genesis does not prevent updates on a WP fork."
2) "Genesis is a WordPress framework and is guaranteed to work with WordPress installations. Also, we haven't haven't received reports of incompatibility with ClassicPress."
I suppose that much will depend on the demand. If many average WP users get upset when they discover the new world of Gutenberg, this might create a sufficient demand for theme creators and plugin developers - provided those average users become aware of the existence of ClassicPress, obviously, which would require major hosting companies pointing to that option, something which is far from sure.
I agree that it won't be easy for ClassicPress. Your advice is reasonable. The hosting company where I have most of my sites recommends, for the time being, to activate the Classic Editor (which I have done, in addition to the Disable Gutenberg plugin) - and told me that they might offer ClassicPress support if there is a demand for it.
Let's see. I guess that the topic might emerge again on this forum in a few weeks or months.November 26, 2018 at 1:43 pm #224607codableMember
- The forum ‘General Discussion’ is closed to new topics and replies.