Hi Menno!
Is it still happening with v1.2.6?
The WordPress cache is explicitly flushed via a call to wp_cache_flush() before the settings get saved in the database.
I tested successfully with Redis Object Cache and W3 Total Cache (with memcached) plugins.
If that’s so specific to their hosting solution, could WPMU DEV Hosting give more information about how cache is handled there? Investing more time troubleshooting one type of hosting solution in particular doesn’t fall under the type of support I give on this forum. If you can help with that, it would be greatly appreciated and I’d be willing to follow up, otherwise we’d have to pursue the conversation through other channels.
Note: it may not be necessary to go further because I plan to remove the settings cache I put in place; after testing, the impact is marginal at best, counterproductive at worst. That was something included since v1.0, and been causing issues since. The trap of early optimization I guess…
If you can wait until the next version when I’d have included more updates, then this should become a non-issue (I’ve been pushing updates rather fast lately and I don’t like that too much, it affects several connected websites, it gets people tired of updating and wondering what will break if they forget 1 site, even if it’s perfectly fine).
Hello Alexandre,
Yes i run 1.2.6. on all remote sites. I think it’s not the WordPress cache but a server cache which gives issues. I had a chat with WPMU DEV of 2 hours and they couldn’t find a solution for it.
Here is also a ticket: https://premium.wpmudev.org/forums/topic/issue-with-wp-remote-users-sync-updating-data/#post-3805927
Maybe your settings cache is cached :), which gives a ‘lag’. If you have a beta version i would like to use it. I hope it doesn’t take too long to update, because i can’t change settings on the plugin. I would like to use it :).
The WordPress Forum is limited to discussions regarding released code ; please open an issue on GitHub ;).
Full fix deployed with v1.2.7 – closing