So, I’ve read about the issues with AP and CP, but getting more and more confused. Does it work or not? Does it “almost” work?
Does it work if I change some line of code somewhere? I’m not afraid of doing so if needed, but someone has to tell me what and where.
I read something about the version tweak or something like that, what does it mean? I also saw somewhere that someone was willing to fork the plugin (that would really be a bless), is there an actual plan for this?
Sorry for all these questions, but I really would like this to work, and work in a long term.
One is changing the “Requires at least:” line in the readme.txt to a lower version than eg. 6.3 - as CP has been reforked from WP 6.2, and that is still part of the compatiblity checks of plugins. So most of the time its just changing that number, et voila. This works sucessfully eg. with WP Super Cache and Autoptize, and somewhat decently with CF7 (parts of it doesnt work, because its aimed further towards Gutenborg, which obv. isnt part of CP).
Another variant would be to change any plugin-internal version check in a similar fashion, which sometimes can be found at the very begin of any plugin, as a part of the activation routine.
A third one is causing something different, but still related, ie. disabling automated updates, by changing the current plugin version number to something ridiciously high.
So if you’ve done changes like the simple “change minimum required version number” in the readme.txt, but want to avoid any future disasters, thats the way to get this done quickly, while still keeping up with updates easily.
last version of activity pub is marked as not compatible by the system. On this forums there are posts hinting at the fact that people are using v1 and the current version is 9.0.2, this means it can have issues.
Notice: Function map_meta_cap was called incorrectly. The post type ap_outbox is not registered, so it may not be reliable to check the capability publish_post against a post of that type.
Deprecated: Function wp_enqueue_script was called with an argument that is deprecated since version CP-2.2.0! The enqueued script thickbox has been deprecated. It will be removed in version 3.0.0 of ClassicPress.
Deprecated: Function wp_enqueue_style was called with an argument that is deprecated since version CP-2.2.0! The enqueued stylesheet thickbox has been deprecated. It will be removed in version 3.0.0 of ClassicPress.
The first means CP does not have a function needed for it to work that WP instead has.
The other two means it uses thickbox (and this means it needs its scripts and styles) but CP deprecated it and it will be removed in v3. this means it is going to work untill we go to v3 than it will become an error.
That said there are alternatives allowing you to be found on the fediverse:
both are working from what I can see (they do not trigger any warning or error notice in my test instance so this means they are CP compatible)
I am pointing at these alternatives because being that Activity Pub is developed by Automattic, even if they go around releasing a fix for ClassicPress it’s a moving target that is going to break every time they change something - their priority is not staying compatibel with this WP fork. Automattic is a commercial entity and basically CP is a competitor.