kongondo

Thanks. I'll have a look. I agree. I checked already, almost 2 months ago ?. It's definitely the frontrunner for inspiration. Yep, keeping this in mind, thanks.

Interesting read, thanks. Related discussion on hacker news. See the bit about: OT: Yesterday, for whatever reason, YouTube was really slow on a device I was using so I tried Edge. OMG, it's true, Edge is way faster than Chrome! :-).

This is now going to happen as part of Padloper itself! :-). Cross-referencing with the relevant thread. https://processwire.com/talk/topic/19912-future-of-padloper-new-project-lead-announcement/

I should have been clearer ?. Padloper name is not changing. The module name will remain as Padloper. The domain where Padloper will be hosted will change ?. Padloper will eventually be hosted at processwireshop.pw to join other modules in that location. Traffic to padloper.pw will eventually redirect to processwireshop.pw. Eventually, the domain padloper.pw may be parked or retired; there are no immediate plans for the domain. For now, it remains active, albeit with the said changes in traffic/hosting.

Alternatively, depending on what your class does and when you need it to be called as well as the 'template approach' you're using, you could put the whole class in /site/templates/_func.php (_func.php) or in a custom file, e.g. /site/templates/_my_class_file.php. Then, in _init.php include the file (/site/templates/_init.php). Or, if you need it earlier (after current page has been determined but before it is rendered), include it in /site/ready.php or if needed even earlier (e.g to attach hooks), in /site/init.php. Follow the links for more info (to site-default). Using this approach, your ready.php and init.php remain a bit cleaner ?.

Thanks @bernhard! I've noticed you've been building some awesome modules lately ?. Unfortunately I've not had the time to take them for a spin yet. I'll keep this suggestion in mind. Cheers.

Just cross-posting an official announcement regarding project lead changes to Padloper.

Hi all, I have posted this in the VIP support forum of Padloper as well. Some of you do not have access to that board so posting here as well. Hopefully it doesn't count as spamming?! In June 2018, Antti announced that he was looking for a new product owner for Padloper. Sometime after, I had a fruitful discussion with him about my vision for the project if I was to take over. We agreed that commitment, motivation and a concrete plan were all important ingredients for the continued success of Padloper. I would like to officially announce that I am now the product owner and lead developer of Padloper. For those who may not know, I am the author and maintainer of several ProcessWire modules, both free and commercial. I am also a moderator in the ProcessWire forums. I would like to share with you a number of things regarding what’s going to happen next. This will be a long read. First, I would like to thank Antti for developing a great product. A lot of man-hours, dedication, passion and love has gone into making Padloper what it is today. Secondly, I would like to thank all users of Padloper. A great product is nothing without active users utilising it, putting it to the test, reporting bugs (even offering possible solutions) and proposing new features. So, thank you for helping make Padloper great! Support Thousands of hours have gone into developing Padloper. Although the code is well-written and easy to follow, Padloper is a big application with many moving parts. As such, it will take some time before I can fully grasp its inner workings. To make this transition as smooth as possible, Antti will help me with support for Padloper for some time. Currently, Padloper has a dedicated support forum. This is an arrangement between Ryan and Antti. The support forum works great as it allows the opening of multiple support threads to cover different issues. I have yet to speak to Ryan whether this arrangement can continue. However, given that I have other pro modules that I support in the open forums, it is unlikely that I will be requesting Ryan to let Padloper’s dedicated forum carry forth. A dedicated forum for one of my pro modules and open forums for my other pro modules will lead to confusion and questions from users of those other modules. Hence, Padloper support in the forums will move to the open forums. The disadvantage here is obviously the fact that support will be offered in one single (and maybe massive) support thread. To get around a ‘single thread support forum’, I am thinking of developing a simple online support queue system for all my modules. Meanwhile, support will continue in a new single thread and via email. Roadmap This list is neither exhaustive nor cast in stone. Its aim is to give an overview of my plans for Padloper. · Padloper 2 – a new major release · New backend for Padloper · Optional pro frontend module for Padloper · Documentation · New payment modules Let’s talk a bit about this list. Padloper 2 Release Padloper 2 will be a major release that incorporates a new, central backend shop for Padloper. This will be a new process module that pulls from the existing parts of Padloper (data models, etc) into one interface (more on this below). This version will also be extensible in the frontend, allowing for the plugging in of a new, optional, commercial frontend shop (full featured shop profile). Padloper 2 will not support the current ‘any page can be a product’ paradigm. Technically, products will still be pages. However, all products will utilise the same Padloper template. These will be invisible to the shop users themselves (e.g., hidden in admin tree). Only superusers will have full control of the Padloper system stuff. Support The current Padloper will continue to be supported until the new Padloper 2 is released. New features will be included in Padloper 2 only. Once Padloper 2 is released, legacy Padloper will only receive security fixes. All other support will cease. Upgrade There will be no upgrade path from the current Padloper to Padloper 2. Although their underlying architecture is the same, making sure that everything works in different setups and environments will be time consuming. However, for those who really need to migrate, if time allows and for an agreed fee, I could develop a custom script for the migration. Backend A new backend interface will be the major visual difference between the existing Padloper and Padloper 2. It goes beyond visual differences though. The new backend will be the single gateway for managing all shop-related features, both current and new ones. The backend will unify and include: · Easily add shop products. · Ability to add as little or as many custom fields to products as required (title, SKU, price, discount field, image/photo, description, categories, tags, etc). · Discounts manager (including auto start/expire discount codes). · Customers manager. · Invoices manager. · Taxes management. · Payment gateways manager. · Improved digital products management. · Stock management. · Manual order creation. · Graphical sales report. · Customer support. · Access-controlled shop editors/staff. · Dashboard for shop metrics. · Shop settings. · Product variations. · Import/export products as CSV or JSON. · Products search/filter. · Etc. Users will be able to turn off backend features that they do not need. This will enable a more streamlined experience for users. I plan to release Padloper 2 within 4 - 6 months, hopefully sooner. This is a major undertaking, hence the timescale. Please note that the first release of Padloper 2 will not include all of the above planned features. The idea is to build incrementally, adding new features in minor updates, focusing on stability, usability and security. Frontend Past requests have included the development of a full featured frontend shop. This is planned for Padloper 2. However, this will be an optional pro module priced separately from Padloper itself. The ability to build own frontend shops using Padloper API will still continue. For those who want a plug-n-play solution, this frontend shop will come in handy. The frontend shop profile will feature an ajax-powered shopping cart and a customisable ready-to-go theme. Pricing Model There are no plans to change the current prices of the 3 Padloper licences (Single, Developer and Agency). However, in order to continue to provide Padloper as a stable product with great features, it is also important that it remains a competitive and financially sustainable project. In order for this to happen and to also bring Padloper in line with my existing pro modules, the pricing model itself has to change. Starting from Padloper 2, the pricing model will shift to an ‘annual subscription’ model rather than the current ‘lifetime licence model’. I am fully aware that there are different opinions for and against annual subscriptions. However, I believe that this model is the most equitable approach that suits both the developer and the clients. The annual subscription will allow users (licence holders) to get 12 months of free VIP support for Padloper as well as future updates available within that time period. After the 12 months, users will be able to renew (online) their subscription at a discounted cost (worked as a fraction of the full purchase price) for a further 12 months (perpetually). Users will be able to continue to use Padloper for life even if they don’t renew their subscriptions. Upgrading current licences to Padloper 2 will be a paid upgrade. Current users of Padloper will get an attractive discount. This will be a time-limited offer (maybe a couple of months) that will start with the release of Padloper 2. New customers will pay the full price for Padloper 2. I hope the planned features are reason enough for you to consider upgrading to Padloper 2. Payment Modules I will be taking over as the maintainer and lead developer of the existing payment gateways (Payment base class, PayPal and Stripe). New payment modules are also planned. Payment modules will continue to be free. However, only ProcessWire 3+ support will be provided going forward. Padloper Domain and Future Downloads I have also taken charge of the Padloper domain. Within the next 12 months, purchase and download of Padloper will shift to processwireshop.pw. Please note that this is not the official shop for ProcessWire! It just bears a name that reflects its product offerings ?. Eventually, traffic to padloper.pw will redirect to processwireshop.pw. Feedback I would love to hear your thoughts about the upcoming changes and any feature requests you might have for Padloper 2. Whilst I cannot guarantee that any request will be implemented, I can promise that I will thoughtfully consider all feedback. Thanks for reading and thank you for supporting Padloper! kongondo

