Andrew Young

Hi there,

The plugin you’re referring to is Conditional Logic for Woo Product Add-ons, which works alongside the Product Add-ons plugin (https://woocommerce.com/products/product-add-ons/). Its purpose is to show or hide add-on fields based on specific conditions.

It’s not designed to store personalized offers or products in user accounts for later use. For your specific needs, you might want to explore plugins like Product Vendors (https://woocommerce.com/products/product-vendors/), or similar plugins, to turn your store into a vendor marketplace, which could offer more flexible product management features.

We hope this helps point you in the right direction!

Best regards,

Meow Crew

Hi there,

We just released a 2.1.5 version of the plugin, which contains compatibility fixes for Product Bundles. Can you please update the plugin to the latest version and let us know if all works fine on your side?

Thanks,

Meow Crew

• This reply was modified 1 month, 2 weeks ago by Andrew Young.

I understand why WooCommerce Fees and Discounts might need to store some of their own meta data, but there’s definitely no reason to save all product meta data. Many plugins, including ours, use meta fields to temporarily store data during cart or user sessions for plugin operations.

It seems like saving all meta data is the most straightforward approach, but it’s certainly not the best practice when it comes to ensuring compatibility with other plugins. Ideally, they should limit the meta data being saved to only what is absolutely necessary for their functionality to avoid unintended side effects.

Thanks again for letting us know, and we recommend reaching out to them to address this.

Hi there,

Thank you for reaching out, and I appreciate your detailed explanation of the issue.

The meta field rcbp_price_in_cart_recalculated is used in the cart to mark that the price for this product has been recalculated specifically for our integrations, such as add-ons and smart coupons, to not . This process is triggered by the hook woocommerce_before_calculate_totals (https://prnt.sc/ke41elagF9u7), and while it’s not absolutely necessary for role-based pricing alone, we use it to ensure compatibility with third-party plugins (to not affect the cost of addons, logic of coupon codes, etc). Therefore, when you comment that part, it won’t affect the price adjustments by plugin alone, but can broke how plugin works with Product Add-ons and Smart Coupons.

Here’s a summary of how the process works:

? When a product is added to the cart, the meta field rcbp_price_in_cart_recalculated is added to mark that the product price has been recalculated for the cart.

? Normally, this meta data is not saved to the database, and it’s only used during the cart session, so we didn’t affect the price once more when some extras are added to product cost, or product cost adjusted by other plugin also. Therefore, it should not affect other users or product prices across the store.

? However, it seems there might be a plugin or custom code in your setup that is causing these meta fields to be saved to the database, which is not intended behavior. This is likely why the price is marked as recalculated and affecting other users.

To resolve this, we recommend investigating how the meta data is being saved to the database. By default, WooCommerce and our plugin do not save this meta field beyond the cart session. It could be that another plugin or custom code is triggering the meta data to be stored.

Feel free to let us know if you need further assistance with identifying the source of this issue. We’re happy to help you troubleshoot further.

Can you also let us know which other threads and bad reviews you are referring to?

Thanks,

Meow Support

Hey,

We understand the issue you’re facing, and while adding an additional event listener is a potential workaround, we’re not sure if it’s the ideal long-term solution.

Just last week, WooCommerce released new versions of Product Add-ons (7.1) and Product Bundles (8.1+) with compatibility fixes. We’ve added this to our task list and plan to include extended compatibility in the next plugin update.

However, if you need a quicker resolution, we’d be happy to provide you with a beta version as soon as we have compatibility ready. Please feel free to reach out the way I mentioned earlier, and we’ll prioritize getting that to you.

Hi there,

Since you purchased the premium version, could you please reach out to us through the support channel inside your WP admin panel? To do so, go to Plugins > Conditional Logic for WooCommerce Product Add-Ons > Contact Us (https://prnt.sc/AfRP7J3Klmyu), then fill out this form: https://prnt.sc/YBkJ4S6KcdzU.

We’re not allowed to provide support for premium users through the forum due to wp.org policy.

Thank you!

Hi there,

Sure thing, happy to help!

I’m closing this ticket, as it seems there’s nothing more I can assist with at the moment. However, feel free to reply here if you need further clarification, or create a new ticket if you encounter something specific during troubleshooting.

Hi,

As far as we understand, this issue happens only after you’ve uploaded some product variations, and the memory exhaustion occurs on one specific page?

Since your situation is more complex than simply asking, “Would performance be better if…,” let us explain how the plugin and WooCommerce work in a nutshell, so you can debug and find the solution.

1. The WooCommerce Role Based Pricing plugin doesn’t calculate and display prices or price ranges directly. It uses WooCommerce hooks (e.g., woocommerce_get_price, woocommerce_get_variation_price) to send pricing data to WooCommerce, which then performs the necessary calculations.
2. In the case of variable products, WooCommerce caches the price calculations to avoid querying the database on every request. It uses WordPress’s transient API to store the price data temporarily. The most resource-intensive operation with variations is calculating the price ranges (_min_variation_price, _max_variation_price).
3. When WooCommerce needs to display the price of a variable product on the front end (e.g., in a product archive, single product page, or, in your case, the homepage), it checks the cached transients for the minimum and maximum variation prices. If these cached values exist, WooCommerce uses them directly, which speeds up page load times. If the transients are expired or missing (e.g., after product updates or cache clearing), WooCommerce recalculates the prices by querying the database for the variation prices and updates the transient values.
4. WooCommerce only recalculates variation prices under specific circumstances: when you manually edit the price of a variation in the admin, when the product’s status changes (e.g., from draft to published), when a variation’s sale period starts or ends, or if the transient cache expires (which can be controlled via hooks or cache plugins).
5. With the WooCommerce Role Based Pricing plugin, when a user role requests the price of a product that hasn’t been calculated yet and price ranges aren’t stored in the transient cache, WooCommerce processes the calculations for each variation (requested by the user). Once the calculations are complete, WooCommerce stores the data in transients. This process shouldn’t repeat unless the transients are cleared (due to the reasons listed in p.4).
6. By default, an average hosting plan should handle the operation of calculating price ranges and caching transients for a reasonable number of variations without hitting the memory limit. However, this depends on how many variations each variable product has, how many variable products are requested at the same time, and your server’s capacity.

Therefore, the issue with hitting the memory limit may be caused by several factors:

• It may happen only during the first pricing calculations for a new user role if too many products are requested at once and your server doesn’t have the capacity to process such queries.
• It may happen because something is triggering WooCommerce transients to be cleared, which means WooCommerce has to reprocess calculations and regenerate the cache repeatedly. This could happen for reasons listed in p.4 above, or because some plugins request transients to be cleared due to their specific needs.
• You may have a large number of variable products on the requested page (e.g., hundreds) with many variations in each product, and your server may not have the resources to process the query.

Recommendations:

You can use Query Monitor or any other plugin or server tool that helps identify bottlenecks and slow queries. Specifically, look for:

• Queries taking too long (generally anything above 0.1 seconds),
• Repeated queries (the same query running multiple times in one request),
• Queries by Component (to see if a specific plugin, theme, or even WooCommerce is responsible for the slow queries).

You can also track how long various Woo hooks and actions are taking to see what’s consuming the majority of server resources.

Additionally, check the number of variable products being requested on one page. It could be that you’re trying to load hundreds of variable products, and some of them don’t retrieve transient data, triggering WooCommerce to initiate calculations instead. In that case, it might be better to limit the number of variable products per page or use something like Lazy Load to retrieve data in smaller portions.

Hi there,

The Conditional Logic for WooCommerce Product Add-Ons is an extension of the official WooCommerce Product Add-Ons plugin. It enhances the functionality by adding “conditional logic,” which allows you to show or hide fields based on specific conditions.

It seems like you are looking to create extra fields for products, you should focus on the WooCommerce Product Add-Ons plugin itself, rather than the conditional logic extension. This base plugin allows you to add various types of fields to your products. Alternatively, you can explore other plugins that also support creating product add-ons.

Hello,

1. There are no shortcodes available to display pricing rules based on each user role. The plugin adjusts prices dynamically for user role\account using WooCommerce hooks. There are no database records that explicitly store “price for role X = XXX,” which could be used to create shortcodes with parameters for each role. We will add this feature to our backlog and may deliver it in the future.

2. The role-based pricing data is located in the wp_postmeta table, meta-key for role-based pricing rules is _role_based_pricing_rulesand_custome_based_pricing_rules for customer based pricing. 

Those are serialized strings associated with post_id (product id), and look something like this: 

a:2{s:13:"administrator";a:8{s:12:"pricing_type";s:4:"flat";s:13:"regular_price";d:10;s:10:"sale_price";
d:9;s:8:"discount";N;s:7:"minimum";i:2;s:7:"maximum";i:4;s:8:"group_of";i:1;s:10:"product_id"
;N;}s:6:"editor";a:8{s:12:"pricing_type";s:10:"percentage";s:13:"regular_price";N;s:10:"sale_price"
;N;s:8:"discount";d:20;s:7:"minimum";N;s:7:"maximum";N;s:8:"group_of";N;s:10:"product_id";N;}}

You can find there: 

• user role associated with pricing rule; 
• pricing_type can be “flat” and “percentage” 
• for flat pricing type – regular_price and sale_price
• for percentage pricing type – discount value
• and qty rules further – min qty, max qty and “gruoup_of” stands for qty step 

• This reply was modified 3 months, 1 week ago by Andrew Young.

Yes, the free version is limited to 1 condition per field, per product, or add-ons group. If you see this notice, you reached the limit – https://prnt.sc/WlfVQ-Y1UkHy. In your case, to set several conditions on the product level you should upgrade to the Premium version.

To create such a setup, you need two conditions: one for field #2 and another for field #3. Unfortunately, this is impossible with the wp.org plugin version. Could you please provide screenshots of how you added the conditions to the fields, and also send us a link to your product? This will help us see how it performs on the frontend. Thanks!

Hi there,

From your description, it seems like you are using the Premium version, not the one listed here on wp.org, since you have more than 1 condition set. Can you please reach out to us through the wp-admin, in the Plugins > Conditional Logic for Woo Product Add-ons > Contact Us (https://prnt.sc/B00Qyyvh14A-).

We’d need to see your setup and theme to help.

Thanks

Hi there,

We’re sorry to hear about the trouble, and thank you for bringing this to our attention. The glitch was tied to Freemius, which is common across many plugins, not just ours. We’ve updated Freemius in our latest release that was deployed today. So you can try it now.

If you run into any snags in the future, feel free to drop us a ticket. We usually sort things out pretty quickly, and it helps us all improve without the tough love of a 1-star review.

We’d be grateful if you could reconsider your review, as every star really supports our improvements.

Many thanks!

Hi there,

How do you expect it to work with Dokan? The plugin is called Conditional Logic for Woo Product Add-ons and it’s designed to add conditional logic (hide\show addons fields based on certain conditions) to WooCommerce Product Add-ons plugin.

If you use WooCommerce Product Add-ons plugin with Dokan in your project, then you can set conditional logic for Add-on fields using the instructions here. If you expect Conditional Logic for Woo Product Add-ons to add conditional logic feature to some Dokan instances – then no, plugin is designed for Woo Product Add-ons specifically.