kongondo

Hi @marie.mdna, Sorry for the delay. Thanks for confirming. I'll test and merge sometime this week. Thanks!

Hi @marie.mdna, Nice! Thanks for the suggested fix. Did you test with uploading images to product variants? Do they save OK? That has always been the issue. Thanks.

I like NativePHP. I like Laravel. I love ProcessWire. I'd rather use ProcessWire to build desktop apps. Now it looks like I might be able to! Very early days.... https://bosonphp.com/ Hopefully it catches!

Hey @marie.mdna, Cool; glad you got this sorted! Yes; Hooking got breaking changes in Padloper version 010 which you found out about. For others reading this, please see this topic: Just curious, are you testing on a multi-lingual site? If yes, is Dutch the main language on the site? I ask because previously, bugs have been reported on such sites. For instance, with respect to creating product variants. Hopefully I fixed them all. Otherwise, please continue filing bugs if you can. Thanks!

Hi @marie.mdna, I've split your question into its own topic as the other thread is specifically for 'me requesting' help 😁. Thanks for the various tests and also the issues you have reported. I am not ignoring them. I just haven't found the time. GitHub did not inform me about them either, which delayed things further. Back on topic, @bernhard's Deepwiki mentioned here looks useful. Alternatively, if you open the module folder in an IDE like VS Code, you can simply search the whole folder for ___ i.e., 3 underscores. Old school/manual but it works. You can then open that in the 'find/search editor' in VS Code. For some reason I thought I had listed all the hookable methods in the docs; looks like I didn't. Could you please share some example code you have tried + tell us where you are calling the hooks. Maybe I have misunderstood this one. The whole idea with a custom checkout customer form is that you can create your own; Extending the one in the demo examples is not required. I think perhaps you meant to say you need hooks in order to handle inputs in your custom checkout form 😃.

Wow. Thanks! I am very ignorant about AI and tools out there (a story for another day/forum). I've never heard of Deepwiki. It does look useful, thanks! 😃. Edit: I've split @marie.mdna's question into a new topic. I think your post is relevant in both threads. I'll leave it here for now.

Hi @Claus, Thanks for reporting. I am a bit perplexed by this one. Are you on a Mac? At first, I was wondering if it's a paths (directory separator) issue. But then... this is confusing. Padloper (nor ProcessWire Commerce) does not have a module called PaymentPaypal. Which leads me to... How old are we talking? 😀

Actually this looks like Markdown to HTML. I want the inverse! I.e. $markdownFile = $someTool->convertHTMLToMD($page->render()); Edit https://github.com/thephpleague/html-to-markdown

An option... https://commonmark.thephpleague.com/

Yes, that's true. I have nothing against Markdown. I just don't like writing Markdown. It is not a pleasant editing experience. I don't mind using Markdown for short content such as READMEs. Been there, done that. The existing Padloper docs are running on VitePress 😀. The editing experience sucks, especially working with tables and images (editing). https://docs.kongondo.com/ Not to digress much, but I have done the whole NodeJS/npm dance. I have (private) repos with various variants of Padloper written in Vue, Vuetify, Nuxt, Primefaces. I ended up back at using ProcessWire with a sprinkling of htmx and Alpine JS (thanks to two buddies here in the forums). I still use Node JS, now and then. Long story short, all I want is a Markdown generator. if I can edit docs using ProcessWire or a WYSIWYG then export that to Markdown and have that trigger a CICD pointing at GitHub pages, that's the ticket for me. This scenario doesn't stop anyone who doesn't mind editing Markdown to do so. We'll meet at Markdown, so to speak 😀. The main (only?) reason to use Markdown is to make contributing easier. An additional advantage for a generating from ProcessWire pages is I would have the documentation saved in a DB as well.

Yes it does and I even enabled it on ProcessWire Commerce repository. Definitely worth considering, thanks.

Yes! This would be great! I like the idea....but... I've got Node fatigue 😁 and I really don't like writing Markdown... So what now? If only there was a way I could work comfortably in ProcessWire and export to Markdown, or better to GitHub... Yes! This is it. OK, I really don't want to use Laravel blade or Twig. Just give me plain PHP. Wait, https://www.atasasmaz.com/p/atas-php-ssg https://github.com/atas/ssg Yes! Now I can have my cake and eat it too! 😄. I'll have a play and see if I can use this in ProcessWire, maybe as a library or a module. This, I think, offers the best of several words! Living the dream! Everyone can generate their Markdown as they please! 😄 Thanks for the idea. I'll have a play. We'll also need to come up with a templating structure of some sort for the docs, to guide contributors. Thanks!

This, plus the 'curse' of ProcessWire got me thinking. I love ProcessWire. I could spin up my own BookStack using ProcessWire. And so I started, but wait... @Ivan Gretsky has a better idea, I think.

