TD Shop Plugin Disables Standard WooCommerce Hooks

Posted in: Newspaper
Post count: 144

Hello,

I’ve run into an issue while working with the TD Shop plugin. It appears that none of the standard WooCommerce hooks are being triggered when the plugin is active. For example:

• woocommerce_before_add_to_cart_button
• woocommerce_before_variations_form
• woocommerce_before_add_to_cart_quantity
• woocommerce_after_add_to_cart_form

The same seems to apply to the Checkout page, where the following hooks are not firing:

• woocommerce_checkout_before_order_review
• woocommerce_review_order_before_shipping
• woocommerce_review_order_before_order_total

I’ve confirmed that disabling the TD Shop plugin restores the expected behavior—these hooks fire normally once the plugin is turned off. However, when TD Shop is active, these standard WooCommerce actions are no longer executed.

This limitation makes it difficult to utilize third-party plugins or custom functionality that rely on these hooks.

Do you happen to have a list of TD Shop-specific hooks or an alternative approach we could use to extend functionality in a compatible way?

Thanks in advance for your help.

Post count: 21065

Hello!

It shouldn’t affect those hooks like that; they should be fully compatible.
I’ll add this to our investigation list.

Thank you for understanding and letting us know!

Post count: 144

Hey Bettina,
Thanks for looking into this. I can confirm 100% it is not compatible, at least with version 12.7.

I created a short video showing / explaining the situation. https://pramadillo.s3.us-east-1.amazonaws.com/Monosnap_screencast_2025-04-22_10-30-59.mp4

Post count: 21065

Hello!

Ok. We will investigate and try to fix it as soon as possible.

Thank you for your insights!

Post count: 144

Hey Bettina,
Has there been any news/update on this? This is really hindering us from being able to utilize WooCommerce on multiple sites that rely on those hooks.

Thanks in advance.

Post count: 21065

Hello!

Unfortunately, I have not yet received an update.

Thank you for understanding!

Post count: 144

Hey Bettina,
It’s been another week, is there any update on this?

Post count: 21065

Hello!

Unfortunately, no.

Thank you!

Post count: 144

Hi Bettina. So, here’s our site we’ve been working on (BTW, we will be using this for MANY more regional magazine publishers here in the U.S.):

https://hartfordbusiness.emds.dev/product/paywall-bypass-link/?url=https://hartfordbusiness.emds.dev/article/test-subscriber-only-article/

As you can see, there is NO field for the URL bypass … this is a injected using standard WooCommerce hooks.

Alternatively, here is a link to exactly the same thing, but on a different site that uses Elementor instead of TagDiv:

https://obj.ca/product/article-bypass-link/?url=https://obj.ca/developers-hope-proposal-makes-ottawa-more-attractive-for-builders/

You can see here that the field, “URL to Bypass” has been injected into the product page. On this site, we’re using Elementor’s WooCommerce widgets, but they properly allow for WooCommerce hooks.

We REALLY need to get this working as we have large-scale publisher sites running TagDiv and WooCommerce and they need this kind of functionality … not only for this paywall bypass feature, but for other elements like gift subscriptions and group subscriptions.

We are willing to pay for special development for this. Would that help?

Post count: 35449

Hi,

We understand your situation and appreciate your patience. At this moment, there’s nothing we can do directly, as this issue requires a developer to check it out.

It is already on our list, and we hope the manager will assign it to a developer soon. However, please note that our team is currently going through a busy period, so it may take some time.

Thank you again for your understanding!

Post count: 144

I appreciate it, Calin. Please feel free to email me directly. I do realize and appreciate that you have a queue … we do as well. 🙂 As I mentioned, we’d be glad to pay whatever it takes to get special development focus on this.

Post count: 144

Hey Calin,

I was able to dig into this further and found the issue. The TD Woo plugin does execute the standard WooCommerce hooks, but it omits the global $product variable from the templates. Because of that, any plugin relying on global $product won’t function correctly.

Until a proper fix is in place, here’s a workaround that should help anyone else who runs into this:

global $product;
if ( is_null( $product ) ) {
if ( class_exists( ‘tdb_state_content’ ) && method_exists( ‘tdb_state_content’, ‘get_wp_query’ ) ) {
$current_product_id = tdb_state_content::get_wp_query()->queried_object_id;

if ( function_exists( ‘wc_get_product’ ) ) {
$product = wc_get_product( $current_product_id );
}
}
}

Hope that helps!

Post count: 35449

Hi,
I’m glad you were able to find a workaround and thank you so much for sharing it with the community! Your input is truly appreciated.

Post count: 25

Hi Calin,

I think I might have a similar problem. I noticed that several important WooCommerce plugins do not display on the product page when using the TagDiv Woo plugin on desktop – for example, WooCommerce Product Bundles, other bundle plugins, or the YITH Countdown plugin. Running these or similar plugins is important, but most of them do not support a shortcode workaround.

What can I do? What could be the issue? It’s clear that the tagdiv woo theme is not handling this correctly because everything works fine on Mobile Theme (mobile) and with other classic themes.

Thank you!

Post count: 35449

Hi Gpeter,

I believe the issue may be due to the fact that the additional plugins lack support for integration with the TagDiv Woo plugin (Woo templates). Since these plugins do not provide shortcodes, it becomes difficult to integrate them effectively with TagDiv Woo.

Thank you for your understanding.

Post count: 144

Calin, that’s not it. I can guarantee you that all of these WooCommerce add-on developers are not going to write special code just to support TagDiv themes.

The biggest issue is TagDiv’s lack of proper integration for standard WooCommerce hooks. THAT is what the various add-on developers are going to code for.

Hopefully TagDiv will implement changes similar to the one that we documented earlier in this thread.

When we manually added that code to one of our sites, magically the TagDiv WooCommerce blocks started working properly with add-ons like group subscriptions and more.

Post count: 35449

Hi,
This situation was reported to the developers 2 months ago. I just checked the thread and it appears to be assigned to a developer, but it hasn’t been addressed yet.
Thank you!

Viewing 17 posts - 1 through 17 (of 17 total)
You must be logged in to reply to this topic.