kongondo

Hi @gebeer,

10 hours ago, gebeer said:

Guess this matter is about supported field types for custom columns. Fieldtype Checkbox seems not to be supported. It is supported in normal listers, though. Would it be possible to add support?

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. 

10 hours ago, gebeer said:

And is there a list of the supported field types?

I used to have one in the docs but I cannot find that page now. I must have deleted it by mistake! Sorry. 

10 hours ago, gebeer said:

EDIT: If I add the field id manually to the MM settings JSON, the column appears in the image lister, but not in the Settings ASM Select

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.

10 hours ago, joe_g said:

So should all the padloper module stuff be under "Padloper/" actually?

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.

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).

7 hours ago, joe_g said:

Some cookie issues in the console:

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.

8 hours ago, joe_g said:

but I would imagine it would fail more gracefully if this was the reason?

I'll see what I can do about this.

8 hours ago, joe_g said:

Hi, typo - I think?

/site/modules/Padloper/templates/invoice line 74

PadLoper -> Padloper (lowercase L)

J

Great catch! Will fix for next release, thanks.

9 hours ago, joe_g said:

Oh I see, thanks. So the $customFormFields in checkout.php is a 'schema' to define the fields, then I also need to change the markup myself.

Exactly! It is a schema. 

9 hours ago, joe_g said:

Maybe it's good to mention the markup file here as well, it wasn't clear to me that it existed: https://docs.kongondo.com/start/checkout/custom-customer-form.html#supported-form-inputs

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.

10 hours ago, joe_g said:

I found this video, and in it there is a list of addons that I couldn't find anywhere, so that's why I asked:

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.

Hi @joe_g,

7 hours ago, joe_g said:

Oh right, it says pretty clear "Does not track inventory", enabling that and it work ofc. How do I delete this thread 🙂 ?

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 😄.

@FelipeReis64. How is this related to ProcessWire?

Flutter has been busy 🙂.

1. Announcing Flutter 3.3 at Flutter Vikings
2. Flutter Casual Games Toolkit (YT Quick Start Video)
3. Introducing the Flutter News Toolkit
4. Wonderous: Explore the World with Flutter: A reference app that shows how to develop tailored UI using Flutter (source code on GitHub)
5. Announcing Flutter Forward: Register for the next Flutter event, streaming live from Nairobi, Kenya (25 January 2023)

Hi @joe_g,

6 hours ago, joe_g said:

I'm trying to change the custom checkout form but it's not using the code for the custom form.

No matter if I use the latest demo-1 version (with corrected variable names):

https://github.com/kongondo/Padloper2Starter/blob/demo-1/templates/checkout.php

or the minimal version:

https://github.com/kongondo/Padloper2Starter/blob/demo-5/templates/checkout.php

it looks the same

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.

6 hours ago, joe_g said:

Also if i set $isCustomForm to 'false' i get a different, more basic, layout:

This is the inbuilt Padloper order customer form.

6 hours ago, joe_g said:

However if I change $isShowSectionBackArrow to 'false' it does hide the arrow, so my checkout.php is processed.

I don't understand how and why this would affect your checkout process. Please explain.

Thanks.

Apologies that the documentation is still very sketchy!

Hello @joe_g,

5 hours ago, joe_g said:

Clicking "proceed to confirmation" in the checkout reloads the page instead of going further. Debugging shows that "$response->errors" is not empty, it contains:

Array ( [0] => shippingAddressCountry )

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'. 

Hello @joe_g,

5 hours ago, joe_g said:

The addons doesn't seem to be included in the padloper 2 download. Where can I find them?

You need to create your own addons (although the inbuilt Payment Gateways - Stripe, PayPal and Invoice, are internal/core addons).

5 hours ago, joe_g said:

If I instead create the folder /templates/padloper/addons/ I get

Yes. I'll issue a fix so that you get a meaningful warning/error message if you don't have that folder created.

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.

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.

6 hours ago, alexm said:

