Plugin Atlas
Forum Replies Created
-
Hi @riccardo,
Thank you for reporting this — you’re right, the v3.0.8 fix was not sufficient for sites using Redis or Memcached.
Root cause: The clean_taxonomy_cache() function used in v3.0.8 does not invalidate the WP_Term_Query cache group
(term-queries), which is where get_terms() stores its results. On sites with persistent object cache, this caused
stale or empty results after the first brand was processed, effectively stopping the transfer after just one brand.The fix (v3.0.9): We’ve replaced the cached WordPress functions (get_terms(), wp_count_terms()) with direct database
queries that bypass the object cache layer entirely. This works reliably regardless of your caching setup.You do not need to disable Redis. Simply update the plugin to v3.0.9 (now available) and run the transfer again. All
your brands should transfer correctly this time.If you had a partial transfer from a previous attempt, I’d recommend using the Rollback button first to restore the
original state, then running the transfer fresh.Please let me know if you run into any issues after updating.
Hi @paul8411,
Thank you for the detailed report – this was very helpful in identifying the root cause.
The issue has been fixed in version 3.0.8, which is now live on ww.wp.xz.cn. You should see the update available in
your WordPress dashboard.What was happening:
When transferring brands from PWB, the plugin was encountering a cache issue on sites using persistent object cache
(Redis, Memcached, or similar). After transferring the first brand, get_terms() was returning stale/cached results,
causing subsequent terms to appear empty. Additionally, any term creation error would halt the entire transfer instead
of skipping and continuing.What 3.0.8 fixes:
- Cache is now properly cleared between each batch AJAX call, so all brands are correctly fetched
- Term creation errors no longer stop the entire transfer – failed terms are skipped with a log entry, and processing
continues - Better debug logging to help troubleshoot if any issues remain
Please update to 3.0.8 and run the transfer again. All your PWB brands should transfer correctly now.
If you still experience any issues after updating, please enable Debug Mode in the plugin settings and share the log –
it will help us investigate further.Best regards,
KostasHi fcdigital,
Thanks for reporting this issue.
About the Spanish error message: This message (“Es necesario asignar un nombre a este término”) comes from WordPress
core, not our plugin. Your WordPress is set to Spanish, so WordPress displays its errors in Spanish. Our plugin is
English-only.What’s happening: Your Perfect Brands database contains at least one brand with an empty name (possibly corrupted
data). When our plugin tries to create this term, WordPress rejects it.The fix: Version 3.0.7 will:
- Skip brands with empty names gracefully (instead of stopping)
- Preserve original slugs to maintain your SEO URLs
Your URLs like cervezasadomicilio.mx/marca/cerveza-1993-beer/ will remain exactly the same after migration.
We’ll release 3.0.7 shortly. In the meantime, you may want to check your PWB brands for any with empty names.
Best regards
Forum: Plugins
In reply to: [Transfer Brands for WooCommerce] Plugin Not workingHi John,
Thank you for reaching out. I’ve just released version 3.0.6 which fixes several issues that could cause transfers to
fail silently.Please try these steps:
- Update the plugin to version 3.0.6 (available now)
- Enable WooCommerce Brands feature – Go to WooCommerce → Settings → Advanced → Features and enable “Brands”. This is
required for WooCommerce to fully recognize the product_brand taxonomy. - Verify settings – In the plugin settings, make sure:
- Source: “pwb-brand” (Perfect Brands)
- Destination: “product_brand” (WooCommerce Brands)
- Run the transfer again – The new version has better error reporting
If it still doesn’t work, please share:
- A screenshot of the plugin settings page
- A screenshot of what happens after clicking “Start Transfer” (any messages shown)
- Whether you see any brands listed in Products → Brands after the transfer
The v3.0.6 fixes include improved backup verification and better error handling that should either complete the
transfer successfully or show you exactly what went wrong.Thank you,
KostasHi @provet,
Thank you for the detailed report and analysis results.
Regarding the counts showing 0/0 but Total: 748:
This typically means those 748 products don’t have a brand in the source taxonomy (pwb-brand from Perfect Brands) but
exist in your catalog. The plugin only counts products that have a source brand to transfer.A few things to check:
- Source taxonomy setting – Make sure “pwb-brand” is selected as the source (not “pa_brand”). Version 3.0.6 now
auto-detects Perfect Brands on activation. - Already transferred – If you already ran a transfer, those products may have already moved to product_brand and no
longer have pwb-brand assignments. - WooCommerce Brands feature flag – I notice it’s disabled. Try enabling it at WooCommerce → Settings → Advanced →
Features → Brands. This ensures WooCommerce fully recognizes the product_brand taxonomy.
Regarding showing products with multiple brands:
This is a valid feature request. I’ll add a clickable link in the “Potential Issues” section that shows the actual
product names/IDs with multiple brands, so you don’t have to search manually or run the full migration.Next steps:
- Please update to version 3.0.6 (just released) which includes reliability improvements
- Enable the WooCommerce Brands feature flag
- Verify your source taxonomy is set to “pwb-brand”
- Run the analysis again
If the issue persists after these steps, please share a screenshot of your plugin settings page so I can investigate
further.Best regards,
KostasForum: Plugins
In reply to: [Transfer Brands for WooCommerce] Analysis Results: Invalid taxonomy.Hi,
Thanks for reporting this issue! I’ve just released version 2.8.5 which adds full support for Perfect Brands for
WooCommerce (and YITH WooCommerce Brands too).The issue was that our plugin was designed for WooCommerce product attributes (pa_*), but Perfect Brands uses a
custom taxonomy (pwb-brand) which works differently.To fix your issue:
- Update to version 2.8.5 (should be available on ww.wp.xz.cn within 15 minutes)
- Go to WooCommerce → Transfer Brands → Settings
- In the “Source Attribute Taxonomy” dropdown, you’ll now see a “Brand Plugins” section
- Select “Perfect Brands (pwb-brand)”
- Save settings, then run the transfer
Let me know if you have any questions!
Thank you for your reply.
Forum: Plugins
In reply to: [WooCommerce] How to migrate to the new brand featureHi @shawnpita, @tecazwebdev, @mgz069, and @seanconklin,
I’ve been following this thread as I’ve developed a specific solution for this exact migration problem that many store owners are facing with WooCommerce’s new brand feature. The Migration Challenge
When WooCommerce introduced the brand feature (and especially with the upcoming WooCommerce 9.6 where it will be enabled by default), they created a significant migration challenge for stores with existing brand attributes. As @doublezed2 from WooCommerce support mentioned, they don’t provide an automated way to do this.
The manual SQL approach that @seanconklin suggested can work but carries significant risks:
- It doesn’t transfer custom fields like your brand_logo and brand_banner
- Direct SQL manipulation can lead to data loss without proper backups
- It doesn’t account for custom brand attributes (non-taxonomy ones)
- It can break existing product relationships
Automated Solution
To address this need, I’ve developed a ww.wp.xz.cn plugin called Transfer Brands for WooCommerce that specifically:
- Safely migrates both taxonomy-based attributes (like your pa_brand) and custom attributes to the new product_brand taxonomy
- Preserves all brand images and custom fields during transfer
- Includes a complete backup and rollback system for risk-free migration
- Shows real-time progress with detailed statistics
- Offers a pre-transfer analysis tool so you know exactly what will be migrated
For your specific case with brand_logo and brand_banner custom fields, the plugin can be extended to transfer those as well to the appropriate term meta for the new taxonomy. Why This Is Better Than Manual Migration
- Zero SQL knowledge required – everything is handled through a simple UI
- Safe rollback capability – if anything goes wrong, you can restore your previous setup with one click
- SEO preservation – maintains all your brand relationships without breaking URLs
- Custom field support – transfers brand images and can be extended for your custom fields
- Batch processing – handles stores of any size without timeouts
You can install it directly from your WordPress dashboard or download it from ww.wp.xz.cn.
Hope this helps solve the migration challenges you’ve been facing!
Kostas
Forum: Plugins
In reply to: [Advanced Custom Fields (ACF®)] Saving a Product – ACF Pro caused Errori have the same problem, when i am saving a product after the latest ACF 6.0.0 update i got an error.
Any updates please ?
thank you
Yes! Understood! I create ticket to your help center!
Thank you!
> I’m most confused on, why isn’t this in WooCommerce core yet.
I’m confused too why this isn’t in Woocommerce core..
Please ask them and update this post.> You might try another monitor after enabling the keys.
Please check the new 10min monitor with the keys enabled.. (id dY8YQJZq)PS. i also enabled redis object cache after new keys.
Thank you!
- This reply was modified 4 years, 4 months ago by Plugin Atlas.
Thank you for your fast reply.
Yes it does that in 5.2.63 but the EAN doesn’t showing in XML feed, i try both values “woo_feed_identifier_ean” and “woo_feed_ean”.
The only value showing in the XML feed is only this —> <ean/> if the feed is filled with EAN or is empty.Hi,
I revert to the older version 2.0.6 and everything works perfectly but i dont have the latest version of wordpress and woocommerce.
My current WordPress ver is and 5.5.3 and woocommerce ver 4.7.1 so if i update the latest versions of wordpress to v 4.6 and woocommerce ver 4.8 wi llthe version 2.0.6 of Woof will work on these versions of wordpress and woocommerce ?
Thank you..
KostasHi!
I have the same problem since your latest BEAR update.
Binded editing doesnt work correctly.
PS. i dont have cache plugin on website.
Any news about newer update ?
Thank you
Hi!
Are you kidding me? I sent 3 emails to your support, one a week ago, one in about 3 months and one older and nobody answered.
It’s very bad not to answer especially to your premium members that bought your plugins.You have very good plugins but you ruine all this work with your bad support!
I wish you will fix this in the future because it seems that you don’t give a damn if someone pays for your plugins.
Ps. Remove from your banners that you have good support 24/7.Best regards
Kostas.