Support » Plugin: Cart66 Lite :: WordPress Ecommerce » pain in the butt

  • More trouble than it’s worth. No documentation for free version. Who knows if the paid version is worth the price?

Viewing 11 replies - 1 through 11 (of 11 total)
  • In regards to the Pro version, I have used it for a client and it works out pretty nice. It is worth well worth $89 IF you intend to use WebPayments Pro. (I don’t know if the same holds true for PayPal Payments Advanced I agree that on the surface if one wasn’t in the Pro version first, the lack of a typical “free” plugin support structure would cast doubt the viability of either product.

    Over a year later with a Cart 66 Pro and it has been a breeze for me to maintain for the client.

    Tonight I will be using the “Lite” version for another client in anticipation of an upgrade to the Pro once sales support intial dev costs. I promise that my mind and work load have washed/forgotten the stuff I had access to in the Pro forums (year support expired). All dev will be done from the pdf manual. Sure, might recall something, but I will get to live developing a cart minus any community forums chock full of “this happened to me, here is the cure”.

    FYI: Adding product to the existing client’s “Pro” version is stupid easy.

    As promised a follow up. After testing four carts incuding Woo Commece, two versions of WP EasyPaypal and the PayPal Payments Pro cart, I came back to Cart66Lite and had the cart up in about 2 hours. Five products, four with variations and two of those with three variations, (Color and Price). Using PayPal Standards this was easy with half my brain asleep at 2AM.
    I didn’t need anything but the PDF and that was to change the code on the checkout page to PayPal since it defaults to Mirijeh.
    Note: Client is hosted on GoDaddy. I just dont’ have the words to share in public to express my “love” for GoDaddy. Instead I would rather stick my hand in a garbage disposal. This works with GoDaddy whereas other popular shopping carts can have PHP config issues due to “GD’s” non-standard security uptightness.



    There’s some documentation available for free on the Cart66 website, though it isn’t obvious: look under “membership resources” (yes, counter-intuitive). But there’s a 60-day money-back guarantee anyway so you really have nothing to worry about.

    When we started with this cart last year for one of our sites, it was the only reputable solution with a proven track record that also allowed us to design our product pages exactly the way we want them.

    Other plugins had a pre-existing product page layout that users were forced to adopt. Nothing bad looking, but they did clash with our existing visuals…through Cart66 we were able to maintain our original vision for the site — plus, it was simple to use. We got the Pro version and support’s been quick and thorough, with DIY customization advice when we needed something more unique!

    Just adding the plugin crashed my whole site.
    Not worth it.

    Thanks for the review, Wudman

    @webdoc, just calling it as I see it. I did a lot of research before landing on Cart66/Cart66Pro. As a developer, I need stuff that works and has good support or is supported by documentation.

    I would also say with 8 uses of Cart66Pro/Lite, I have never seen a site crash. My best practices is to backup a site before adding any plugin (or making any major update if a daily backup isn’t automated). I’d put my money on the mentioned “crash” was due to another defective or conflicting plugin.

    Best practices for me is to only use plugins that are actively maintained and that are absolutely necessary for site function. That means routine plugin reviews. That review includes looking at the last entries in on the plugin’s page to see recent issues and how they are resolved.

    Totaly agree

    Hey Wudman, I bookmarked this thread cause we have the same idea about criteria for choosing plugins, or any open source software.

    I was wondering how cart66 is working out for you,

    and I also wonder what you do about choosing themes? Do you worry about theme lock-in?

    I learned and got burned by theme and plugin lock-in when I used to develop with Joomla. When it comes to WordPress, I was experienced and lucky. Like most WP developers, I tried to get away with free themes and got burned a few times.

    In 2008 while at CES in Las Vegas, it was clear I needed to find a dependable responsive framework solution. I ended up adopting a premium version of an responsive theme. After about a year, that theme developer persisted in following an ugly responsive , which prompted me to start testing other responsive frameworks.

    Because of how I was burned with a “pro” Joomla, I set some basic standards for my client sites.
    1. One time developer licensing fee
    – Never again will develop a client WP site where updates may be tied to renewing a membership. Clients should expect their site will work regardless if they have a relationship with the initial web developer. If a client chooses to change the theme with another developer, so be it, but it is bad policy that a client’s site would crash or generate errors when WP updates.
    2. Parent/Child framework
    – Nothing worse than a theme update trashing a site because the theme is overwritten regardless if you or the client causes the update.
    3. Clean “default” theme
    – Give me a blank palette. Why spend billable hours in “un-design” mode?
    4. Exclusive and robust “pro” forums
    – “Free” support is slow and available to anyone who thinks he/she is a web developer. “Make ’em pay and they go away” Pro forums tend to have less noise and experienced users that can step in with the right answer.
    5. Test, test, test!
    – When it was clear that the first developer I adopted for responsive design (2008), was focused on a clumsy implementation of responsive in his theme, I started looking for another solution.

    The first thing I did was set up several test sites, loaded with my core widget pack, menus and content. Then I would throw frameworks at these sites to see what happened. I landed on a framework that met my qualifications and then I quietly updated all my client sites for free.

    I have used that framework for 90% of my client and personal sites for the last three years.

    By the way, that first developer eventually fixed the responsive nature of the last theme I purchased from his company, but like the Eagles sing, “I’m already gone…”

    PS: I will be updating a Cart66Pro cart tomorrow. My client bought in after my research and recommendation. We have run the cart successfully and it has been incredibly profitable for him.

    Okay, I’ll bite. ha ha ha Which framework did you wind up using?

    Congrats on you and your client’s success. That’s pretty sweet.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘pain in the butt’ is closed to new replies.