Hey @kongondo just to let ya know there is still some issue with adding/saving products and pages in Padloper after PW v3.0.203. I've just tried updating to 3.0.208 and that little bug is there. 👍🏼

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.

4 hours ago, alexm said:

Ok. So as the comments in the hook example explain, there needs to be logic added to identify the logged in user. I'm thinking the best way to identify the customer details is to add a new role for administrators of the shop and then use a condition to check if a user has said role. If they do, don't auto-populate, as this hook overrides more PadloperProcessOrder::getOrderCustomer and this is used for more than the checkout customer details form.

Great catch! I need to update the demo with this info, at least the description bit, if I cannot find a better hook. Thanks!

2 hours ago, joe_g said:

Hi hello,

After filling in the final checkout form, selecting a payment method and clicking "proceed to confirmation" i get this error:

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.

3 hours ago, joe_g said:

Aha, i get it now - i should make my own templates called 'categories' and 'products' 🙂

😄 exactly. I acknowledge that the instructions are not great for this demo in particular! I'll work on this. Glad you got it sorted.

9 hours ago, joe_g said:

Hi there,

just installed padloper 2,

Hi @joe_g,

Thanks for the purchase!

9 hours ago, joe_g said:

so i upgraded to what is now the latest (8.2) but I get these errors:

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.

8 hours ago, joe_g said:

With 8.2 the 'pages' view doesn't work either. You get 'unkown error, please try later'.

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.

3 minutes ago, GEN- said:

Thanks Kogondo, I didn't see this comment. I just saw the one from November 20th talking about the version 0.2.8 on the dev branch. I just tried getMenuItems(1705, 1,['default_title' => 1]) and it works.

Thanks again

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.

11 minutes ago, GEN- said:

Hi kogondo, I am a colleague of Spiria. In this exemple, the default language is French. if the profile of the user who modify the menu is english, the url of the item that will be displayed is correct, but not the title. 

 

Hi @GEN-,

Thanks for clarifying. Did you see my response above about this with respect to the option default_title?

On 11/23/2022 at 7:57 PM, Spiria said:

but the title is displayed in the wrong language as before

I don't understand this. 

1. 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?
2. What is the wrong language in this case?
3. A screenshot with English explanations would help.

On 11/23/2022 at 4:02 PM, entschleunigung said:

Hi,

I once bought a license years ago, now I wanted to install MM again.
I have version 0.12 B, installed with PW 3.0.200 and Jquery File Upload 0.0.9, at first glance everything looks good.

I can upload images in the admin, these also appear, but now the curious, as soon as I click on an image on Edit the image is deleted.

In the logs also appears "rmdir: Unable to rmdir: /site/assets/cache/FileCompiler/".

All this is installed on a local environment with DDEV and PHP 7.4 ...

Any idea what could be the reason for this?

Greetings

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.

On 11/29/2022 at 10:52 AM, gebeer said:

@kongondo Media Manager fields always return a MediaManagerArray, even if Maximum Media Allowed is set to 1. This is not bad at all but it would be great if the logic would follow PageFiles or Page Reference field conventions. There we can choose whether to return an Array or a single object.
So for Media Manager fields it would be nice to have that option, too. Or a default behaviour where fields with max allowed 1 return a single MediaManager object because returning an array doesn't really make sense in that context.

Good idea. I'll and this on my todo list.

On 11/30/2022 at 11:56 AM, gebeer said:

@kongondoIn my install (PW 3.0.200), Media Manager pages for images and documents get saved under Admin->Media Manager->Media Manager:Audio instead of Media Manager:Image and Media Manager:Document. They have the correct template media-manager-image and media-manager-document, but are under the wrong parent.

What could be the reason?

I have no idea. I'll test here and let you know, thanks.

Hi @gs-df

5 hours ago, gs-df said:

Which files i have to look into for this feature?

Coupons/Vouchers are not currently supported so there are no files to look at 😀.

5 hours ago, gs-df said:

have u any tips for adding the feature voucher/coupon?

Some quick thoughts...

I see three main components:

1. Creating coupons
2. Managing them (editing, etc)
3. 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.