Hi Thierry,
when you save the playlist and refresh or re-visit the playlist edit page, are the changes reflected properly?
In short, is this a back-end issue (how data data saved), or a front-end issue (how data are displayed)?
From you description up until now, it sounds more like a front-end issue, and probably a caching issue, just like you mentioned. So, my first suggestion is to completely disable all caching plugins/features and see if the issue persists. Assuming it works correctly, you can then start enabling caching plugins/features one by one, until the problem comes back, so that we can identify the exact culprit.
I’m saying caching plugins/features as you may have separate plugins for e.g. object caching (redis, memcached, etc), and page caching (e.g. WP Rocket, Litespeed cache, etc). But you might have a plugin that handles both or more.
I also see that you use Polylang. This might also be responsible in case of improper configuration. For example, if you have configure the plugin to translate AudioIgniter playlists, you might be editing the English playlists while you display the French ones. So, make sure that either you are not translating the playlists, and if you do, that you’re editing the appropriate ones.
Thread Starter
thfofr
(@thfofr)
Hello Anastis,
Thank you very much for your reply. Indeed, my problem apparently stemmed from the propagation delay of my WordPress cache plugin (Total Cache), because the playlists finally updated themselves a day later. It is weird because the other elements of my website (like the css) were updating without delay, but I will check for possible cache transmission issues between my WordPress and my host.
To answer your other question, I understand that Polylang could cause confusion between language versions, but it’s not my case, my Polylang settings are such that it doesn’t apply to my playlists.
Thank you again and congrats for this excellent tool that works very well by the way 🙂
Thierry
Hi Thierry, glad you found the culprit!
You may want to check for any special handling that the plugin may do on URLs with query strings.
AudioIgniter uses URLs of the form https://www.your-domain.com/?audioigniter_playlist_id=123 to actually load the playlist data, so you may even want to exclude this pattern altogether.
Thread Starter
thfofr
(@thfofr)
Hi Anastis,
Thanks, indeed it can be useful!
Best,
Thierry
