Smoove connector for Elementor forms

smoove plugin will send contacts details via POST methode to smoove’s API
smoove is a marketing tool that allows you to create newsletters, SMS, marketing automations, CRM and more
link to the service:
https://rest.smoove.io
link to the service terms of use and privacy policies:
https://www.smoove.io/privacy-policy.aspx

1. In your Smoove account create an API key.
2. Please make sure that you have installed Elementor.
3. Go to plugins in your dashboard and select “Add New”.
4. Search for the Smoove connector for Elementor forms, install and activate.
5. Enter the “Smoove settings” in the plugin’s menu and enter the API key and follow the instructions in the description.

For any questions contact our support: https://www.smoove.io/contact-us.aspx

4.4.11

• Improved: the after-save validation now checks only the forms of the document being saved (a page, or a header/footer/popup template while editing it). Forms that belong to a different template rendered on the same screen are validated when that template is saved — so saving a page no longer warns about the footer’s form, and vice versa.

4.4.10

• Fixed: the after-save validation popup now reads form settings from the live Elementor document (and from the panel’s current model for the form being edited), so a form whose mailing-approval field was just mapped is no longer reported as unmapped on newer Elementor versions.
• Improved: the validation popup now shows the form’s name and element ID, making it clear which form on the page needs attention.

4.4.9

• Updated the “Tested up to” WordPress version and raised the minimum required PHP version to 7.4. No functional changes.

4.4.8

• Cleanup: all editor console logging is now off by default behind a single SMEF_DEBUG flag (set it to true in assets/js/editor.js to troubleshoot; smef_diag() / smef_regenerate() helpers appear only then).
• Cleanup: removed dead code from the editor script (unused legacy field-options function, disabled inline-validation functions and console test helpers). No functional changes.

4.4.7

• Fixed (root cause): the editor script relied solely on the ‘elementor:init’ event, which newer Elementor fires before footer scripts attach their listeners — so the entire field-mapping (and save-validation) logic never ran. The script now boots as soon as Elementor is ready (immediate check, init event, or short polling), restoring the field mapping on current Elementor while remaining compatible with older versions.

4.4.6

• Debug: Added step-by-step [SMOOVE] console logging for field-mapping generation, console helpers smef_diag() / smef_regenerate(), and a re-render guard that regenerates the mapping shortly after the smoove section opens.

4.4.5

• Fixed: Field mapping generation now locates the mapping controls even when newer Elementor renders them outside the panel view element (robust DOM root lookup).

4.4.4

• Fixed: Field mapping now reliably appears in the Elementor editor on current Elementor versions (robust multi-trigger loading; no longer depends only on a deprecated panel hook / MutationObserver).
• Security: Hardened the API logs table against SQL injection via the sort (orderby/order) parameters.
• Cleanup: Removed duplicated field-generation code in the editor script.

4.4.3

• Fixed: Fields mapping now displays correctly – restored dynamic field generation from version 4.2.0
• Fixed: JavaScript now properly creates field mapping controls for each form field
• Fixed: Restored original loading order (lists and fields together)
• Improved: Better error handling when lists fail to load

4.4.2

• Performance improvements: Fields load first (fast), then lists (slower)
• Bug fixes: Fixed syntax errors and improved error handling
• Better user experience: Fields mapping appears immediately
• Removed caching to ensure always fresh data from Smoove API

4.4.1

• Removed caching system for real-time data
• Improved API request efficiency

4.4.0

• Added caching system (later removed in 4.4.1)
• Optimized list fetching loop

02/04/2024