Jump to content

kongondo

PW-Moderators
  • Posts

    7,379
  • Joined

  • Last visited

  • Days Won

    139

Everything posted by kongondo

  1. Hi @gebeer, I cannot remember why I don't support it. I think it is just an oversight on my part. I will add this in the future. I used to have one in the docs but I cannot find that page now. I must have deleted it by mistake! Sorry. Better to add 'FieldtypeCheckbox' in the array in 'MediaManagerUtilities.php' around line #1814 (in the method allowedFieldTypes()). This is where I'll add it in a future release.
  2. Yes. The folder /site/modules/Padloper holds all Padloper modules. It is the parent folder for all Padloper modules including a module called Padloper ๐Ÿ™‚ as. you have undoubtedly found out.
  3. Hey @joe_g, I've just tested on my demo site and it works fine. I don't think Stripe would authorise a payment below $0.50 US anyway (CHF 0.10 is $0.11 US). Those have to do with Stripe itself. They inject the JS to build the Web Element. I have never been able out if I am able to 'mute' them. I'll see what I can do about this.
  4. Great catch! Will fix for next release, thanks.
  5. Exactly! It is a schema. Yes, you are right. Good idea. I had the same thought only yesterday ๐Ÿ™‚. Just to be clear though, that markup is just a demo and not a requirement as developers can use any templating and markup strategy that they want.
  6. No worries. Yeah, I made the video to demo possibilities. I should have been clearer that those addons were just demos and not official Padloper addons.
  7. Hi @joe_g, Yes, inventory has to be tracked for stock to decrease. This happens as soon as a payment is confirmed and checkout completes. You cannot delete a thread unless you are a moderator. But let's keep this thread in case it helps the next person ๐Ÿ˜„.
  8. Flutter has been busy ๐Ÿ™‚. Announcing Flutter 3.3 at Flutter Vikings Flutter Casual Games Toolkit (YT Quick Start Video) Introducing the Flutter News Toolkit Wonderous: Explore the World with Flutter: A reference app that shows how to develop tailored UI using Flutter (source code on GitHub) Announcing Flutter Forward: Register for the next Flutter event, streaming live from Nairobi, Kenya (25 January 2023)
  9. Hi @joe_g, The template file checkout.php does not control the form layout or inputs. For that, you need to use the template partial checkout-form-customer-details-html.php. Here's the one for demo-1 and here is one for demo-5. This is the inbuilt Padloper order customer form. I don't understand how and why this would affect your checkout process. Please explain. Thanks. Apologies that the documentation is still very sketchy!
  10. Hello @joe_g, Apologies. I updated demo-1 checkout form template file earlier but forgot to also update the template partial for customer details form. I have now fixed this. I will also need to fix those for demos 2 - 4 (inclusive). For info, please see the docs for allowed form inputs. Your 'country' <select> needs to have name='shippingAddressCountry'.
  11. Hello @joe_g, You need to create your own addons (although the inbuilt Payment Gateways - Stripe, PayPal and Invoice, are internal/core addons). Yes. I'll issue a fix so that you get a meaningful warning/error message if you don't have that folder created.
  12. Hi @joe_g, Per our discussion, your issue is identical to the one reported in this thread: Specifically, the deprecated form option 'equivalent_padloper_input_name'. I will update demo-1 to reflect this.
  13. Hi @joe_g, You need to create a shipping zone, edit it and add at least one country to it :-). In this case, Netherlands. Screenshots Edit shipping zone to add country(ies) to it Countries in each shipping zone are shown in the shipping zones dashboard More info here in the docs.
  14. Hi @alexm. Thanks for letting me know. I might have to speak to Ryan about this one as I have no clue where to look. I'll focus on it over the hols. Cheers.
  15. Great catch! I need to update the demo with this info, at least the description bit, if I cannot find a better hook. Thanks!
  16. Hi @joe_g. Sorry about this. Could you please confirm that Netherlands is also added to a shipping zone? The error tells me that possibly a shipping country was not found. Irrespective, I need better error handling.
  17. ๐Ÿ˜„ exactly. I acknowledge that the instructions are not great for this demo in particular! I'll work on this. Glad you got it sorted.
  18. Hi @joe_g, Thanks for the purchase! Thanks for bringing these to my attention. I have been testing with PHP 8.1. I'll test with 8.2 to fix these (and possibly other) bugs. Do you mean ProcessWire or Padloper? If the latter, what 'pages' view is this? Also noting here that I have seen your other support questions. I'll get to them as soon as possible. Many thanks.
  19. Glad you got it sorted! ๐Ÿ˜„. By the way, I know there are some CSS issues that need fixing. Something changed in ProcessWire that is messing up the page selections. I have accepted a PR for this in the Project in GitHUb and will be merging with dev 0.28 this week now that you have confirmed 0.28 works. Thanks.
  20. Hi @GEN-, Thanks for clarifying. Did you see my response above about this with respect to the option default_title?
  21. I don't understand this. What title are you referring to? The titles of menus that are displayed in the dashboard that shows all Menu Builder menus in the backend? What is the wrong language in this case? A screenshot with English explanations would help.
  22. Hi @entschleunigung. Sorry for a very late reply! I missed your post. I have no idea what's happening. Are you able to please try with a different ProcessWire version? I don't recall anyone ever reporting a similar issue.
  23. Good idea. I'll and this on my todo list. I have no idea. I'll test here and let you know, thanks.
  24. Hi @gs-df Coupons/Vouchers are not currently supported so there are no files to look at ๐Ÿ˜€. Some quick thoughts... I see three main components: Creating coupons Managing them (editing, etc) Using the coupons in the frontend and expiring them in the backend. Creating Coupons There's are a number of approaches. a. Coupons as a special type of product Add a custom text field to products template. Create coupons as products. Hide these 'special products' from the frontend. Advantages Easy to create. Not much coding needed; you can use the Padloper and ProcessWire APIs. Disadvantages Not intuitive; can confuse editors. Lots of unused fields relevant to product but not to coupons. Extra code to hide coupons from being displayed in the frontend as products. b. Coupons as dedicated ProcessWire pages Let coupons be dedicated ProcessWire pages. Could use own custom dedicated template (i.e. non-Padloper template). Can either hide these pages under admin or have them live under Padloper main parent page or have them as usual pages. Add custom fields to hold coupon details such as valid date(s), expiry, usage, number, etc. Alternatively, create a custom Fieldtype for coupons. Advantages Straightforward and easy to manage as separate pages. Not much coding needed; you can use the ProcessWire APIs. Disadvantages Extra code to hide manage coupons c. Coupons as items in a custom database table Create a custom database table dedicated to holding coupons data. Use $database to CRUD coupons. Advantages Straightforward and relatively easy to manage as separate records. Scalable. Disadvantages Knowledge of working with custom tables needed. Extra code for CRUD. Managing Coupons Depending on your chosen route above, you could directly edit the coupons as ProcessWire pages, or create a Process Module (not great as will be outside the Padloper 'environment') or use the Padloper addons and addons API. The latter is my preferred method as it gives you near unlimited ways to manage your coupons in a dashboard. You could use this dashboard to manually send coupons to customers. You could also automate the process. Using Coupons This is the easy bit. You will need to use a custom checkout form to add fields you need to capture details about the coupon details that the customer has provided. You can then use a hook(s) to process coupon details entered by customer (e.g. validate, etc). See demo 2 and demo 3 on how to use and hook into the order checkout to process custom form details. Hope this helps.
ร—
ร—
  • Create New...