[Szilvia]

Thanks, I have success by disabling “High Performance mode”. If “High Performance mode” is not enabled, then each cart item update works as expected. Since it is Sunday and I have a lot of other tasks to do, I am happy with this quick fix for the time being.

Also, preparing a testing site takes about an hour, because of added security precautions I need to perform manually.

Maybe by sending you the logs when I am testing with “High Performance mode ON” will help you?

[Szilvia]

Thanks for the very quick reply! I am preparing a staging site for you to test, I’ll send it to you ASAP.

[Szilvia]

Thank you for your quick reply!

“It works without limitations, but will not receive automatic updates.”
That’s okay, I can live with it.

“Just remove the license information in Settings > WooCommerce Extended Coupon Features of your staging instance.”
I think it is just a temporary solution. Could you please consider removing the warning message from the log? Or at at least please make it possible to define staging domains somehow.

Whenever I start working on the staging instance I clone the database from production to the staging site. This means from now on I will also need to clear the license manually in order to get rid of the warning. I’m not very happy with performing unnecessary manual adjustments each time.

[Szilvia]

Thanx in advance!

[Szilvia]

Hello,

I have just updated from 2.5.5.1 to 2.6.0.2

“Invalid response block from server” errors are back. This time we get lots and lots of:
[16-Dec-2017 12:27:54 UTC] WooCommerce Extended Coupon Features error: Invalid response block from server

I tried to google but could not come up with too much. Maybe this is related?
https://wordpress.org/support/topic/invalid-response-cannot-render-graph/
also
“There isn’t a code, dos2unix is a tool which will help converting the files to unix format. It’s a command line tool.”

Is it possible that this is a result of you using Windows line breaks?

[Szilvia]

Hi,

Thanks for the reply! We have to apologize for the false alarm, you were right, we were running an old (2.3.x) version of the plugin.

It just happened that our license key validation was not working, because we moved the site in the not so distant past, completely forgetting to re-validate the plugin, and thinking that we were running the latest version.

v2.5.3 has not yet generated any php errors/notices so far (WordPress 4.8 + WooCommerce 3.1).
You can set this to [Resolved].

Regards,
Szilvia

[Szilvia]

Thank you for your reply!

We will take a look at the example next time. For the time being we decided “manually” handle our issue. If it happens frequently, we will need to solve it programatically.

Regards,
Szilvia

[Author]

Posts