This is probably due to page caching, which wouldn’t be active on the backend of your site. You should be able to configure the cache to exempt pages that have Participants Database shortcodes.
Hi,
Thanks for your answer. I don’t think it’s a cache issue since I already tried to purge the cache and it didn’t help. The participant also won’t show up on another browser. The problem appeared only like last month, we didn’t have any issue before that.
Purging the cache won’t solve the problem if it is a page cache, you need to set up those page exemptions. The symptoms you describe are consistent with a cache preventing fresh data from getting displayed, particularly the part where is works on the backend but not the front.
If it is not a cache issue, it will be helpful if you can describe in detail the sequence of events that shows the problem. This way I can duplicate the process and see where the problem you’re seeing might crop up.
I went the straightforward route on my testing site (not the one I linked before) and deactivated my cache plugin + define(‘WP_CACHE’,false); in wp-config but it unfortunately did not solve the problem.
As for the detail sequence of events, I just fill the form to add a new participant, click on “Validate”, see it on database and backoffice but when I go to the front office, I don’t see the new entry EXCEPT the first one I add after I deactivate/active a plugin. It does not have to be PDB, it can really be a random one.
The funny thing is deleting a participant in the database lead to the same issue. I can still see the one I deleted on the front page until I do the plugin manipulation.
I am sorry if it is not clear enough, english is not my native language. Please let me know if you had another idea when you were talking about the cache.
Thank you
Yes, this is definitely caching, but probably not a caching plugin. You should contact your hosting provider and ask them to place caching exemptions on the pages with Participants Database shortcodes.
Hello,
I just wanted to update if anyone encounters the same issue : the culprit was Elementor. After cleaning and deactivating Elementor’s cache, everything worked fine again.
Thank you