Glad you are finding it useful. Currently, you can't. You can file it as a feature request though. Please file as an issue here. Edit: Alternatively, you can do this easily yourself like so: // get the categories page. $categories = $pages->get('/blog/categories/'); $out = ''; // @note: optionally limit these if there's lots of posts >>> children('limit=x') foreach ($categories->children as $category) { $categoryPostsCount = $pages->count("template=blog-post, blog_categories=$category, sort=-blog_date"); // append category title and link $out .= "<h3><a href='$category->url'>$category->title</a></h3>"; $out .= "<span>$categoryPostsCount</span>"; } echo $out; limit controls number of posts returned. A value of zero means do not apply any limit, hence returns all available posts ?.

Very good resource here: Refactoring with Visual Studio Code

Update: Menu Builder 0.2.4 Changelog Fixed a bug where default_class was not getting applied to menu items in getMenuItems() context. Fixed bugs where last_class was not getting applied correctly/at all to some menu items. In modules directory.

I've just read this quickly. Maybe for now your options are: Sanitise separately: i..e, do the email itself bit then append your incoming+account/ Use your own regex to sanitise the email (e.g. using $string = $sanitizer->match(string $value, string $regex); Docs are here) Sanitise as you are doing then re-insert your / afterwards using string replace or similar. Like I said, I read this quickly, so, I might be missing the point ?.

?

So problem solved?

Hi @DarsVaeda, I am totally clueless about this as I've never used ProCache. Could you disable ProCache and see if we can rule out the upgrade to PW 3.0.98 as the cause? Any errors? (use Tracy Debugger)

No need to be ?. Although this feature has been, relatively, around for a while, it's not easy keeping up with all the new stuff. That selectors page has been updated several times with new stuff so it's good to have a fresh look at it.

http://processwire.com/api/selectors/#or-groups

Been there, done that. Btw, just had a quick look and wondering if there's any reason you are not sanitizing values in wakeupValue() and sleepValue(), unless you are doing it in some other place?

Get ready for a face palm ? On line # 145 public function __processInput(WireInputData $input) { the method processInput() is missing one underscore at the beginning and should be public function ___processInput(WireInputData $input) {

Great catch. Existing modules better watch out then.

That's crazy! Wild guess: does giving them custom names or IDs change anything?

So potentially affecting any (process?) module that renders two button inputfields in a single form?

Hi @psy. Please request @apeisa to give you access. He has the 'keys' :-).

...from the link provided above ?. So, yes, it is like NB Navigator. The advantage is that Visual Studio Code is our editor of choice for various reasons ? (now, I hope this does not lead to a NB vs VSC debate; that really is not the purpose of this thread).

Yes, you are right, my apologies! I forgot about that one ?