Thanks for the reminder! I have edited the first post here as well as the announcement one. I'd also noted there the issue with manual orders. Please file bugs here: https://github.com/kongondo/ProcessWireCommerce/issues Thank you.

Thanks both! I did try bookstackapp a little while back but got stuck on something. I cannot remember whether the issue was ddev or Laravel. I did not try it on my server. How's your setup? Thanks.

Padloper is dead! Long live Padloper! It is official! Padloper is now ProcessWire Commerce. ProcessWire Commerce is a free, open-source fully featured e-commerce module (plugin) for building and managing fully function online shops (stores) in ProcessWire. It is flexible, extensible, highly customisable, scalable, robust, multilingual by design and battle tested. Pro Support ProcessWire Commerce is designed to be easy to develop with and to use. For some, you might need extra reassurance that professional help will be available if you need it. Or, you might have a question about how to perform a certain thing or wish to support the project to ensure that any issues are dealt with quickly. Or you might want to sponsor a particular feature. If this is you, Pro Support and custom development can be purchased from my website. Community Support These forums. Donations If you value my work or my work helps support your work or you just want to say thanks, please consider donating. Thanks! Requests Modalities are still being worked out. Please note: I'll add features at my own pace; if and when I can (reasons for this discussed elsewhere in the forums). I'll focus on security, PRs and maintaining the project and major bug fixes. I hope community will contribute. Sponsored (pay for a feature) features: This can be by individuals or community driven. Please contact me for availability. Known Bugs ProcessWire Commerce Admin GUI is broken in the new admin theme, i.e., ProcessWire 3.0.248 (or newer). Save + Exit and similar broken on some pages at some recent ProcessWire version. Manually order creation broken (backend). Please file bug reports in the repo here - https://github.com/kongondo/ProcessWireCommerce/issues. Contributing This is a community project. All contributions are welcome! We are still working out how the 'how'. Documentation Please see this thread. Other Important Stuff Migrating from Padloper. Community help request. Tech Stack ProcessWire (PHP). Vanilla JS htmx Alpine JS Tailwind CSS MySQL Download Here you go!

ProcessWire Commerce is a free, open-source fully featured e-commerce module (plugin) for building and managing fully functional online shops (stores) in ProcessWire. It is flexible, extensible, highly customisable, scalable, robust, multilingual by design and battle tested. The current features are: Core Features Product Management: Create and manage unlimited product listings with options for unlimited variations, pricing, and descriptions. Support for 4 product types: Physical with shipping, physical without shipping, digital and services/events. Optionally track stock. Order Management: Process and manage orders, handle refunds, print invoices and communicate with customers. Frontend order placement and backend manual order creation. Shipping Options: Configure shipping methods, rates, handling and zones based on location and product type. Rates can be tiered and based on weight, price, quantity or flat. Support for 'rest of the world' shipping. Tax Management: Calculate and apply taxes automatically based on location and product type. Prices can include/exclude taxes. Tax overrides can be added to product categories (collections) and/or shipping. Analytics & Reporting: Gain insights into sales, customer behavior, and product performance. Payment Gateways: Integrate with numerous payment processors to securely accept online payments. Invoice, Stripe and PayPal included by default. Easily add your preferred gateway. Optional Features Inventory Management: Track stock levels, manage back-orders, and set up low stock notifications. Product Categories (collections). Product Tags. Product Attributes (for product variants, e.g. colour, size, etc). Product Types: 'Phones', 'Books', 'Shirts' and so on. Product Brands: Create and manage shop product brands/vendors/manufacturers. Product Properties: Further describe products based on various properties such as 'Colour', 'Grade', 'Weight', etc. Product Dimensions: For instance, 'Centimetres', 'Kilograms', 'Litres', etc. For use with Product Properties. Downloads; Digital products or files that accompany a product such as 'tickets', 'manuals', and so on. Discounts: Redeemed by customers or applied automatically at checkout. Support for four types: Fixed, Percentage, Shipping and Buy X get Y (last one is WIP). Discounts can be applied to whole order, parts of it, to select customers or countries. Customer Management: Create and manage unlimited customers. Can be created at checkout (using the API and/or hooks) or manually in the backend. Email customers directly from admin. Customers can have multiple addresses. Customer Groups: Create and manage unlimited customer groups Add customers to as many customer groups as needed. Customer groups can be targeted for marketing, promotions, etc. Legal Pages: Create and manage legal pages such as 'Shipping Policy', etc. Gift Cards: WIP. Move some pages from /admin/shop/ to a parent in the home tree. With your help, we can add more features 😀!

