User Favorites shortcode not displaying all favorites

My first inclination would be to question if it’s a conflict with page cache, but there are workarounds in place for both favorite buttons and shortcode-generated lists specifically for this.

There isn’t anything I can think of that you would be doing wrong.

Is this something on a public site you could link to?

Hey Kyle, thanks for responding.

Our website is: https://rightbeatradio.com
You can see the button specifically on this page: https://rightbeatradio.com/product/soda/

Here’s what I discovered – we have a plugin that loads youtube video comments on each of our product pages. Until that plugin has FULLY loaded, meaning comments have loaded and have displayed, the favorites button will not accept user interaction.

For example, if I visit a product page and click the favorites button before everything has loaded, it will act like it saved the favorite but then it jumps back to its original state – as if the button was never clicked. I hope this makes sense.

A workaround that we did was to add a 4 second timer to the button so that it won’t display until the youtube comments plugin has fully loaded. It’s not the ideal workaround, but it does work for now.

I am certain that my original issue was not that it wasn’t displaying all of my favorites, but because I was clicking the button before everything had loaded.

Does this all make sense? If you visit the link above, you’ll notice the button on a timer. So you may not be able to test it properly at this point.

Thanks man.

Version 1.1.1, just released, now includes an option to add a “loading indication” to the button(s). It may help provide a visual indication that a) the initial button is loading, and b) when someone favorites a post, something is going on in the background.

As an example, it’s up on the plugin website (it’s on slower shared hosting, so it should be noticeable): favoriteposts.com.

In your case, you’d probably want to use the provided hooks to change out the loading gifs to match your theme. There’s documentation on how to do that on the plugin site.

I know it’s more of a “band-aid” fix, but I can’t currently think of a better way. The button “update” needs to trigger once the document is ready (with page cache enabled), and if other page elements/resources are delaying that, there’s not much to do.