I don’t think the issue is on our side, but on the side of AIOS.
Got it, will you explain to AIOS about the ongoing problem with this setting?
I’m in their Slack already 🙂
Maybe it’s best if you submit a ticket with them, to convince them it’s an actual issue.
Hi @rogierlankhorst
Did they answer you? I just opened a post on their forum: https://ww.wp.xz.cn/support/topic/error-with-burst-plugin/#new-topic-0 , maybe you could add an answer and technical details. Thanks.
Ok, with some help from the AIOS team I found the problem.
When Burst cals the rest api it loads the back-end minimized, without the other plugins, for performance reasons. So the AIOS plugin is not active at that moment. As the salt is applied dynamically, it is not applied during that rest api call.
I didn’t realize it was a dynamic feature, which is why I couldn’t find the cause.
A solution for this is to disable the rest optimizer, by going with FTP to your website, and in the wp-config.hp add the following line:
define( 'burst_rest_api_optimizer', true ); //will prevent the plugin from adding the optimizer again.
Then go to wp-content/mu-plugins
And delete the file burst_rest_api_optimizer.php
Then all plugins will load during REST API calls as well.