| 开发者 | clixxcrm |
|---|---|
| 更新时间 | 2026年6月1日 20:31 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[clixxcrm_formulario hash="..."]clixxcrm folder to /wp-content/plugins/, or install the plugin through the WordPress plugins screen.Inside Clixx CRM, go to Settings > API and generate a token.
No. Form submissions are sent directly from the visitor's browser to your Clixx CRM via the public webhook endpoint.
Yes. The "Embed HTML" tab in each form has a built-in customizer with controls for button text, colors, spacing and typography, plus a live preview. The generated HTML is fully self-contained and can be pasted into any site (WordPress or not).
Yes. The "Clixx CRM Form" block lets you pick a form from a dropdown and adjust the iframe height in the inspector panel.
admin_head — it is now registered via wp_register_style / wp_enqueue_style and wp_add_inline_style, attached to a dedicated clixxcrm-menu-icon handle that loads on every admin page; (2) added == External services == section to the readme documenting the connection to app.clixx.com.br (/api/auth/verify, /api/anuncios, /api/webhook/inscricao/{hash}), what data is sent and when, plus links to the Clixx CRM Terms of Use and Privacy Policy; (3) the inline <style> / <script> tags inside the standalone Embed HTML snippet (which is meant to be COPY-PASTED into any external page, not enqueued by WordPress) are now assembled via concatenation and explicitly commented so they are not mistaken for WordPress front-end output.data-campos-extras no container e injeta os campos extras no preview ao vivo e no código copiado. Cores/sliders preservam os campos.campos_personalizados em /api/anuncios (já incluso). Limpe o cache do plugin (transient clixxcrm_anuncios) para puxar os campos novos.clixxcrm to clixx-crm to match the plugin slug on WordPress.org. All __(), _e(), esc_html__(), esc_attr_e(), etc. calls and the Text Domain: header + block.json textdomain were updated. Internal slugs (menu URL, option keys, postMessage protocol) kept as clixxcrm.Plugin URI from the plugin header (it pointed to the same URL as Author URI, which the WordPress.org submission validator rejects). Once the plugin is published, the canonical plugin page is wordpress.org/plugins/clixxcrm/.renderPreview removed. The cache-busting fix from 1.4.4 stays.CLIXXCRM_VERSION PHP constant was never being updated past 1.0.0 because of a too-strict regex (it required ') with no whitespace between, but the source file had ' )). Result: every release since 1.0.1 was shipped with the constant stuck at 1.0.0, which caused wp_enqueue_script(..., CLIXXCRM_VERSION) to always emit ?ver=1.0.0, so browsers reused the cached admin.js from the very first install. All previous "preview not updating" reports were caused by browsers serving the old admin.js.admin.js.renderPreview in try/catch with console.error to surface any silent failures..clx2-form selector in the embed CSS is rewritten to #unique-id .clx2-form before being injected. This gives the embed rules a specificity of (1,2,1)+, beating any WordPress admin rule. No iframe, no Shadow DOM, no CSP edge cases — just plain DOM with rewritten selectors.esc_attr on every echo), $_POST inputs run through sanitization helpers, view variables prefixed with clixxcrm_, heredoc strings replaced with concatenation, load_plugin_textdomain() removed (auto-loaded by core since 4.6).iframe.srcdoc instead of document.write() for reliability across security plugins / CSP setups.<iframe> to isolate the embedded form from WordPress admin global CSS rules. Without isolation, admin rules on input, form, button were overriding the embed's own styles, so only text changes were visible.opacity: 0.6 overlay.mb_strtoupper so accented characters such as Ã/Á are uppercased correctly.https://app.clixx.com.br. Override at development time via define('CLIXXCRM_API_URL', '...') in wp-config.php.[clixxcrm_formulario] shortcode and Gutenberg block.