Christina

Hello –

This happens with multiple websites with very different setups – I will send an email with details.

Thanks.

Just coming back to update – I did send in my bugs a month ago, they tell me they are working on them for the next version, but a new version has yet to be released.

I’ve also found more bugs, including vendors not being able to add products once their account is created and product filters breaking when this plugin is activated.

I have been patient but I’ve lost a lot of sales at this point, and have decided to remove this entirely from my website. This has been so disappointing, and again, a waste of time and money.

I have manually submitted to the email provided, just now, the various fatal errors and 404s this plugin causes to my site without my intervention.

I am happy to rescind my one-star review once it’s promptly addressed, otherwise, it stands.

I can’t submit a ticket through your support page because when I fill everything out the form does not submit. Have you tested your website in Microsoft Edge? And no, I won’t use Chrome.

Not sure why this was marked as resolved. I did go through and update to the versions that were released, but my problems still persist. I can give you the lines and files where you need to make the fixes, if this is not something you can handle. For being a paid plugin customer, this is ridiculous how broken this code is.

I’m using WooCommerce 8.3.1, and WordPres 6.4.2

Thanks for the tip! Would this get added to an upcoming update?

Sure, here’s the error with WooCommerce integration turned back on. Thank you for taking the time to look at this:

Warning: Trying to access array offset on value of type null REDACTED/wp-content/plugins/gtm-kit/src/Integration/WooCommerce.php?on line?866

Fatal error: Uncaught TypeError: TLA_Media\GTM_Kit\Integration\WooCommerce::get_item_data_tag(): Argument #3 ($index) must be of type int, null given, called in REDACTED/wp-content/plugins/gtm-kit/src/Integration/WooCommerce.php on line 863 and defined in REDACTED/wp-content/plugins/gtm-kit/src/Integration/WooCommerce.php:815

This is most definitely a bug – whether or not you consider this correct behavior now, the fact this change was not marked in the changelog and I had to go through and debug the input coming through to find the field just didn’t exist in the data anymore is nonsense.

My plugin is dependent on the _wpcf7 hidden field coming through so I know what form ID is being passed. That’s gone now. Why was this removed?

Yes! I just pushed the 3.0.0 version that fixes a LOT of bugs and added more documentation in regards to how to use it.

Thank you for posting this. It worked for me too. The documentation still doesn’t have this clearly stated. Plugin authors, please update your documentation!

No, the WordPress core is not installed in a subdirectory. But I will try turning off the Live Traffic. I will let you know in a couple days if this fix resolved the issue.

I had disabled WordFence because of the issue, but have re-enabled the plugin and with a retest, do not see the error. I will retest in two days and see if the problem remains fixed.

I can’t put a noindex on that link because it’s a query string.

I’m still seeing WordFence show up in Webmaster Tools. I want to make sure this is just lingering or if this is still an issue:

Instead of seeing
https://www.somedomain.com/wp-admin/admin-ajax.php?action=wordfence_logHuman&hid=123456... etc

As “Type”: Script and “Reason”: Blocked

I am now seeing this
https://www.somedomain.com/?wordfence_logHuman&hid=123456... etc

As “Type”: Script and “Reason”: Not Found

I’m also running into this issue. Any resolution from WordPress on this?

We ended up resolving this issue on our own by coding some changes to the paging and rewrite methods (not within our .htaccess, but the plugin itself, notably in wpbusdirman.php)

Thank you.