December 15th, 2018 at 16:26 #71600
First thing I want to say is, Nirvana is hands-down my favourite theme. I’ve used it in several custom colour variations on one domain, tying my main site and several peripheral blogs together but keeping them distinct. Due to a combination of budget and being perfectly happy to announce what theme I’m using and not needing any support thanks to the beautifully organized settings interface, I haven’t signed up for the paid options. I did donate a few dollars (or a couple of coffees?) some time back to say thanks.
Because of Gutenberg being a poor match for my needs, I’ve migrated my blogs on that domain over to ClassicPress, a WordPress fork I imagine you’ve heard about. This leads to two questions.
1) Would it be possible to maintain compatibility with ClassicPress? It’s specifically a hard fork of WordPress 4.9.8 slanted more towards business and consistency. It’s in Beta 1 now and the team is working hard on the first production release, ClassicPress 1.0.0. Version 1.x of ClassicPress will always stay backward compatible with WP 4.9.x.
Although I’m certain you’re working hard to make your themes compatible with the recent and upcoming changes in WP as of 5.0, I hope that they can remain compatible with earlier versions of WordPress, such as 4.9.8? I really hope so, because as long as your themes remain compatible with WP 4.9.x, they’ll also be compatible with version 1.x of ClassicPress.
2) Is there any way of switching the footer to a more accurate “Powered by Nirvana & ClassicPress”? As I said, I have no desire to remove the link, only to amend that detail. You probably know this already, but there is even a handy condition that you can use in your plugin:
function_exists( ‘classicpress_version’ )
I’m really hoping that you’ll be open to keeping your themes available to users who are choosing a specifically business-oriented fork over the main one.
Thanks very much!
Steph ShangrawDecember 18th, 2018 at 21:15 #71694ZedCryout Creations Team
Thank you for continuing to use our creation.
The classic editor is still available and usable with WordPress 5.0+ releases using the separate Classic Editor plugin.
We will continue to support the classic visual editor with our themes for as long as it is available in WordPress, but for now we are not planning to explicitly support WordPress forks.January 6th, 2019 at 01:38 #72421
I’m aware of the Classic Editor. Gutenberg is unlikely to fit my work any better in three years when it is no longer supported than it does now, and the Classic Editor is unlikely to do anything about the further phases of Gutenberg being pushed on everyone.
ClassicPress is staying compatible with WP 4.9.x for as long as possible, but I guess, sadly, I can’t count on Nirvana in the long run. Thanks for the answer, I’ll start the search for a theme that is going to specifically support ClassicPress.
The topic ‘ClassicPress compatibility and support?’ is closed to new replies.