I’m sorry to inform you I’ve tested on two websites and it failed. Test results and error log included below. – Test Wordpress 5.8 → ClassicPress 1.3 Wordpress 5.8 → all plugins up to date; → Theme: Make PLus (with plugin) → Security: Wordfence, 2FA enabled → imagick not installed (sited…

Thanks for the edit. On the second site I use Contact Form 7, but not on the first one. Apart from that, the migration plugin didn’t mark any issues/errors. If this would be released ‘in the wild’ you’d have a lot of frustrated users for sure. The last thing people want to hear is “yeah, turn off y…

[image] Rudy_Brinkman: The link as provided in this topic Right, that won’t work. The Advanced Controls section shows this warning which is worth paying attention to: Use this form to switch to other versions of WordPress, or ClassicPress migration builds! Official release builds of Classi…

[image] Rudy_Brinkman: On the second site I use Contact Form 7, but not on the first one. Apart from that, the migration plugin didn’t mark any issues/errors. Can you send the error log for the second site also? It is probably a different issue then.

This I don’t understand. It says above: [image] ClassicPress 1.3.0-rc2 Release Notes We encourage you to try out this release candidate by pasting the zipfile URL into the “Advanced” section of the migration plugin, and letting us know if you see any issues. I followed these instructions, did…

The error log was from the 2nd one. Here’s the error logging from the 1st site. Clearly it points to a plugin, but as with the 2nd site, the migration tool doesn’t show this upfront. You can’t do this to John Doe who wants to upgrade his website… [Wed Aug 25 17:55:42.231597 2021] [proxy_fcgi:error…

OK, I see what you mean, I’ve updated the release post to make this a bit clearer. We rely on reports like yours to mark plugins as incompatible with ClassicPress. This is not an easy problem to solve, and this is the reason there are so many warnings about making a backup in the migration plugin. …

BTW, when CF7 started to demand WP5, I found the Smart Forms from Rednao is a much better plugin, than CF7. It supports WP4.9 and works in ClassicPress without problems.

Sure a list of incompatible plugins has to exists, but why not to use the list just for plugins that states to work with WP 4.9 but don’t work and automatically excluding those requiring WP 5+? Sorry if I’m wrong but I totally miss how the migration plugin works.

That is how it is supposed to work. The remote List stores plugins that for some reason cannot be detected as incompatible by our migration plugin already The migration plugin checks both readme and main plugin files for requirements. If it finds a WP 4.9+ instance, it tells so to the user. If it …

The latest release of the migration plugin only works based on the incompatible plugins list stored on our API server. [image] anon66243189: The migration plugin checks both readme and main plugin files for requirements. If it finds a WP 4.9+ instance, it tells so to the user. This part has …

ClassicPress Forums

A couple more plugins incompatible with migration

Support

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled