Vivek Acowebs
Forum Replies Created
-
Thank you for your interest in contributing to the plugin.
At the moment, we do not provide a public code repository or accept external code submissions / pull requests from third parties.
For bug reports, feature requests, suggestions, or compatibility issues, please continue using this support forum.
If you encounter a specific bug or have a feature request, kindly share the detailed use case, reproduction steps, screenshots, and environment details so we can review it properly.
In the free version, conditional logic works only with fields created within the same addon form. Conditions based on WooCommerce product attributes or variation selections are not supported.
To use conditional logic with product attributes or selected variations, you would need to upgrade to the Pro version.
Could you please share:
- A screenshot showing the issue clearly
- The product page URL where the issue occurs
Thank you for the detailed explanation.
Since the addon data is being saved correctly in the order item meta and is visible in the admin order details, the issue appears to be related to how the data is rendered in emails during asynchronous payment status updates.
We will review this in detail.
Please note that this forum is limited to support for the free version, and we’re unable to request backend access or perform detailed investigations here.
Based on the videos, it appears you are using the premium version of the plugin. If the issue persists, we recommend reaching out via the live chat on our website for further assistance.
To investigate this accurately, we’ll need to see the exact sequence where the issue occurs.
Could you please share a screen recording that includes:
- Adding product with addon fields
- Proceeding to checkout
- Performing a failed payment → retry → successful payment
- The resulting order emails received
- Admin order view showing addon data
Once we have that, we can pinpoint the issue.
You can first try adjusting this directly from the settings without making any code changes.
Update the hook and its priority, then verify if the output aligns as expected.Thank you for reporting this and for the helpful suggestion regarding wp_enqueue_media() usage.
This has now been corrected. The wp_enqueue_media() call has been removed from the latest release of the free plugin, so it will no longer be loaded across admin pages.
Please update to the latest version of the plugin, and the issue should be resolved.
Thank you again for bringing this to our attention and helping us improve the plugin.We understand how frustrating this.
Could you please confirm whether you tried deactivating all other plugins (except WooCommerce and our plugin) to isolate the issue? This step is important to determine whether the behavior is caused by a script conflict within the WordPress admin area.
Please note that due to forum limitations, we’re unable to request backend access here. If the issue persists after trying the above step, we recommend reaching out to us via the live chat on our website for more direct assistance.
You can achieve this from the plugin settings itself.
Please navigate to: Plugin Settings → Other Settings
There you will find the option: Hide empty fields in cartKindly enable this settings and try.
At the moment, the option to disable past dates in the date picker field is not available in the free version of the plugin. There is no built-in setting in the free version to restrict date selection based on past or future dates.
This type of date control (such as disabling past dates, setting minimum/maximum selectable dates) is supported only in the premium version, where advanced field restrictions and logic settings are available.
- This reply was modified 4 months, 1 week ago by Vivek Acowebs.
Our form builder relies on a drag-and-drop system that requires a stable DOM structure.
When another plugin modifies the WordPress admin DOM during editing, it can disrupt the drag state, resulting in items freezing, shifting, or dropping incorrectly.
This usually occurs after the page has been open for some time and is not caused by the form itself.
Please temporarily deactivate all plugins except WooCommerce and our plugin, then enable them one by one to identify the plugin causing the conflict.We have reviewed it and the following CSS for you:
.wcpa_wrap .wcpa_checkbox .wcpa_checkbox_custom {
border: 2px solid #000;
}Kindly add as additional css and check.
The issue is likely caused by a customized email template that is not rendering the order item meta correctly.
To help isolate this, please try the following checks:
* Temporarily switch to a default WordPress theme and test again
* Disable any email customization plugins and retestSince the WCPA values are already saved and visible in the order backend, no changes are required at the plugin level. The issue appears to be related to how order emails are being generated on this site.
If the requirement is to make a custom field mandatory on a simple product, this is already supported. You can enable this directly from the field settings:
Once enabled, customers will not be able to add the product to the cart unless they fill in or select a value for that field.
If your requirement differs, please share the exact scenario so we can review it and provide appropriate guidance.
