No longer working with ClassicPress

(@kelson)

Hi, I updated Statify to 2.0.1 on two blogs today, one WordPress and one ClassicPress. On the ClassicPress blog, Statify no longer displays in the dashboard, and I see the following errors in the JavaScript Console:


Uncaught TypeError: wp.apiFetch.createRootURLMiddleware is not a function
    <anonymous> https://journal.kvibber.com/wp-admin/index.php:1047
index.php:1047:30
Uncaught TypeError: wp.apiFetch is not a function
    g https://journal.kvibber.com/wp-content/plugins/statify/js/dashboard.min.js?ver=2.0.1:2
    A https://journal.kvibber.com/wp-content/plugins/statify/js/dashboard.min.js?ver=2.0.1:1
    <anonymous> https://journal.kvibber.com/wp-content/plugins/statify/js/dashboard.min.js?ver=2.0.1:2
dashboard.min.js:2:1356

Statify is displaying on the WordPress blog’s dashboard.

Current versions of ClassicPress are forked from WordPress 6.2.

The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)

Plugin Support Stefan Kalscheuer
(@stklcode)

5 days ago

apiFetch was introduced in WordPress 5.0 and the Statify script explicitly depends on wp-api-fetch. So if functionality is on par with 6.2 it would have guessed it works – apparently that’s not the case and this Gutenberg feature is missing.

Frankly I am aware that ClassicPress exists, but that’s it. Never ran or tested anything against it. (and I think none of the team members or beta testers did Statify so with Statify 2.0) AFAIK there’s no “official” statement about compatibility.

If that’s the only issue we might consider polyfilling apiFetch or adding a fallback. We also make use of wp.i18n after data is loaded, nut that should be available according to (very brief) web search.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.

Tags