Question about woocommerce compatibility

  • Woo is not compatible because of it’s dynamic content

    But isn’t it?

    If theme sends html with blank div in minicart icon, price field, quantity field, and update those with js, shouldn’t that make it wp2static compatible?

    Comments are not really an issue, because product pages have rating reviews. They are pre rendered, like product description. And customers feedback trough mail, not trough wp comments directly in product page

    That leave my account, cart and checkout pages as issue. Can’t those pages be excluded from wp2static conversion, as caching plugin does?

    All in, it means really only 3 small js queries in order to make it compatible

    So what it the issue with wp2static and woocommerce?

    Not trolling, is an honest noob question. I don’t fully understeand why cahing is ok, but static is not

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Leon Stafford

    (@leonstafford)

    Hi @leonardorodriguez,

    Good honest question.

    So, take WooCommerce in “Catalog mode”, I think it’s called. It’s just fetching content from DB and rendering it, so those sites convert to static fine.

    When it’s being used for orders, though, there is a user interaction – ie, add to cart, persist that cart across subsequent payloads. That’s where Woo can’t function when going static, as it still expects the DB there to handle that.

    A “client-side” cart, that only sits on top of the static site and uses a 3rd party’s server for processing orders / validating price hasn’t been tampered with by a user before checkout, doesn’t have any dependencies on your website’s backend.

    My tested and recommended one of these is Snipcart, but there are others.

    I started early this year on a Woo to Snipcart automagic conversion add-on for WP2Static, then got sidetracked by life, but aiming to have it ready for V7 launch. This will allow you to keep using Woo to create your eComms site, but offload just those parts that won’t work on a static site to Snipcart (first, other cart options should then be easy to replicate).

    This will have a large interested user base as many have already used Woo on their sites and want to go static. It will probably still be a recommended way for new sites, as Woo has such a developed ecosystem within WP with many addons and easy guides to follow out there.

    Another approach would be to use a dedicated Snipcart (or other static friendly cart option)’s WordPress plugin. Snipcart had one of these official plugins years ago, but made a decision not to maintain it, rather focus on being a “platform-agnostic” solution.

    At least one user I know has made their own custom Snipcart plugin for WP, so it’s not too hard and if you’re just selling a few products, it’s even easier. Snipcart just requires some CSS/JS included on any product pages and custom markup to denote what is a product, with attributes to set the SKU, price, variants, etc.

    Feel free to ping me again later to check on the progress of my Woo->Snipcart addon and in the meantime, explore whether a custom implementation of Snipcart (or other static friendly cart) without Woo would make sense for you.

    Lastly, there is a new static WordPress solution out there, called Sitesauce.app – they allow proxying back certain URLs to a WP development site. I don’t like the security hole that opens up for this scenario, but is definitely another option worth investigating.

    Cheers,

    Leon

    Plugin Author Leon Stafford

    (@leonstafford)

    When it’s being used for orders, though, there is a user interaction – ie, add to cart, persist that cart across subsequent payloads.

    ^ I may be technically inaccurate there, if the cart doesn’t need the DB, but certainly some user interactions with Woo to get all the way to checkout are expected to require the DB.

    Perhaps if using something like PayPal Express checkout, it can still work when going static?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Question about woocommerce compatibility’ is closed to new replies.