Error with new update

Hi @sviluppomania,

Weird that the issue came back. Did you update qTranslate or Burst?

Kind regards,
Hessel

Hi @hesseldejong ,

Only Burst has updated.

Hi @sviluppomania,

I made a new WordPress install. I installed the latest version of qTranslate from GitHub and the latest version of Burst from the repository.

I activated the “Slugs translation” integration, and unfortunately, I can’t reproduce the issue. Do you have more settings turned on that influence the WordPress rest routes?

Can you check in the console what the rest routes are with the setting turned on and with the setting turned off?

You can check by doing the following in Chrome(Other browsers should be similar):
1. Inspect the page
2. Open the network tab
3. There is an input box named filter, type in ‘fields/get’
4. Click on the request, and you should see a Request URL.
5. Can you send us the request URL with the settings turned on and off? You can strip your domain if you like.

Kind regards,
Hessel

The Dashboard Burst only disappears with that qTranslate-XT integration active.

If it’s on ‘fields/get’ :

/it/wp-json/burst/v1/fields/get?false&nonce=18dcd736c4

Request Method: GET

Status Code: 404

, if it’s off fields/get is and it’s like this:

/wp-json/burst/v1/fields/get?false&nonce=18dcd736c4 ( without it/ or en/ )

Request Method: GET

Status Code: 200

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

Hi @sviluppomania,

Thank you for the information.

We have changed the fetch function to the default Gutenberg/WordPress fetch function: apiFetch. I think qTranslate should work with this function. But unfortunately, I still can’t reproduce the issue. So I’m not sure if this will fix your issue.

I hope you can try it out and let me know how it goes. Sorry for the trouble and thank you for your patience.

Kind regards,
Hessel

Unfortunately I tried to insert the correction, but the error still appears. I believe there is some incompatibility with slugs. Because if the Slugs integration is deactivated the REST API calls them without /it/ or /en/ , but if the integration is active there is the 404 error:

Failed to load resource: the server responded with a status of 404 () /it/wp-json/burst/v1/fields/get?false&nonce=911bfe1b6c:1

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

Hi @sviluppomania,

Sorry! I should have added a Github URL to my previous reply. Not sure why I forgot.

Can you download this fix from our Github?
https://github.com/Really-Simple-Plugins/burst/compare/qTranslate-fix-2

Let me know if this fixes the issue.

Kind regards,
Hessel

The fix I put in is the same as the GitHub URL.

https://github.com/qtranslate/qtranslate-xt/releases/tag/3.13.0