Hey @lucasbelini,
Can you confirm you’re on version 1.9.0 of the plugin?
There was a fix for this in the most recent version of the plugin. If you are definitely on this version. I’ll take a deeper look and see if I can replicate.
For that it’d be great to know which web browser you’re using. Most of my testing was done in Chrome.
Thanks,
Tom
@tbenyon yes i’m running version 1.9, actually this start happening when i updated the plugin =/ dunno why it’s happening and i didn’t had this problem before 1.9 hahaha. i’m using chrome too
@lucasbelini no worries. Apologies for the inconvenience.
I’m in my day job right now so will try and have a look at this asap for you.
Will keep you posted but please feel free to chase me.
Thanks,
Tom 🙂
thanks a lot for the quick respond.
keep up the good work 🙂
looks like it was a server-side cache problem, i spent the last 2 days trying to figure out what was the problem hahaha i’m sorry to waste your time with this, it’s working properly now.
Awesome! That’s great news 🙂
Bet that feels good to sort out!
If you have any more questions, feel free to get back to me.
If it all works and you have time, I’d be grateful if you could write a review or even buy me a beer.
Thanks and good luck with the project 🙂