kevin.bamber

Hey Komal,

Thanks for this, email received and patch applied.

We have migrated this onto production and everything appears to be working as expected.

Thanks for your help; marking as resolved.

Kevin

@komal-maru ,

Why is it that the second we purchased the plugin, based on the agreement that a fix is provided for the purchased version of that plugin, you have stopped replying?

I make reference to the following line within your final comment:
“If you are purchasing the Pro version, then please let us know, we shall provide the fix for it as the code is different in the Pro and Lite version”

I have uploaded the broken version of your pro plugin onto our staging environment pending fix, and can confirm that it is experiencing the same issues as the free version was prior to the original fix provided.

This is highly disappointing.

Please provide us with an update; or provide me with details w.r.t your money back policy.

Thanks,
Kevin

Hey @komal-maru ,

Any updates on the above?

Thanks,
Kevin

@komal-maru ,

Have instructed our client to go ahead and purchase the pro version of plugin. They will be sending us files so I can implement the fix and push to production.

Any chance you could point me to the fix for pro version so I can have everything I need in order to make this process as quick and efficient as possible?

Cheers,
Kevin

Komal,

We are being chased by our client here.

Could you please let me know what the ETA for pushing these fixes to production is like?

In terms of plugin structure, does the pro version match the free version? i.e. If we purchase the Pro version now, could we apply the same beta fix you provided me to that codebase, or if the wc-cpp-core php file doing different things / including different classes there?

Looking forward to hearing from you.

Thanks,
Kevin

Hey Komal,

Thanks for this, tested locally and it appears to have solved the issue.

Any chance you have an ETA as to when this will be pushed to a production version of your plugin, and whether it will also be applied to the pro version? (the latter being more important to us before going live)

Cheers,
Kevin

Hi Komal,

Its been 3 weeks since my initial bug-report.

I was under the impression that I was going to hear something from you last week; do you have any news for me?

Please provide a heads up if you feel like this bug fix is going to take much longer so I can look into and purchase a different plugin if needed; we need to go live with these changes to our client’s website ASAP.

Thanks,
Kevin

Hi Komal,

Thanks for your swift response and apologies for the delay from my end; I seem to have missed the email notification related to your reply.

Wondering if you have any updates since my team needs to start getting things in place for production.

Any idea of the E.T.A. on this?

Kind regards,
Kevin Bamber

Further to previous, in case it helps, I have provisioned the website (along with my plugin configurations) onto a publicly accessible staging server. https://igaming.staging-2.wbwgn.com/

https://igaming.staging-2.wbwgn.com/courses/responsible-gaming/ is a sample product utilising the default site currency (Euro); while https://igaming.staging-2.wbwgn.com/courses/affiliate-management/ makes use of the secondary (USD) currency.

For security purposes, I will only be able to provide you with Nginx credentials to visit the storefront privately.

Thanks,
Kevin Bamber,
Software Developer
BRND WGN

Hey, I’m having the same issues within the loop on the latest plugin version; but only on first click.

First time a user clicks on the Facebook link for a blog within an archive page, he/she is provided with generic content for that archive page. Second time, (without a need for refreshing) the content is correct.

URLs within data-counter-url and data-share-url parameters are correct

Any ideas? https://www.gasanmamo.com/the-company/blog/page/4/