bitpresssupport
Forum Replies Created
-
Hi there, thank you for reaching out to us.
Currently, Bit Form does not have the feature to call an existing record (e.g. custom post type/PODS) as an edit.
We are working for so many upcoming awesome features enlisted in our roadmap. we added your request to our roadmap, and hopefully, we will start for this feature after we release the feature updates in the queue. Thank you for having patience and for supporting us.
Request for a feature here is the link: https://www.facebook.com/groups/bitapps/posts/4088723257806464/
Please let us know if you have any further questions or concerns.
Thank you.
Hi @newshop
Currently, Bit Forms doesn’t have compatibility with WPML.
If we get enough user requests, we will check the possibilities and feasibilities. You can request here for more features.
Link: https://www.facebook.com/groups/bitapps/permalink/4088723257806464
Thank you,
Bit Apps Support.Hello Newshop! To remove the Bitform stylesheet for a specific form, you’ll need to concatenate the form ID to the style handle when using the wp_dequeue_style and wp_deregister_style functions. For example, if your form ID is 24, you would use the following code instead:
add_action(‘wp_enqueue_scripts’,’custom_remove_styles’,1000);
function custom_remove_styles() {
wp_dequeue_style(‘bitform-style24’);
wp_deregister_style(‘bitform-style24’);
}This should prevent the stylesheet from being loaded for the specified form. Let me know if you have any other questions or if this solution doesn’t work for you. Thanks!
- This reply was modified 3 years, 2 months ago by bitpresssupport.
At Bit Integrations, we integrate any new release with the core plugin. This is why you are currently seeing the default MailPoet field in the field mapping option. In addition, we are always open to adding more fields based on user requests. Our developer team is currently exploring the possibilities for expanding the available fields.Please enable Google Sheet API and Google Drive API from Library.
Please check the video link: https://www.loom.com/share/8782881192744fc0a8093b9014a30df1We apologize for the inconvenience you faced with the styling of success messages. Our development team has taken your feedback into consideration and added readable classes for success and error messages.
We recommend please upgrade to the latest version of the Bit Form (2.0.3 for the free version and 2.0.2 for the pro version) to apply the fix. Thank you for your valuable feedback and we hope this solution works well for you.
Thank you for your patience while we worked to resolve the issue with the missing attachments in the email. We’re happy to inform you that our development team has resolved the issue. Please upgrade to the latest version of the Bit Form (2.0.3 for the free version and 2.0.2 for the pro version) to apply the fix and verify that the attachments are now included in your emails. If you encounter any further issues, please do not hesitate to let us know. Thank you for your understanding and support.
We are sorry for the inconvenience. Our developers are currently investigating the issue you reported regarding the missing attachments in the email. We understand the importance of this feature and we are doing our best to resolve the issue as soon as possible. We will keep you updated on the progress and provide a solution once the issue is resolved. Thank you for your patience and understanding.
Thank you for letting us know about this issue. We have already forwarded the issue to the development team. We apologize for any inconvenience this may have caused and assure you that the issue will be resolved in the next update.
We are pleased to let you know that the plugin has been updated and the issue has been resolved. Please update the plugin and check if the problem has been resolved.
If you are still experiencing the same issue after updating the plugin, please don’t hesitate to contact us at [email protected]. We are always here to assist you.
We are happy to inform you that we have updated the plugin, and now the “Entry ID,” “Form ID,” “Title,” and “Date Created,” is included in the field mapping option.
We have also tested the duplicate record trigger for Gravity forms, and it is working perfectly on our end. We recommend updating the plugin to the latest version and checking if the issue persists.
However, if you still face the duplicate issue after updating the plugin, please do not hesitate to contact us at [email protected], and we will be happy to assist you.
Forum: Plugins
In reply to: [File Manager] Window width and theme selectionWe appreciate your interest in our product. We have taken note of your suggestion regarding Bit File Manager. We will consider and check the feasibility.
Thank you for your feedback
Our developer team checks the issue you are facing. SKU element of the woo-commerce product, Suppose a woo-commerce product is ordered. Then we extract the info of the product. Somehow trigger is executed without the product and our function is unable to get info and this type of error occurs. We check out our end. Everything works fine. If you are still encountering this issue, please send an email to [email protected].
We would be grateful for the opportunity to assist you in resolving the issue. Thank you for your understandingDear Daniel Fernandez,
We appreciate you bringing this matter to our attention. Currently, when we release an integration, it is integrated with the core plugin. As a result, Bit Integrations only displays the available fields in the field mapping option that are present in the form field.
However, we will take your feedback into consideration and have a discussion with our development team to see what can be done to improve this situation. Thank you for your input.
Hello @jkp2015
In the next version, FormCraft will be included in the trigger list of Bit Integration.
Thank you,
Bit Apps Support Team.