I’m running into the same issue with the ActivityPub plugin discussed here and here. Since the plugin gets updated regularly, what does one need to watch out for to keep compatibility with ClassicPress? Is it worth adding a PR to allow for a recent ClassicPress version to be compatible, and if so, which version should that be? Like 2.5 or 2.0? The WP version required is 6.4 as far as I can tell.
I would like to keep using it, and be able to update it, and also use it on a new ClassicPress project I just started, but am a bit confused what the best action to take is in this case.
ActivityPub Plugin is morphing into a full-featured AP client inside WordPress. As it gets more and more features, I think the gap in supporting ClassicPress will become wider.
A viable alternative would be a fork that focuses only on the main aspects of integrating a website to fediverse, almost as an “auto poster” specifically built for ActivityPub: it creates a profile and relays posts to the fediverse, and that’s it.
Although I admire and cheer for Matthias Pfefferle, I’m skeptical that AP Plugin will achieve its ambitious goals (becoming an 1:1 alternative for Mastodon) someday. And if so, it won’t be without collateral damages
Lately I’ve had to short-circuit the comment_reply_link function in class_comment.php to return early before it tries to register a block, or it breaks rendering posts that have ActivityPub comments on them already.
I’ve been meaning to look into a real fix instead of just putting return $link;in there and propose the fix, but maybe I should just report the bug to them.
