Fauzan Azizie
Forum Replies Created
-
Forum: Plugins
In reply to: [SaveTo Wishlist Lite – WooCommerce Wishlist] TI Wishlist ImporterHi @lgs77717,
Good news, the TI WooCommerce Wishlist importer just shipped in SaveTo Wishlist Lite v1.0.6, along with importers for MoreConvert and WPC Smart Wishlist. So you can run it whenever you’re ready.And yes, you’re safe to import even though you’ve already started using SaveTo. No duplicates, no overwrites. Here’s why:
- Your existing SaveTo wishlists won’t be touched. The importer only brings over wishlists from TI.
- If you run it more than once, no worries. TI wishlists that were already imported just get skipped.
- Your TI data stays intact too. The importer copies it over rather than removing it, so your original data is always there if you need to fall back on it.
When you’re ready:
- Make sure TI WooCommerce Wishlist is still installed and active.
- Go to SaveTo Wishlist > Settings > Imports.
- Click the TI WooCommerce Wishlist card under “Select Import Source”.
Hi @adamstocklotstv ,
Thanks for the system report and the screenshots — that gave me what I needed.
What changed about the attribute dropdown
In a recent release we tightened up the Field Mapping picker so WooCommerce global attributes (the
pa_*taxonomy attributes) only appear in one group instead of two. Previously they showed up under both “Added Custom Attributes” and “Dynamic attributes”, which led to a lot of “which one do I pick?” confusion. They now live exclusively under “Dynamic attributes”.That’s why
pa packaging/pa_opakowaniedoesn’t appear under “Added Custom Attributes” anymore.What you should select
Looking at your screenshots, “Opakowanie” is set up as a WooCommerce global attribute (your Products > Attributes screen confirms it — slug
opakowanie, taxonomypa_opakowanie). For a global attribute, the correct choice in Field Mapping is:Dynamic attributes > Product Opakowanie
Not the “Opakowanie” entry under Added Custom Attributes — that one matches an unrelated post-meta key (likely from another plugin), not the taxonomy term assigned to your product. That’s why your feed was coming through without the packaging value.
Switch the mapping for
ilosc_sztuk_w_opakto “Product Opakowanie” under Dynamic attributes, save, and re-export. The feed should pick up the value (15 in your test product) again.About the CSV feed showing “Error”
That’s still worth a closer look. Could you also send a debug log so we can see what’s failing? Steps here:
https://adtribes.io/knowledge-base/send-your-debug-log-to-support/
Plus, briefly:
- Open the feed inside Manage Feeds and check for an inline error message
- Or open the feed URL in the browser and paste the message that appears
- Roughly how many products are included in this feed?
Two recent CSV-feed fixes shipped around the same time (an empty-batch handling bug and a multi-value separator fix). The debug log will tell us whether you’re hitting one of those or something else.
Hi @jusneale,
Since you mentioned you’re using the Pro version of the plugin, I’m not able to assist you here — the ww.wp.xz.cn support forum guidelines don’t allow support for commercial/premium products in this forum.
Could you please open a ticket with our premium support team instead? You can do that here: https://adtribes.io/my-account/support/
When you submit the ticket, it would help us get straight to a fix if you could include:
- A screenshot of your field mapping showing custom_label_0 and custom_label_1.
- A screenshot of the rules screen where they’re not appearing.
- The feed type you’re working on (Google Shopping, Facebook, etc.). We’ll take it from there on the premium side.
Thanks for understanding, and looking forward to helping you over on the AdTribes support portal!
Hi @adamstocklotstv,
Sorry to hear the feeds stopped working after the update. To help track this down, could you share:
- The exact error message — a screenshot of the feed error, or the message shown when the feed is opened/regenerated.
- Which feed is affected (Google Shopping, Facebook, etc.) and the file format (XML / CSV / TXT).
- A WooCommerce system status report — WooCommerce → Status → Get system report → Copy for support — pasted into your reply. This will tell us your plugin, WooCommerce, and WordPress versions in one go.
On the second point — “before the update, the system didn’t download attributes (I have them set to global)” — could you clarify? For example:
- Are these WooCommerce global attributes (pa_*, configured under Products → Attributes)?
- Which feed field were you mapping them to (e.g. color, size, material)?
- Are the attributes set on the parent product, the variations, or both? A screenshot of how the attribute is configured on the product, plus how it’s mapped in the feed rules, will let us reproduce what you’re seeing.
Thanks!
Hi @ecoshopee,
Thanks for reaching out!
We did send you an email asking for confirmation on your refund request but unfortunately didn’t hear back from you. Please check your inbox (and spam folder) in case it landed there.
As refund requests involve account and order details, we’re unable to handle them here per the WordPress forum guidelines. Please get in touch with us through our support channel and we’ll get this sorted for you right away:
https://adtribes.io/my-account/support/
Best regards,
Forum: Plugins
In reply to: [SaveTo Wishlist Lite – WooCommerce Wishlist] TI Wishlist ImporterHi @lgs77717,
Our dev team is currently working on the TI Wishlist importer — it should be available in the next update of SaveTo Wishlist Lite. We’ll keep you posted once it’s out!Hi @namespending,
Thanks for the extra context — that’s really helpful!
The “Wishlist / Backlog / Complete” use case for video games is a great example of how multiple fixed wishlists could work in practice, and it’s exactly the kind of detail that helps us scope the feature properly.I’ve forwarded your feedback to the team as a feature request, including your preferences around fixed names rather than customizable ones, and having it applied to all users — existing and new alike.
I’ll mark this thread as resolved for now and circle back once this lands in a release.
Thanks again for taking the time to share how you’d use it!
Hi @namespending,
You’re not missing anything — there currently isn’t a built-in way to automatically create 3 predefined wishlists for every customer.
Right now, here’s how it works:
- A single default wishlist is created automatically the first time a customer uses the wishlist feature. You can customize the name of this default wishlist:
How to Configure General Wishlist Settings - Multiple wishlists are supported, but customers create them themselves from their My Account page:
So at the moment, the closest option is enabling Multiple Wishlist mode and letting customers create their own lists.
That said, I really like your idea, so I’ve already submitted it as a feature request for our developers to consider.
To help us better understand the feature, could you share a bit more about your use case?
- What would the 3 wishlists be used for?
- Should the wishlist names be fixed or customizable?
- Should this apply to existing customers too, or only new signups?
Hi @webparaplan,
Thank you for confirming the number of users on your site.
With 6,000 users, the admin wishlist page is attempting to load all of them into the dropdown at once, which requires around 60 sequential API calls — that’s what’s causing the long load time and poor experience you’re seeing.
We’ve identified this as a scalability issue and have a fix planned for the next update. The fix will replace the current “load all users” approach with a search-as-you-type field, so instead of fetching all 6,000 users upfront, it will only query for matching users as you type a name.
This should make the page load near-instantly regardless of how many users your site has. We’ll update this thread once the new version is released.
Thanks for reporting this — it helps us improve the plugin for stores at scale like yours.Hi @supadigital,
Thanks for flagging this — sorry to hear your client’s site was affected!
The good news is that this vulnerability has been patched in WooCommerce Wholesale Lead Capture 2.0.3.2. Please update to the latest version (2.0.4.1) as soon as possible to secure your site.
For further assistance, please reach out through our premium support channel: https://wholesalesuiteplugin.com/my-account/support/
Note: As per the WordPress forum guidelines, we’re unable to discuss premium plugin issues here — our support team will be happy to help you over there!
Hi @webparaplan,
Thanks for reporting this — we’ve been looking into it and we think the slow loading on the “Select User” dropdown is related to how many registered users your site has.
Could you let us know roughly how many users/customers are registered on your site? You can check this under Users in your WordPress admin — the total count shows at the top of the page.
That’ll help us confirm the cause and prioritise the fix.Hi @peterbohus,
Really appreciate the kind words — and the great suggestion!
The “shopping list” use case is exactly the kind of real-world feedback that helps us build better features. You’ll be happy to hear we’ve added bulk “Add to Cart” to our future features list. We’re planning to let customers add all items — or select specific ones — to the cart straight from the wishlist page.
That said, it’s impressive you wired up a JS workaround yourself! Once we ship the built-in version, you’ll be able to remove that custom code.
We don’t have a specific ETA yet, but it’s on the roadmap. Keep an eye on plugin updates for when it lands.
Thanks again for the feedback — it genuinely helps shape where the plugin goes next.Hi @webparaplan,
I’ve raised this to the dev team to investigate as well.Hi @peterbohus,
Good news — we’ve identified the problem and it will be fixed in the upcoming update. We’ll keep you posted once it’s out!Hi @webparaplan,
The empty “Select User” field and missing products you’re seeing in the admin area are most likely caused by the All-In-One WP Security plugin. That plugin has a “User Enumeration Prevention” feature that blocks the request our plugin uses to load the user list — which explains why the field eventually populates after a delay (the security plugin’s rate-limiting kicks in, then releases). Here’s what you can try to confirm and fix this:
1. Go to WP Security > User Security > User Enumeration in your WordPress admin.
2. Temporarily disable the “Disable Users REST API” option.
3. Reload the SaveTo Wishlist admin page and check if the Select User field and Products now load correctly.
If that resolves it, you can keep that specific option disabled — our plugin needs access to the WordPress users list to populate the dropdown. The rest of All-In-One Security’s features will continue working normally.
We tested your public wishlist link and can confirm the wishlist itself is working correctly on the frontend. The issue is only on the admin side where the security plugin is interfering with the data loading.
Let us know how it goes!