Thread to discuss the state, suggestions, contributions, etc. regarding documentation for ProcessWire Commerce. The minimal Padloper documentation found here can be a starting point. I'll try my best to write the documentation. I need your help though. Please note the caveats in the 'open-sourcing Padloper' thread. I.e., I'll do what I can when I can. Your help is vey much appreciated. I'll prioritise assisting documentation contributors, to help point them in the right direction. Documentation should cover: Frontend documentation - for frontend developers: End-to-end how to work with ProcessWire Commerce in the frontend to build a shop. Backend documentation - for shop editors. How to use the GUI to configure, build, run and manage a shop. API documentation - for documenting how ProcessWire Commerce is built, developing for it and contributing. Thank you! You contribution is much appreciated!

NOTE: Here and elsewhere referencing ProcessWire Commerce, Padloper refers to Padloper 2. Padloper 1 was retired 3 years ago. -------------- New Site Install ProcessWire Commerce. The current (outdated and incomplete!) Padloper docs are still helpful. Note though that configuring ProcessWire Commerce is accessed via /admin/shop/configure-pwcommerce/. For template files and hooks, please note the following: Changes Template Files All instances of $padloper should be replaced by $pwcommerce. For instance $padloper->getCart() should become $pwcommerce->getCart(). All instances of 'pad_' should be replaced by 'pwcommerce_'. For instance 'pad_price_total' should become 'pwcommerce_price_total'. Hooks Your hooks, e.g. in ready.php should be renamed as follows: All instances of Padloper::someHookedMethod should become PwCommerce::someHookedMethod. Please note the spelling is case-sensitive. Existing Site DO NOT UNINSTALL Padloper! DO NOT INSTALL ProcessWire Commerce! Download and install the Padloper to ProcessWire Commerce migration tool from this repo. Please READ all the instructions! Template Files: As above. Hooks: As above. Any issues please let us know below. Include info about: ProcessWire version (please note ProcessWire Commerce/Padloper's admin GUI is broken in new admin theme, i.e., ProcessWire 3.0.248 (or newer). Padloper version. Site language(s). PHP version. MySQL version. For issues with the migration tool itself, please raise an issue in the project repo. Include the above environment information please. Whilst I have thoroughly tested the migration tool (on a multilingual site), usage of the migration tool is at your own risk!

ProcessWire Commerce will be here later today. As mentioned in earlier discussions, my hope is that this will very much become a community project. ProcessWire Commerce is a mature project that powers hundreds of shops, big and small. There still some work needed to make it better. This is where you can chime in, to the extent you can. Please note: I don't have it all figured out yet. With your help, we can figure it out together, including the contribution process. Below are the things that currently need to be worked on. Documentation: Frontend documentation - for frontend developers: End-to-end how to work with ProcessWire Commerce in the frontend to build a shop. Backend documentation - for shop editors. How to use the GUI to configure, build, run and manage a shop. API documentation - for documenting how ProcessWire Commerce is built, developing for it and contributing. Still considering if/how to how to host documentation. Suggestions welcome. Fix Bugs Identify, report and suggest bug fixes. Please file bug reports in the repo here - https://github.com/kongondo/ProcessWireCommerce/issues. Fork the project, fix bugs and submit PRs. Tutorials Help write ProcessWire Commerce tutorials for different audiences. Help create demos. Ecosystem Help grow the project. Star it on GitHub. Create add-ons. Build migration tools. Create a logo for ProcessWire Commerce. Help write unit tests (???) Site Profiles Help develop an official, multi-lingual, modern site profile/theme to be used to showcase ProcessWire Commerce. Contribute site profiles or themes.

Version 1 is here! https://github.com/orgs/NativePHP/discussions/547 Mobile apps capability in the works: Not surprised; given that Caleb Porzio also wrote Alpine.JS 😊.

I am considering open-sourcing Media Manager (and my other commercial modules). Please read and hopefully participate in the discussion in the Beer Garden (away from Google's prying eyes). Although the topic referred to is titled 'Padloper', the issues addressed equally apply to Media Manager. Thanks.

I am considering open-sourcing Padloper (and my other commercial modules). Please read and hopefully participate in the discussion in the Beer Garden (away from Google's prying eyes). Thanks.

Now there is 😀.

LyriChord is a Fieldtype, Inputfield and Markup module that lets you input a song's lyrics and optionally chords. You can input these manually or by importing from your clipboard. Inspired by the challenge posed by @oscarale in this thread: The markup module is optional. You can output your song the way you wish. For the HTML I prefer to use tables as they make it easier for things to be aligned properly without having to play around much with the CSS. Planned Features IMPORT XML HTML JSON CSV OCR PDF Other? NOTATION Staff? Guitar Tabs Solfa BOOKS Song books Pagination? EXPORT OTHER Support for syllables Transpose ??? Project + Download TBD soon. I need to cleanup a few things Quick(-ish) Demo