kongondo

Yes. Works for me. Good catch ?.

Now it does, thanks ?. Thank you very much for the very clear and detailed explanation. My confusion is over ?.

Great timing then @alexmas I recently updated the demo to actually show the available colours and sizes of variants. I will update the repo soon. Later today, I'll also write some code here to look at since the demo one is a bit opinionated.

Thanks @horstfor enlightening me. Some of the confusion is gone. I still don't get why you would version a field or template (not template file) though ?.

Hi @alexm. Just to be clear, do you mean you want to list all the available colours and available sizes of a selected product? E.g Product A is available in Black, Red, Purple, etc. and Small, Medium, X-Large?

I have been reading these posts with great interest but also a great deal of confusion. It seems that there are maybe 3 conversations going on simultaneously. Or maybe they are one and the same (or sides of the same 3-sided coin ?) and it is me who is not getting it. I suspect the latter. #1 Conversation 1: Create fields and templates quickly using a configuration file. #2 Conversation 2: Deploying sites from local to production. #3 Conversation 3: Versioning fields and templates. It is #3 that I don't understand at all. Maybe this is because I always use #2 in my 'deploy to production' strategy. This is not a criticism against #3. I genuinely don't understand why you would need to version templates and fields (but especially templates). I have read most of the posts but it is still not sinking in. Could someone please briefly explain this (i.e., why one would want to version templates and fields)? By versioning a field, for instance, does it mean that if the field label or description, etc. changes, that you need to be able to roll back those changes? Something more complicated than that? Please don't' laugh ?.I am probably exposing my ignorance here but happy to learn ?. Thanks.

Shopify has several APIs for this with multiple SDKs. Have a look and choose one that suits you.

Excellent! Please post (start a new topic) in this new support board whenever you are ready, thanks.

Please note that Padloper 2-related pre-sales support has been moved to its own sub-boards in the open forums. Please read the pinned topic 'About this Board' in the board. Thanks. https://processwire.com/talk/forum/62-padloper-pre-sales/

Done! ? Thanks. https://processwire.com/talk/forum/62-padloper-pre-sales/

This is a temporary board for Padloper 2 pre-sales issues. Is is intended for general pre-sales questions and more specific Padloper 2 topics such as technical/coding questions, bug reports, documentation, feature requests (wishlist) or anything related to Padloper 2. For paid support for Padloper 1, please continue to use the existing VIP Support Board. This open board for Padloper 2 is necessary as it allows non-Padloper 1 users access to a support forum. Please note that once Padloper 2 is officially released, these boards will likely be merged into one. VIP Support will continue but it may happen in an open board with priority given to those with active subscriptions. Padloper 1 topics would be archived (but accessible). Thanks.

Hi @alexm. Pete is currently helping me with this. Hopefully this week, we'll have a 'pre-sales' forum that anyone can access. We'll use that for issues, wish list, etc. Ideally, we could have done issues in GitHub but Padloper is not an open project. Both pagination and lazy-loading have not yet been implemented. They are high on my todo list, especially the latter.

Since you cannot get access to your developer and since it seems you will not be getting a replacement developer for this, I would suggest, albeit with caution/caveats, that you take over the current superuser account. This will mean changing the following: The current superuser password The current superuser email If needed, the current superuser username 1 and 2 are more important. 1, since you need to be able to log in and 2 since you want ProcessWire to send messages (when needed) to an email account you have access and control over. The above requires that you have access to the ProcessWire files. This can be either via FTP or CPanel. In any case, you need to be able to edit at least a template file. Please let me know. Please don't post your FTP/CPanel details here ?. At this point, we just need a yes or no response if you have access to files. By the way, if you'd rather discuss via PM, please feel free to message me here in the forums.

