Hi - new member, donator and ClassicPress user here. Spotted CP a while back but finally took the plunge after the recent shambles with WP Engine and Automattic.
I’ve been working with WordPress for over 10 years and create completely custom themes for clients. I’ve been getting increasingly frustrated with speed issues, terrible core code, Gutenberg and now full site editing. Half of my time is spent disabling things I don’t want or need along with clearing notification spam from WooCommerce and the big WP plugins.
Migrated one of my blogs to CP in ~5mins so great work on the migration plugin, thanks. Also tried my base theme and usual plugin stack (inc ACF for my page builder, SEOPress, WPSCSS, BackupWordpress) and that seems to work too!
I’d love to help with theme development, UX and documentation/tutorials/proofreading along with testing plugins as I experiment with using CP for my own sites and small client sites. Nifty with HTML/CSS and have basic JS and PHP skills.
Recently joined Bluesky as well after Mastodon kind of fizzled out, and would be great to see CP on there
Hi Web242! Yes it’s looking good so far - only snags are some minor interface issues with ACF Pro and ContactForm7 not being available.
Related - is there somewhere we can collect info on what works/doesn’t as a community reference?
Cheers,
Nick
I use CF7 with ClassicPress v2, you may need the version spoofing tool from the Classicpress plugin directory (or you could use an older version depending on if you are using a bunch of plugins). The latest version if CF7 does have an issue with some missing functions, but they can be added, and a backport will be available in CP v2.4 I believe.
Here are the links to the functions, you can just copy / paste them into your functions file (or wherever), I also do the ‘if function exists’ thing to make sure no conflict is created if they are called from another plugin or something:
Mastodon fizzled out? Its numbers are up. I’m guessing you didn’t find it to your liking somehow, and that’s fair, but it doesn’t justify mis-characterizing it as ‘fizzled out’.
That’s interesting, thanks! CF7 wasn’t allowing install from the plugin repo but was wondering if it could be installed via upload. One client relies on that sending to a webhook so would be great to get it working.
Good shout on Fluent Forms, big fan of their SMTP plugin
I might be able to fix the ACF Pro styling issues, and they don’t prevent me using my page builder. Will investigate and report back!
Good catch thanks - more accurately my Mastodon experience fizzled out. There are still apparently over 900k active users according to https://mastodon-analytics.com/ so it might be me!
Do you use and enjoy Mastodon? I love the philosophy of federated social and will keep my accounts going as the latest Xodus might get things moving again with the people I follow.
We have a utility that allows you to ‘spoof’ the WP version, that way plugins that actually do work (or can be patched to work) can be installed even if they call for a higher version of WordPress.
The plugin is available from the ClassicPress Directory.
CP v2.2.0 will report as WP v6.2.6, so to install plugins that say they need a higher version, you can use the utility to enter any WP version you wish.
Mastodon comprises my entire social media presence at this point, if I don’t count a LinkedIn account I quit paying for and haven’t visited in at least 3 years (and I don’t). Mastodon is good for interaction, not very good if your goal is getting tons of followers; whether or not Mastodon is good for you depends on what you want from SM.
The work here is not creating and adding to the site. There’s something that involves much more work, to which I’ll return below. But I’m actually much more bothered about false advertising.
What does it mean when a plugin is called “compatible”? For example, is ACF Pro compatible? That apparently depends on how easy a person finds it to add a bit if code.
And what about a plugin that’s compatible for one user, but not for another who uses a different feature?
And what about a plugin that used to be compatible but isn’t now for some reason? Regular testing would be a lot of work.
Having people make suggestions on a thread makes it clear they are personal suggestions made at a specific time. Putting up a list on the CP website looks like a set of promises we’re in no position to keep.
Hmm good points - this is a really tricky one to pin down as ClassicPress and the plugin code are constantly changing. My thoughts were something like https://www.protondb.com/ with a traffic light system, but even that probably wouldn’t stay accurate for long…
In other news, I migrated my freelancer tips blog today. Migration went flawlessly and it loads much quicker now
That site is a great model of how to do it well, but it depends on there being literally tens of thousands of individuals registering their input. So any incompatibility is likely to get noticed quickly. That, in turn, facilitates the traffic light rating system, because it’s likely that all the different features will be tested out by someone.
We just don’t have the numbers to adopt that approach. One person’s view of a plugin will, instead, have disproportionate value, and we’ll end up in a legal minefield. (And yes, I am a lawyer.)
There is also the issue (sort of stated by Tim) where one person can get a plugin to work and keep it working, but another person cannot. To some extent, if a plugin relies on anything that is part of blocks / Gutenberg it probably won’t work or will need a lot of recode. If the plugin does not rely on those components, then it probably will work, or can be made to work with some amount of (usually fairly simple) recoding. I don’t know that we can get more specific or create a list, because I am already seeing a number of conflicting posts even with a fairly small contribution pool.
It’s not just CP that changes. Many plugins change even more dramatically. ACF Pro is a good example: when I started using it, it only did custom fields, it did them well, and updates to fix vulnerabilities were rare. Somewhere along the line, the ability to add custom posts, taxonomies, and options pages was added, and the security updates are much more frequent. And since WPengine owns it now, I’m concerned there may come a time when it will be unusable for ClassicPress.
@raygulick I agree that’s a possibility. Since you are so familiar with ACF, and ACF seems to be such a popular plugin among CP users, would you, perhaps, be interested in developing something that replicates ACF functionality that could go into CP core?
