sales funnels

A FunnelKit SQL injection vulnerability led the host to suspend the user's site until they updated to the patched version.

A user says FunnelKit required senior-level manual fixes for checkout display, validation, import, server errors, and translations before it became usable.

Raw CSS appears above the checkout form after an integration issue, which another user says hurts buyer confidence and sales.

Adding a subscription to checkout broke the page during a sales campaign, creating urgent risk of lost revenue before the user fixed a vendor-provided snippet.

The user found malicious checkout scripts after a reported FunnelKit vulnerability, and support said the issue had been patched and backported.

FunnelKit could not create new funnels or edit existing ones because template and page edit screens were empty until support resolved loading.

Checkout shipping fields fail to expand on three sites, causing failed payments because billing address data is required.

A FunnelKit Automations Pro user found password reset emails fail when using an email address and requested an official patch.

FunnelKit crashes the WordPress post editor when used with the latest Bricks Builder, and support provided a fixed upcoming version.

FunnelKit Checkout does not correctly apply partial WooCommerce Account Funds credit during checkout.

FunnelKit templates hardcode fonts and colors on individual elements, making dark-mode and sitewide styling work tedious until the vendor updates templates.

CartFlows Field Editor breaks Polylang checkout field translations and leaves the user without a workable way to customize required fields per language.

A required phone field validates on credit-card checkout but is not visibly marked when customers use a PayPal payment button.

After a redesign, FunnelKit could not create or import funnels because missing database tables were not recreated until the user manually deleted plugin tables and reran verification.

A paid FunnelKit user cannot find how to edit thank-you page content and reports a confusing support system with untrackable tickets.

Raw CSS appeared inside the Checkout Block for MailPoet users until FunnelKit released a fix.

The user needed product-specific thank-you messages, then complained that the required rule feature is only available in the paid version.

CartFlows Pro analytics queries the wrong users table on multisite, causing database errors until the table reference is changed.

The reviewer says CartFlows is too limited in the free version, pushes upgrades, and requires an active subscription for future Pro updates.

CartFlows prevented customers from changing the shipping method after updating their address at checkout.

After a WordPress update, FunnelKit generated open_basedir PHP warnings every five seconds and significantly slowed the site.

A CartFlows reviewer says the lack of a predefined dark mode and difficult payment block customization are discouraging them from using the plugin.

The latest CartFlows version hid floating checkout field labels after input, and support provided a CSS workaround while escalating it.

Express checkout buttons fail to show on CartFlows checkout while they work with WooCommerce Blocks, and support moves the investigation to a private ticket.

CartFlows showed checkout fields that were disabled globally and in its own settings because of a conflict with another checkout field editor.

FunnelKit's Meta Pixel AddToCart event was not detected because the Woostify AJAX add-to-cart response did not return the expected WooCommerce data.

CartFlows checkout can hide the coupon input after a coupon is removed, preventing another coupon from being applied without a page refresh, though support could not reproduce it.

The mini cart often appeared empty even though checkout and cart data still contained products.

CartFlows checkout offers opened to a blank page for older funnels even after updating, while newly created funnels worked.