I don't think this is a fair comparison. You can easily create a form, have it submitted (including uploads -> to some tmp folder), create a page if happy with the uploads, save it, move your uploads to the file/image fields, then save again. No orphan pages. I believe your issue is because you are calling $page->getInputfields(). This calls all the fields on that page's template, including your image field. Being a new page, you cannot add (as has been pointed out) to that field unless the page is saved. One reason is that ProcessWire stores a page's files in the page's assets folder (site/assets/files). E.g., site/assets/files/1234/some_image.jpg. Without saving the page first, there is no folder 1234, hence there is no destination for your image. Unless I've forgotten something, this is one of the explanations. Above means that to get around this, create your own form with your own file upload field instead of relying on $page->getInputfields(). This way you can handle the uploads yourself and only create a new page when satisfied with the sanitisation and validation. Alternatively, call $page->getInputfields() with the $fieldName argument (in your case an array) that exclude your image field. I haven't tested this approach, but I think it should work.

Excellent! Thanks for this one! Thanks @dotnetic!

Maybe you'll convert the UIKit 3 template to Tailwind ?.

Hi @Andy. Thanks for this. I have seen it before. It was recommended to me by @Jonathan Lahijani a while back. Two reasons why I didn't select it: I needed a simple template for the demo. I am more comfortable with Tailwind compared to UIkit etc ?.

Thanks @Andy. I'll have a look at your PR.

Hi @AndZyk. You are right. Thanks for your thoughts. I'll have a talk with @Pete. Currently, Padloper has a VIP support forum. However, not everyone who is interested in the module has access to that forum. Thanks.

Hi @Malinda. Welcome to the forums and ProcessWire. We have a jobs board here, in case you need it in future: https://processwire.com/talk/forum/22-jobs/ Yes. That is to be expected. For YouTube, you have three options at least: 1. Tell CKEditor to stop stripping your iframe, as explained here: 2. Use Hanna Code. An example can be found here: There are simple Hanna Code examples but I cannot find them at the moment. 3. Use one of the available Video embed modules: https://processwire.com/search/?q=video&t=Modules You would need to be a superuser (the higher up level [highest in fact]) to be able to access ProcessWire templates. However, the files that go with the templates (template files) and styles are stored in your directory/folders where your ProcessWire installation files are stored (on your webhost / server). Access to them is usually via FTP or a CPanel-like dashboard. The template files will be under /site/templates/. The location of styles is a matter of choice for your developer but the usual locations are /site/templates/styles/ or /site/templates/css/ or similar. By head area I assume you mean the <head></head> of a template file or an auto-appended file like _main.php (/site/templates/_main.php). The JavaScript would be picked up, yes. However, the code does not (shouldn't even, I would argue) go into CKEditor. It would be stripped out anyway by CKEditor. I am not sure what you mean by code in this case as well. Usually, that code would go into your /site/templates/scripts/main.js or /site/templates/js/main.js. The main.js is usually a custom file created/amended by your developer so it could be named something else, even scripts.js. I hope this helps. It would be helpful to know the what version of ProcessWire you are using. All the best ?.

Hi @Stefanowitsch, Very quick response. There is no best practice really. ProcessWire is blocking access to form-submit.php because it is not a template file. There are different approaches to handling ajax requests, including: Creating a dedicated page (it doesn't have to be visible) and calling that Home page to handle all requests. You can then include your form-submit.php and let it deal with the response and send it back to your home template. Same page the form was called in (1-3 are similar). Using the new URL Hooks.

I realise the demo site README was not clear enough, apologies. Did you create the pages products and categories under /home? Have you enabled URL segments on the templates products and categories? Edit: I notice even your /about/ page is not working. Do you have that page?

Depends on what you guys want me to prioritise. I haven't looked at it in detail but from the expression of interest form it seems that Stripe is pretty high up the list. <?php namespace ProcessWire; $this->addHookAfter('PadloperCart::getProductPrice', null, 'customProductPrice'); function customProductPrice(HookEvent $event) { $product = $event->arguments('product'); // get the product field with the price $stock = $product->padloper_product_stock; // grab the price $price = (float) $stock->price; if (wire('user')->name ==='my_best_friend') { $price = 0.01 * $price; } $event->return = $price; } Padloper is very versatile. You can use it as a POS using the backend only; as a full ecommerce solution with a front and backend or as a headless CMS or API only shop. :-).

Cross-posting...