No WordPress user created after submitting Toolset User Form linked to WooCommerce payment. Also Shop page misconfigured.
Solution:
Expected behavior — form was set to "Create user" only on "Purchase complete." User is hidden until the WooCommerce order reaches "Completed" status. If payment fails or order stays in pending/processing/on-hold/cancelled, no user appears in WP Users.
Fix WooCommerce page setup: Shop page was set to Checkout. Set Cart, Checkout, My Account, and Shop to separate, distinct pages under WooCommerce → Settings → Advanced → Page setup.
Test end-to-end with Stripe sandbox or mark COD order as Completed manually in WooCommerce → Orders to confirm user creation triggers.
The client wanted users to view, edit, and delete their own posts from a “My Account” page and expected the View/Browse link to go directly to a specific Content Template. Attempts to link directly to the Content Template using Toolset’s link options and View shortcodes did not work as expected.
Solution:
In Toolset, Content Templates cannot be linked to directly. A Content Template is applied automatically when a visitor opens a post’s permalink. The correct approach is to link to the post URL itself. When the post is opened, Toolset renders it using the assigned Content Template for that post type.
For edit and delete actions, Toolset Forms’ built-in edit and delete post links should be used, as they correctly handle post IDs and permissions.
User created a classifieds site and wants to charge users for posting an “ad” (1 month / 6 months / 12 months) using Toolset Post Forms + Toolset Forms Commerce + WooCommerce.
The form redirects to the WooCommerce cart after submission, but the cart is empty (no product/billing info shows). The setup used “product based on custom field”, however no custom field was selected/mapped, so Toolset had no product to add to the cart.
Solution:
Connect the Toolset form submission to a WooCommerce product by mapping a Toolset custom field to WooCommerce Product IDs:
A YouTube video added via Toolset was visible while editing, but it did not display on the published (frontend) page. The user had already tested with LiteSpeed Cache disabled, switched to a default theme, and kept only Toolset plugins active, but the issue remained.
Solution:
The issue was traced to the Toolset Field Group settings: the field group name used Japanese characters, which caused the View/dynamic field detection to fail on the frontend. Renaming the field group to an English (Latin) name (e.g., “post”) and saving fixed the problem, after which the YouTube video displayed correctly on single posts.
I created a Repeatable Field Group “Opening time” and tried to add filters in a View, but the expected options don’t appear—only a grey, locked filter shows, and I can’t select additional filters.
Solution:
Set the View’s Content selection to the RFG (“Repeatable Field Groups from the current Gym > Opening Hours”); the owner filter is added and locked by design. Create a separate View to list the RFG items and insert it into the Gym Single Content Template (or use nested Views in legacy mode if building on a separate page).
Nous documentons les problèmes connus et leurs solutions dans Toolset erratas. Pour gagner du temps, vérifiez d’abord dans cette rubrique si le problème auquel vous êtes confronté est un problème connu. Cette liste est volontairement courte. À chaque publication d’extensions de Toolset, nous nous efforçons de résoudre tous les problèmes connus.
Politique d’assistance
Le personnel Toolset vous guidera volontiers pour utiliser correctement les extensions Toolset, vous fournir les informations dont vous avez besoin, vous aider à résoudre les problèmes et vous conseiller quant aux meilleures pratiques.
Merci de veiller à ce que chaque ticket d’incident ne référence qu’un seul incident.
