• wpuser

    (@cyela)


    After testing the plugin I decided to deactivate it and delete it, then the Woocommerce native checkout page stopped loading in Elementor, it just came with an error everytime, I checked the database and this pluging had left hundreds of pieces of information behind like tables and strings of code, I contacted the developers but they never replied, I had to reinstall the site compleatly to get rid of those errors, a waist of time! use it at your own risk.

    • This topic was modified 8 months ago by wpuser.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Adam @ WPCrafter

    (@wpcrafter)

    Thank you for taking the time to comment here, although I think you may have CartFlows confused with perhaps another plugin you use.

    1. You said “I contacted the developers but they never replied”. We searched our ticket desk as well as the support forum here and have never been contacted by you. You don’t become the most used and most recommended sales funnel builder for WordPress without providing top tier support. We respond to all tickets in under 24 hours unless it is the weekend. This goes for free users and Pro customers.

    2. You said “I checked the database and this pluging had left hundreds of pieces of information behind like tables and strings of code”. This is simply not accurate of CartFlows and anyone can install and verify this. First, CartFlows doesn’t add any tables to your WordPress database. Second, CartFlows, like all WordPress plugins, makes a few entries in the wp-options table (every plugin does this). It has no effect on your website or database, and as I said, every WordPress plugin does this. That’s what the wp-options table is there for, this is how WordPress works.

    3. You said “Woocommerce native checkout page stopped loading in Elementor”. The free version of Elementor does not let you design WooCommerce controlled pages like product page, shop page, cart page, checkout page, etc. These are features that you can have if you purchase Elementor Pro. But all of that has no relation to CartFlows.

    The core version of CartFlows allows you to create a new global checkout page using any page builder you choose. This is a side feature where the main feature is building sales funnels. To date, we have over 100k users that choose CartFlows to power their ecommerce website. We are hyper-focused on performance, simplicity, and enabling our users to maximize the sales of their ecommercce stores.

    If you want one of our engineers to look at your database to see what’s going on there, feel free to contact us via our ticket desk. However, it is a technical impossibility for CartFlows to have created any tables in your database.

    Thread Starter wpuser

    (@cyela)

    Bro, I know what I saw and what you plugin did to our site, I did send a message to your email address and they took more than a week to reply with some generic answer, I had to waist 3 days because of this, fortuntely it’s fixed now. BTW I was using a couple of different plugins to create custom checkout pages which worked fine, but after I installed this plugin they simply stopped working. Actually it was my fault because I should have known that wordpress developers are not the best and I should have taken more precautions.

    Plugin Contributor Adam @ WPCrafter

    (@wpcrafter)

    Well sorry for the mixup. Let me be clear here, we don’t have a support email address. There are only 2 ways to seek support:

    1. Here on WordPress.org where we have responded to everyone’s request
    2. The support request form on the CartFlows website which goes to our ticket desk. You would receive an immediate email confirmation and we respond to every request in under 24 hours, but many times it’s under 4 – 8 hours. Unless it’s the weekend.

    As I said, we have no record of a support ticket from you or anything related to the WordPress database. If we did have a ticket we would have responded to it promptly as we do for all of our users.

    We are sorry that you didn’t have a pleasant experience here and wish you the best.

    A generalization like “wordpress developers are not the best” is just plain ignorant, or more likely it’s projection… a reflection of their own inadequacies managing a WordPress site. Clearly cyela is not a developer or else they would have first backed up their site/db, and could have avoided the mess they got themselves into. Then again, the blame first types never think they’re at fault.

    As a WP dev, it’s frustrating to have to read these kinds of comments. If they actually wanted to address the issue, they’d have detailed their steps so that their particular issue could be replicated. But this just sounds like sour grapes because they couldn’t be bothered to mitigate the risks before trying a new plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Destructive plugin’ is closed to new replies.