Hi @matt33
[gamipress_achievements] shortcodes as GamiPress: Achievements widgets shows the achievement earned status based, by default, on the current logged in user
But in both ways you are able to define a specific user ID, then achievements will show the earned status of this user to let you place achievements for example on an user public profile to let other know what he has earned
The unique issue you can get (if you don’t defined a specific user ID) is that your achievements earned status are getting cached by a caching plugin (W3 Total Cache, WP Super Cache, etc)
Keep in mind that this type of plugins will store the HTML of every page, so dynamic content (like earned status based on current user) won’t be updated until cache get updated too
If your problem comes from a caching plugin, the unique way to fix it is excluding pages with dynamic content to being cached
Hope it helps you
Best regards
Thread Starter
matt33
(@matt33)
Hi @rubengc,
Thanks for you reply.
At the beginning I thought it was a cache problem, but when I delete all the cache and when I turn my browser in private, I had the same issue, when an achievement is unlocked, he is set as active in the shortcode [gamipress_achievements] for all users.
I earned the achievement with my login, I created a new user delete cache, and I already see the achievement as active with the shortcode, it’s the same for the other users and the guests.
Thread Starter
matt33
(@matt33)
Hi,
Sorry, but the problem is not resolved, there is a bug.
Hi @matt33
You issue is not an assets caching (CSS and JS), is an HTML caching issue
To explain it to you, you cache plugin stores the [gamipress_achievements] output for user 1 (for example) and the rest of users are showing the HTML related to user 1
You will find the same issue if you have a widget that shows the username of current logged in user, if user 1 logs first and you cache plugin stores the HTML that has his name, the rest of user will see the user 1 name instead of their respective names
Clearing browser cache hasn’t effect, because browser cache (or private navigation) just affect to assets cache (CSS and JS), not HTML
The unique way to fix it is excluding pages with dynamic content to being cached
Best regards