Hello - Toe in the water time

General Discussion
1

Hello everyone.

I’m one of those developers that clung onto WordPress, continuing to use the classic editor and avoid blocks, but can see the writing is on the wall, and I need to switch platforms.

ClassicPress seems an obvious answer. But I shall have to investigate. I’m on Hostinger VPN hosting. As all of my sites are currently on WordPress, I was thinking of creating a fresh installation of wordpress and then upgrading it to CP as a first step. Is that a simple option? I see that there is a plugin for it, but am wondering about cross compatibilities. For example, for any wp site, the first thing I’d want to do it install a security firewall plugin and a backup plugin. Would Wordfence and Updraft work?

My background is social networking development, and I used to be an active member of the BuddyPress development team. I also run a number of websites, and am developing an integrated content management system currently, which I’m planning to extend into a network model.

1 Like
2

Welcome to ClassicPress! Using the plugin to switch to CP is very easy. Updraft will work; I use it myself. I don’t use Wordfence, though, so others can chime in on that.

1 Like
3

My advice is: install CP and install the plugins you want to use one at a time and see whether CP supports it or not.

Please note that CP will (or may) remove jQuery support from core in version 3. I’m not sure if this will affect themes and plugins that rely on it.

4

Thanks, I’ll take a look at the theme options

5

what is jQuery being replaced with, if anything? presumably there will be a migration plugin?

6

Vanilla JS, here’s a link to more info:

1 Like
7

Ciprian Popescu’s WP Guardian security plugin works with CP and has an email 2FA option; if you want app-2FA, WP 2FA works with CP as well. Ciprian is a forum member, maintains the plugin also with an eye on CP, and responds to queries. There is also the CP Pepper plugin that is included in the CP download.

1 Like
8

Support for jQuery will NOT be removed in version 3. While we are steadily replacing use of jQuery in core, we won’t be ready to abandon it in version 3 of ClassicPress. We SHALL, however be removing support for jQuery UI, which was abandoned by the jQuery developers years ago. That has been replaced in core by a combination of more modern HTML, vanilla JS, and the SortableJS library.

3 Likes
9

I think that’s reasonable enough. Thanks for clarifying.

1 Like
10

I’ll take a look at those plugins.

11

I like CP Pepper, and see that as a definite plus for CP. Same with the use of bcrypt.

I’ve moved beyond “if”, and now thinking of when, and how.

From a development perspective, is it possible to have a site that is switchable between WP and CP? I think we can switch directories, but is there still compatibility in the core databases?

1 Like
12

ClassicPress has a couple of extra database tables (that enable relationships between any objects), so any functions that make use of them will cause an error. But since you’re new to CP, you won’t have any such functions yet. CP core uses them, but obviously if you swap to WP, then you wouldn’t have those functions.

1 Like
13

Thanks, would you have a document of those tables? They sound interesting.

On my main test server, I have over 1000 plugins that I like to keep an eye on, and use for occasional tests. I’d like to be able to switch it between WP and CP. I guess my next step is to see if I can use conditional logic in .htaccess, if I can pass it a parameter to tell it which system to boot.

1 Like
14

Take a look at this post: ClassicPress Version 2.2 is Out! | ClassicPress

15

I use Wordfence with CP, but obviously the core file detection does not work properly.

16

Yes, I’ve just fixed the deprecation notices for it. delt and braces lol.

1 Like