This is NOT plug n play plugin

  • gcosoftware

    (@gcosoftware)


    2 weeks, 4 days ago

    In my opinion it only works after hours of senior-level work. This is not “plug and play”.
      
     I deployed FunnelKit as the checkout for a WooCommerce store. Yes, it has nice templates — but that’s where the upsides end.
     To get anything to actually work correctly, I had to manually work around a dozen-plus bugs. Specifically:       

     – The “Place order” button doesn’t show up without custom CSS — the plugin hides its own payment section and never reveals it.
     – A postcode marked “not required” still blocks the order (server-side validation ignores the UI setting) — fixing it requires PHP code.
     – The “Page Layout: Theme” setting in the UI simply doesn’t work — the header and footer disappear, and the only way to fix it is editing the database directly.
     – Exporting/importing a funnel between instances breaks editability — after import you can’t open the step in Elementor (“the content area was not found”); you have to rebuild everything by hand on production. If you were counting on a dev→production workflow, that’s a dealbreaker.
     – The default configuration triggers 502 errors on a typical nginx setup (a cookie storing the full price HTML overflows the buffers).
     – Cart message translations don’t work out of the box (wrong text domain) — they stay in English despite correct translations.
     – The form needs manual CSS to remove empty gaps and align the step bar — the visual panel isn’t enough.

    My WPstack runs on PHP8.4 so it is NOT old scrap, this plugin should works as other, but it takes one working day on making it usable.

     Bottom line: if you don’t have work experience with toptiers AI coding assist or you’re not a senior developer comfortable with PHP, CSS, nginx, and WordPress internals — you will not manage this plugin. From that perspective it looks like a half-finished product: a few pretty templates don’t make up for the lack of basic reliability. The whole point of a checkout plugin should be “it just works” — and that isn’t the case here.

    Disclaimer: I didn’t buy pay version, I’ve used and managed only free version, maybe in pay ver. works well.

    • This topic was modified 2 weeks, 4 days ago by gcosoftware. Reason: correct in number of stars rating
Viewing 1 replies (of 1 total)
  • Plugin Support Funnelkit Support

    (@supportfunnelkit)

    2 weeks, 3 days ago

    Hi @gcosoftware,

    Thank you for taking the time to share the details.

    First of all we really apologize for this experience, and as you can see we provide passionate support, and, we would request you to contact here because there are a few items that need more clarity.

    We would love the chance to look into each of these points with you, as several of them are not expected behavior and may be tied to specific server or theme configurations.

    We have done a deep analysis of this ticket today, and I met with our team lead to discuss this, and I’m putting in all the points of what we can figure out.

    – The “Place order” button doesn’t show up without custom CSS
    These sounds more like a theme conflict than anything else, because if you have to write custom CSS then surely there is some CSS that is bringing up, that is, That is causing the, place order button to hide.

    If you can inspect and give us the link to checkout page, we can look at the source of the CSS that might be doing this. So, we can easily inspect the source and see where this is coming from.

    — the plugin hides its own payment section and never reveals it.
    It’s not expected behavior. This often traces back to a theme or another plugin overriding the checkout output. Can you please share which payment gateway were you using? (e.g., Stripe, PayPal, Square, Braintree etc.)?

    – A postcode marked “not required” still blocks the order (server-side validation ignores the UI setting) fixing it requires PHP code.
    This depends on the WooCommerce internal process to keep the postcode required or optional based on the country and the payment gateway to process the order. Certain countries, state and cities to be Required.

    We will definitely take into consideration, this experience and see how we can improve and make it more clear in the UI.

    – The “Page Layout: Theme” setting in the UI simply doesn’t work — the header and footer disappear, and the only way to fix it is editing the database directly.
    For this we have the setting to switch to “Default template” to show the native header footer. By default the Funnelkit checkout templates are set to “Funnelkit Canvas For Page Builder”.
    https://funnelkit.com/docs/checkout-pages/how-to/enable-native-header-footer/

    You do not require to edit the database for this when we have the inbuilt setting for this to choose the template.

    – Exporting/importing a funnel between instances breaks editability — after import you can’t open the step in Elementor (“the content area was not found”);
    If the developer have created a custom WordPress page template for your theme that does not include the_content function then you will need to include the_content in your code to edit it with Elementor .

    Add the_content function into the page template’s code. Add the following line: <?php the_content(); ?>

    Secondly, there could be a potential permanent error as well that would have come up.

    This error is pretty common and it is documented in Elementor Documentation also
    https://elementor.com/help/the-content-area-was-not-found-error/

    – The default configuration triggers 502 errors on a typical nginx setup (a cookie storing the full price HTML overflows the buffers).
    We thoroughly reviewed and confirmed that there is no cookies from Funnelkit that bought the massive data. All the data are almost 3 to 4 bytes that are very negligible.

    Usually, the configured setup for cookies are around 2 MB. and if the store is already pre-loaded and there are other cookies creating from any other source and they are already in large value and you were just over the limit or even few bytes can change and that could have potentially triggered error, but we would love to know status report and check these values.

    This .md file for all the cookies stored by Funnelkit Builder Lite and PRO and Cart.
     https://www.dropbox.com/scl/fi/y70113gjrhubizzzrmg0z/COOKIE-AUDIT.md?rlkey=ef4ngvaa5ypelg4lfw2zsvnbz&e=1&dl=0

    We do understand if there is any kind of scope of improvement, so you should let us know. We are here to help.

    – Cart message translations don’t work out of the box (wrong text domain) — they stay in English despite correct translation.
    We discussed this with our product team and we are not getting any wrong text domain in the Funnelkit Builder Lite.

    Can you please share some instance where you found the wrong text domain or which particular cart message was not translated?

    This will help us if anything needs to be updated.

    – The form needs manual CSS to remove empty gaps and align the step bar — the visual panel isn’t enough.
     It seems your theme is adding any step bar on the top of checkout page because on the lite version of Funnelkit Builder, we do not offer the step bar as it comes only with the single step. We have tested with many themes but there could be a possibilty that any theme adding it. Let us know the theme name that you were using or if it was a custom theme.

    Our dev environment and customer success team have already moved to 8.4 (some on 8.5.x). We checked on our development server and there is no pending errors from our end. If there is any error on your site-specific, please share the error logs with us and we will take care of it.

    Could you open a ticket with us at our support channel and include your environment details (PHP version, theme, checkout page URL, and the funnel export if possible)?

    Happy to assist.

    Thanks
    Team Funnelkit


Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.