Error with new update

@sviluppomania can you try re-saving the permalinks (in the WordPresss menu: settings/permalinks), then check again?

If that doesn’t help, can you post a screenshot of your developer console? (right click on the screen, “inspect”, “console”). The error shown there can tell us a bit more about the issue.

• This reply was modified 2 years, 3 months ago by Rogier Lankhorst.

/wp-json/burst/v1/fields/get?false&nonce=4b42a77eec:1
Failed to load resource: the server responded with a status of 404 ()
index.js?ver=c75a27a0c910c31b9804:1

Uncaught (in promise) Error: Request failed with status code 404
at e.exports (index.js?ver=c75a27a0c910c31b9804:1:10690)
at e.exports (index.js?ver=c75a27a0c910c31b9804:1:13106)
at XMLHttpRequest._ (index.js?ver=c75a27a0c910c31b9804:1:5220)

@sviluppomania ok, so re-saving the permalinks didn’t work?

The errors in your console show that the rest route is not loaded.

Do you maybe have a plugin installed which blocks the entire wp rest api?

I tried deactivating all plugins, the only one that when deactivated shows the Dashboard Burst again is this plugin: https://github.com/qtranslate/qtranslate-xt (qTranslate-XT), maybe there is some new Burst update that is not compatible with

Ok thanks, we will test with qtranslate and get back to you

Autoupdate Burst are braking sites

When du you fix this??

@medieskolen an upgrade function in the 1.3.0 update used a function only accessible when logged in, causing an error during auto updates.

This was fixed in 1.3.1, which was released 7.30 am on November 24th.

I’m sorry for the inconvenience caused. We’ve put additional tests in place to improve auto update tests to prevent this from happening again.

Hello @rogierlankhorst
I noticed in the log that there is also this error:

Error in hook rescheduling cron event: burst_every_5_minutes, error code: invalid_schedule, error message: Scheduled event does not exist., data: {"schedule":"burst_every_5_minutes","args":[], "interval":300}

Can it help you?

This also:

PHP Fatal error:  Uncaught Error: Call to a member function format() on bool in /wp-content/plugins/burst-statistics/statistics/class-statistics.php:663
Stack trace:
#0 /wp-content/plugins/burst-statistics/settings/settings.php(341): burst_statistics->convert_date_to_utc()
#1 /wp-includes/rest-api/class-wp-rest-server.php(1171): burst_get_data()
#2 /wp-includes/rest-api/class-wp-rest-server.php(1018): WP_REST_Server->respond_to_request()
#3 /wp-includes/rest-api/class-wp-rest-server.php(442): WP_REST_Server->dispatch()
#4 /wp-includes/rest-api.php(410): WP_REST_Server->serve_request()
#5 /wp-includes/class-wp-hook.php(308): rest_api_loaded()
#6 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#7 /wp-includes/plugin.php(565): WP_Hook->do_action()
#8 /wp-includes/class-wp.php(399): do_action_ref_array()
#9 /wp-includes/class-wp.php(780): WP->parse_request()
#10 /wp-includes/functions.php(1332): WP->main()
#11 /wp-blog-header.php(16): wp()
#12 /index.php(17): require('...')
#13 {main}
  thrown in /wp-content/plugins/burst-statistics/statistics/class-statistics.php on line 663

@sviluppomania

– To check if the cron job runs correctly, I installed the plugin ‘WP Crontrol’. On of the cron jobs is ‘burst_every_5_minutes’, which has the action ‘burst_statistics->generate_cached_data()’ connected to it.

I don’t see any issues with it currently. Maybe you can use the WP Crontrol plugin to delete the event, after which it will get added by Burst again with the correct action. Can’t reproduce the issue myself though. Let me know if the above helps.

– Regarding the error you posted. I don’t expect this to cause your blank settings page: the time passed to this function is not valid, causing the function to fail. It doesn’t prevent the Rest Route from loading. I’ve added a check which catches such a situation, but couldn’t create one in which this occurred. This will get merged in the next release. You can try to see if it makes a difference:
https://github.com/Really-Simple-Plugins/burst/tree/catch-not-instantiated-datetime-object

– I’ve installed qTranslate-XT, from github here:
https://github.com/qtranslate/qtranslate-xt/releases/tag/3.12.1

This didn’t cause any issues with the settings page. But maybe I need specific settings for this to reproduce it. Maybe you can list your settings here, or email it to support(at)burst-statistics.com. If any of those settings cause the issue, I should be able to reproduce it by enabling that setting.

Hello,
the problem actually lies in qtranslate, precisely you have to try:

Settings -> Languages -> Integration

You have to activate the “Slugs translation” integration, if deactivated it shows the Dashboard Burst.

I could reproduce it! Thanks for the specific setting, this made it very easy to find the problem.

It appears the with this settings, qTranslate will add a /en/ to the Burst rest route. This route doesn’t exist, so breaks.

You can find the fix here:

https://github.com/Really-Simple-Plugins/burst/tree/qtranslate-fix

Let me know if that works for you as well!

It will get merged in the next release.

• This reply was modified 2 years, 3 months ago by Rogier Lankhorst.

Great, problem solved, solution works.

What was the problem ?

The problem was that with this settings, qTranslate will add the language, e.g. /en/ to the Burst rest route. This route doesn’t exist, so breaks.

this

wp-json/burst/v1/fields/get

Then becomes:

/en/wp-json/burst/v1/fields/get

Hi @rogierlankhorst ,

the same bug came back, if the “Slugs translation” integration of the qTranslate-XT plugin is active you don’t see the Dashboard Burst, if the integration is deactivated it shows the Dashboard Burst again.