alexm

Will do 👍🏼

@kongondo awesome ok. I’m keeping a little doc of bits that I pick up on which I’m hoping will be constructive. it’s not a major issue being that I can edit the variations independently, it’s just that those master product pages with such high amounts of variations crash as one would expect. Fantastic job I must say! I tip my hat to you sir. You deserve every success coming to you with this project!

@kongondo where is best to submit a list of things I find. These aren't necessary issues, so didn't know if you want them submitted to Github as that's the frontend shop. One I have in mind is that I have a product with 711 variations (ridics I know) and I know we've discussed this before with your Variations module, which is integrated into Padloper 2 in a new form. But i'm wondering if you kept the pagination feature as my variations all show as one huge list.

@szabesz same for me. Excited to give it a spin! 🥳

@Roych No, you're not missing anything I don't think. @kongondo has been working on the docs and also putting together the repository and will then update everyone who registered interest via email I do believe.

@kongondo Gold baby! Digging for gold 😂

yessssssy! EXCITING

Thank you Santa @kongondo ! 😂😁

This! So it's not going to function as a front end store in the short term. Why would one do such a thing when I could wait and use something as delicious as PadLoper. Haha. It will be simply so invoices can be created quickly from the relevant stock items. It's my fault for not explaining in more detail. By all means, jump in and take a look. I'll fire over details once I've uploaded it in a mo 😁

SORRY! Missed your reply. My bad. 1. It is the product itself. 2. It does. 3. Yes, that would also be fine as it's a combination of 2 attributes. So it could just be Small Lilac like you say all in one column.

I have indeed expressed interest! 😁 Yup! Haha, mad. I've uploaded an example of the amount of colours for one T-shirt and the various sizes available, for your enjoyment ha. Insane. So those have all been added. Yeah so, I've not made it clear that I meant when editing the page like a donut. See screenshot with red arrows. I have added hook so that when the page is saved and a quantity has been entered for that row it grabs the price from the related product (col 1) and then adds it to the price field and calculated the line total. It would be awesome if there were a way to either output the available variant sizes and colours as separate selects say, or as one join column called variations. I applaud your efforts, patience and skill! It looks and sounds phenomenal based on the ongoing discussion in the PadLoper thread. Imagine if you drop it on Christmas... We could call you Santa? 😂

@kongondo I'll end up scrapping this setup once PadLoper is ready in the long run as I know it doesn't use pages now. So this is only a bridge really and there is no need to part with too much of your time considering this if it simply isn't straight forward. Thank you for your time.

@kongondo thank you for that. That means my set up is the best setup based on the way it works! Great work by the way!! 😊 I saw this in the product video demo way back! Great job again. Looking forward to hopefully testing alpha, if you approve and supporting the amazing task you've undertaken as and when purchasing is available. e.g. One has 396 variations Table not PageTable. Effectively I'm using it to create a kind of invoice page and the table acts as the items to invoice. I have a PageReference field which grabs a product. It would be awesome to be able to either, grab the product variation (though they aren't I understand that they aren't pages, so that is ruled out), then I could grab the associated information such as sizes and colours available. Then I thought that perhaps another way would be to grab the available variations for a Referenced page in the PageField and then output a dropdown of options to make it easy to pick. To be honest though, it's not a whole lot of effort to just type XL and Blue in 2 text fields failing there being a solution that you can see.

@kongondo I've got a work around, or solution the way I see it. Add a column called available and then just have all colours and sizes added and then just set "available" to false on the ones that aren't applicable. Would there be any performance impact with this. I can't seem to think of a better way other than having a lot of variation configurations.

Hey @kongondo just purchased this as I need to produce a kind of catalogue website for clothes and this seems to make life easier than adding lots of product-variation pages. A couple of questions though. Due to the fact that nearly every product has different combinations of sizes or colours, does that mean I have to create a new variation configuration for each item? Also I'm using ProFields: Table on order pages where the user can pick a product. Would there be any way of pulling in the product sizes into a field on the PageTable/have you ever tried anything similar. As there is (obviously) not a field type for Variations with ProFields Table, I guess perhaps a hook could work? Many Thanks