MrSnoozles

Agreed. I'm missing headless too. Because it's a buzzword that's trending and PW for sure can be used headlessly. We used the really excellent GraphQL plugin from @dadish to use PW as an API for an entire mobile app.

Hi @Dharma, I haven't done this myself yet, but I would look into hooking PagesRequest::getPage . Also check how LanguageSupportPageNames.module is hooking into that method, and get an idea of what it's doing to figure out how to overwrite the behavior.

@diogoDo you have anything planned for these bigger changes already? I have a vision in my head how the ProcessWire backend could look more modern and at the same time be faster to use and cover more use cases, especially when ProcessWire is used for applications rather than websites. If you're planning on working on more profound changes I'd love to discuss some ideas.

ProcessWire has a lot of great features that make it better than many competitors. I'm sure there's much more, but here's a start: Build anything Powerful field types and unlimited templates allow you to build anything. Simple yet powerful API ProcessWire gives you the tools to build what you want, easily and in record time. Headless or hybrid Create a REST or GraphQL API or a traditional website. Any template engine Twig, Blade, Latte or plain PHP? We've got you covered. Multi language Reaching an audience in multiple languages is not an afterthought but built right into the core. Powerful permissions Let users see only what they need to see, with a fine grained permission system. Easily Extensible Modules can change or extend almost any aspect of the system. Long-term backwards compatible We know you hate breaking changes. So do we.

@ryanThe Custom Field module has changed the way I work with ProcessWire more than any other module in the past 10 years. The possibilities are insane. No more "being scared" of adding a new field because it will clutter the admin UI and might have an impact on performance. If I want to store more information about something I can now just do it. And everything is immediately version controlled - no need to create fields or run migrations when going live. It's incredible!! Is there a chance the module will be developed further anytime soon? I so wish it would support the file and image types.

Have a nice weekend, Ryan. Any chance of getting a sneak peek at the redesign you teased at the end of last year?

Updated the post to be clear it's an example and varies depending on which modules are used.

It looks like you need to make $map available in your Latte file first. Then, as Bernhad has said, you could write in your Latte file {$map->render($page, 'YOUR MARKER FIELD')} With https://processwire.com/modules/template-engine-latte/ you would write something like the following in your PHP template file (or ready.php): $view->set('map', $map); It might vary depending on which modules you use exactly in your project.

Okay cool. I thought with JSON functionality they were starting to diverge.

@ryan The module sounds very cool. Does it support MariaDB too or only MySQL? A storage_name option could be useful to be able to rename the field in the api, but keep the values in the database.

Clickbait title aside, I recently found a cool new feature in PHP 8.1 and wanted to share it with you, in case you didn't know this either. Starting with PHP 8.1 you can write $this->method(...) (yes, that's the actual syntax, not a placeholder) to reference a method. I find this super convenient, especially for defining hooks. Plus the IDE can refactor this much better than the traditional [$this, 'method'] callback. <?php class MyModule { public function init() { $this->addHookAfter('ProcessPageView::finished', $this->doSomething(...)); } private function doSomething(HookEvent $event) { // TODO: something } }

This is super useful, as is Mystique. Will it support searching and more complex fields, like repeaters? Agree, this is very useful.

Again, regarding a more modern administration: I like how the Silverstripe backend works, both how the page tree is presented, as well how the page edit screen looks. I also like that expanding the tree works in a (imo) more standard way (meaning a click will edit the page, to expand it there's an arrow). I think we could get some inspiration from there. You can try the demo here, no need to sign up: https://demo.silverstripe.org/admin/

Agree with that. I really like the Craft 5 backend, from your screenshot at least. Would be nice to have a page tree in the sidebar though for quick navigation when it's used as a cms. When used as a custom app, what we usually want to do, is to hide everything that says "page" and provide custom views to the user. E.g. we want sections that show "events" or "skyscrapers" in a list/table, the way users know it from other apps. I think what was meant is to drop utf8 and myisam or at least do not offer those options in the installer. If somone knows what they are doing and they offer advantages it's possible to change it in the database. My guess would be that the majority of people do not know what's the difference and want utf8mb4+innodb. I didn't know back then and was wondering why emojis were not shown on my site. Took a while to find out that I need utf8mb4 instead of utf8. Any particular reason why you wouldn't like it?

I'm so happy it comes as a very good module instead of being integrated by default. We're using PW to build internal tools as well, where SEO settings do not make sense. Love this list, couldn't have formulated it better ♥ As for composer installation: This does not mean that an installation of ProcessWire has to get more technical. It could still be downloaded as a zip file and extracted. The only differences would be that instead of site&wire directories, you would have site&vendor directories. Also it would be possible to install a new ProcessWire instance directly from composer, as opposed to going to the website, finding the download page and downloading & extracting the zip archive. And it would appear a bit more professional, imo. I just see advantages here.