Everything looks good there. There is clearly something different in your setup than every other user of this plugin.
What versions of WordPress and each plugin are you using?
Do you have any PHP object cache setup?
Do you have any web cache setup?
What type of webhost are you using/testing this on? Some of the cheaper shared hosting plans force caching on the users.
If there is a bug keeping the plugin from working on your setup I am happy to fix it, but I can not reproduce your problem in the various configurations I have tried.
Hi @jamesgol, i have the plugin on two setups, one is online and another localhost.
I have a fresh xampp instalation and the latest release of wordpress, woocommerce and your plugin.
See the infos of my localhost on this link: http://bazara33.com/infos/info.html
And the versions of my wordpress: https://imgur.com/a/AIgQ4
My theme is the latest storefront ( from woocommerce )
You want to check my online instalation as well? They both are with this bug.
Do all of your setups run on Windows? I’m not sure anyone has ever tested that. I have no Windows devices to test on.
Though I really can’t imagine the Windows PHP would perform that differently. What the plugin does is very simple and I can’t think of any component that would respond differently.
If you send me information about your online site I could take a look and see if there is anything obvious going on. You can post information here or email me directly <james@gnuinter.net>. Please don’t post any credentials here.
Hi @jamesgol, the online setup is with linux, but my local setup ( wich i had created especially to reproduce the bug ) is windows.
You wanna see the phpinfo of the online or you need access to see what is going on? I can upload this version that i have created on my localhost and you can see everything in there. Ok? I wll send you credentials to access it.
I see you are using the development version of the plugin. Have you tried using the actual version that is released?
Yes! I started to get this bug with the latest release, but then i saw that you have committed some updates, and thought that those are fixes for this bug.
There’s definitely a bug on the development version related to this, due to not checking if items are expired. The method of checking changed completely since the release version so there should be no problem with the released version.
I’m working on the development version to resolve the issue there.
Wow, this is awkward! I had this bug, then i try everything until i found your git and then i tryed the developer version without succes either, and now this is working again? This is madness! hahaha well, thanks and sorry for waste your time!
In fact, i’ll fork some translations for Brazilian Portuguese soon.
The release version should have always worked unless WooCommerce made some change that broke compatibility (it’s always a moving target for something like this that pushes beyond expected behavior)
I did just update the development version, so if you would like to update and try that it should be working as expected again.
