DrQuincy

I have used Shopify once a long time ago for something really simple and it worked quite well — and have used Opencart and the experience was absolutely horrendous. Plus a couple of others but most of the time I end up coding them myself for these reasons. I use libraries to speed things up but, in general, I find there is often something custom the client wants. With some systems even if this is a minor thing it can be impossible or a huge headache. Only yesterday a colleague was encouraging me to try Shopify again as he says there is very little you can't do with it and it has improved a lot since I last used it. I may do if I get the time but I am going to try Perch Shop as it looks interesting, PW + Snipcart and, when V3 goes into production, Padloper. Custom work is my bread and butter but of all the CMSs I have used Processwire is far superior to any others so an online shop module that works with it would be great so long as it is not restrictive. I don't go out of my way to do online shops as they aren't my favourite kind to build but I predict there will be a lot of this work around now as online sales have proved very effective during the pandemic.

Thanks. So the PW + Snipcart option is for lower volume of sales — but that's probably most of my clients anyway.

No worries, thanks and keep up the good work! All added to my list of things to try out. ?

Thanks @Gadgetto. After looking at your module and the docs you linked to this is looking like a very attractive offer and a good, solid product. I am particularly impressed that they validate the data from the referring URL. your module looks excellent too. So, it looks like your module brings most of what the client would need from Snipcart into the PW dashboard. That is a massive bonus as the fewer logins the client needs, the better. Sorry, what do you mean by this — do you mean it's undecided as to what the best way is? Thanks, is it possible to make the checkout load in page between your site's header and footer as opposed to in an overlay?

I'm very interested in this. Would you mind giving a brief summary as to how this works? In PW how do what field type do you use for product variations (e.g. size and colour of clothing)? Snipcart checkout is a popup on your site, right? If so, how much can you customise the look and flow? How easy is it to run code after failed and successful transactions so you can update stock, send emails, etc? Is it just like webhook endpoints in Stripe? Does Snipcart allow you to mitigate tampering with the basket? If you pass everything, including the price, to Snipcart via data-* attributes then the user could inspect the element and lower the price. Can you prevent this from happening? Thanks.

Thanks for this — very interesting. But how are Shopify only charging you $266? Is this what Shopify charge for the monthly fee, i.e. without the payment gateway? I thought they took something like 2.9% + 20c + monthly fee. Snipcart appears to be 2% + Stripe fees. Is the saving the fact Shopify charge a flat monthly fee and Snipcart take 2%? The actual payment gateway fees look similar.

Thanks, I'll have a look later. I take from what I have seen it that a JS library handles the cart and then it goes through to Snipcart for the payment. If this is the case do you have much control over payment pages flow and style? Also, I note that offer Inventory Management. How do you sync the inventory of Snip with PW. Or is that for if your site is static and can't do inventory management?

Hi Craig, With Snipcard, how does it work? Do you add the products to PW or Snipcart? What handles the payment gateway? E.g. Stripe.

Hi both! Yes, I have seen that thread! I think V3 is out of the question for now but was interested in what the state of V2 was. If it's not supported or widely used I might be best rolling my own if there is no suitable library either. I looked at Sylius and it seems like you can decouple what you want but is probably overkill for what I want. These are my concerns too. V2 is unspported and V3, even once ready, seems to be managed by one person. I am more than happy to pay but am a bit uneasy about putting all the eggs in the basket of a single developer. I'm thinking that I can just use a repeater for product options and the ID or a SKU field for mapping it to the basket. Is there anyone out there who is using Padloper V2 who can allay any of these concerns? I think PW is the best kept secret in the world of PHP CMSs (as in it hould be way more popular than it is) and initially thought it a shame there was no eCommerce capability. But it does bring me back to the point in my original post that it is difficult to create an eCommerce platform since requirements can be very specific so maybe it's as it should be. Having said that, on paper, Padloper does look very good from what I've seen.

I've used a lot of CMSs, frameworks and libraries over the years and have never really been blown away by any eCommerce platform. Padloper looks good though and I have a fairly simple online shop coming up. I am wondering whether to just code the cart and payment gateway parts myself on top of a PW install — or use Padloper 2. Given it is not supported would you still recommend its use? Are there a lot of people here using it in production and therefore you can get support here? It's a shame v3 is not ready yet. Are there any pure code cart and payment libraries or frameworks that can be easily plugged into PW via composer? Thanks!

That's it exactly, thanks Jens! ? I can confirm enable the option specified here shows the Trash option in the tree view.

I have added a user with restricted permissions; there are two templates that I have allowed them to delete. When you go into a page that belongs to one of these two templates the Delete tab is there and they can move it to the trash. They cannot see the trash though. What is missing though is if they hover over a page belonging to one of these templates is the Trash button. Is this expected behaviour (because the user cannot see the trash)? Is there any way to give a non-superuser the tree view Trash button for templates they can delete? I am not bothered about them seeing the trash in this instance but it is a shame they have to go into the page to delete it when there is potentially a button that can do it from the tree view. I did fund a thread where Ryan said non-superusers cannot be given access to the trash — does this still stand? Thank you!

Hi, I have done a few sites with PW now and love it — thanks so much for it. Up to now, I've done image resizing in the templates but this can make the font-end very slow when images are generated (but is fine for subsequent pages loads). To speed it up I have: Enabled client-side browser-resizing so huge images are scaled down before upload Added an InputfieldFile::fileAdded hook so images are re-sized in the admin so the front-end should never have to resize This seems to work great, I just wanted a second opinion to confirm that: Variations created this way will be deleted when the page is deleted, i.e. I do not need a fileDeleted hook The front-end will never re-generate the images (presuming the admin created them) when I call $image->size($imgWidth, $imgHeight) I believe the above two assumptions are correct; I just wanted it confirming. ? Thanks!

Ah, it's part of $input; I was looking in the wrong place. Thanks for the fast reply!

Hi, Loving PW, it's a shame it is not more widely known! I have paginated news items working fine but the page title is the same regardless of what page you're on. So, page 1, 2, 3…10, etc all have the title "News". Is there a way to get PW to automatically append the page number to the title. Or, how can you get the current page number and do it yourself? Thanks.