Ivan Gretsky

I assume you want those other RM types that should not be editable by the user with the given role still to be shown in admin, but with all their fields being disabled. The best way to achieve this is via hooks. Look here or search for similar topics for inspiration. Check RestrictRepeaterMatrix's source code for another example. You need to get the InputfieldRepeaterMatrix field at some point (maybe after the renderReadyHook method), foreach through the blocks and change their fields' output based on your conditions. Sorry for no ready-to-copy-and-paste code))

I remember that there were some attempts to create courses on PW, but none of them really stuck in my memory. I think it is better to make one's way through tutorials and read through the docs. There are some videos that can be useful. These come to mind: https://www.youtube.com/watch?v=IHqnLQy9R1A - a really dated walkthrough I have once started with; everything looks different but the essence is the same) https://www.youtube.com/playlist?list=PLOrdUWNK38ibz8U_5Vq4zSPZfvFKzUuiT - a comparaison to WP

Reading through the commits log is like never before. I guess we are going to have a lot of cool stuff we were waiting for happening soon.

Cool! Why a zip file and not a repo?

Good day! I have a module that sets a url hook. But then I have code in site/ready.php that stops page rendering process under certain conditions based on a page being viewed. So I need to modify that condition to include all url/path hooks. How do I do it? I thought of setting a custom $config variable. Or checking for $config->requestPath(). But maybe there is something universal?

@maximus Seeing the speed with which you produce new cool modules just maybe you could come up with a custom theme css pretty quickly: - https://forum.nette.org/cs/31690-dark-mode-pro-tracy-css (translate from Czech) - https://github.com/nette/tracy/blob/ab7b1d19c0de130bed6de5b30c9ad7884131b465/src/Tracy/Debugger.php#L107-L111 It is already possible to change the debugger output to dark natively like this Debugger::$dumpTheme = 'dark'; (https://tracy.nette.org/en/dumper), but that is already by default, as I understand.

I have read this a couple of times. But as I am not as fluent in AI dev I couldn't quite grasp the whole workflow idea. So let me explain as I understood it and make my points. I think most devs develop in either IDE like VS Code with an AI extension, Zed and such or in CLI with Claude Code, OpenCode etc. They want their agents to be able to test certain url and see if there are any errors or warnings. I guess it is already possible by telling agents where the Tracy logs are and how to read them. AI has or could easily gain access to those anyway. An MCP could be intermediary here but does it help with anything? Another way would be to use the newly introduces CLI modules that could query an URL and return it along with debug info from Tracy. Just maybe AI agents can now debug in the browser, but that seems like a too complicated scenario. Am I misunderstanding something?

A lot of things changed in the world. I do not quite like many of them... But this what is happening here right now with ProcessWire is just amazing! Ryan finally found himself a companion to work with and they both are doing really well! I was kind of concerned about PW development, but not anymore.

I have googled and ai-ed about it... We can call that a breaking change or not to our liking. Or holywar about it) My point was if someone downloads the new code to a site with PHP 7 the site will actually break 😎 But 2.0 is better anyway for marketing purpose and community spirit IMHO as it symbolizes the new era for the module)

I guess this one deserves v.2.0, as we got Soma 2.0 back and finally ready for action! And it is a breaking change after all)

I have it in a Controller file in renderSomething() method called from render(). Function or throw - doesn't matter. I moved this code to init() and even to wireframe.php. The issue is the same. The server returns a 404 code but doesn't redirect and shows an error page. I have tried this on two other sites with Wireframe. And the behaviour is different there. If i put the code in wireframe.php there, it gives me a 500 error. But in controller it works ok and shows the 404 page. Those 2 sites are not multilingual and not so heavily modified... Can you suggest a way I can debug further? I have found the issue. The template of 404 page was changed to a template that caused an infinite loop. Sorry for bothering you @teppo. But natural intellect also needs prompts and you helped me with a one)

Good day, @teppo! Good day everyone! As the topic says. If I throw new Wire404Exception(); in Wireframe controller, I expect a redirect to 404 page to happen. But an error message is shown instead. Is it a bug?

Top one is 62 (+23 repeaters). Regular ones are 15 to 25.

AFAIK Incus is a community fork of LXD developed (partly) by same people. So not so new actually)

Now when they're all pinged, we need to have something for them... Something to do or to write about... Maybe just say hello and share where they're at now...

I can't see the video. Is it just from where I'm at?

Cool @Jonathan Lahijani! So you are still using apache on those LXC instances, right? Have you considered Incus instead of Proxmox? I've read it is more easy to setup and manage if you're good with cli. And is "more native" for LXC's.

This is really cool and migrations is a proper test case for AI as they should touch upon almost every part of PW. I am as excited about all this as everyone else here! And this part (quoted above) of the blog post obviously made me and probably @Jonathan Lahijani and @gebeer think about migrations. Though I can imagine that @ryan himself didn't think about this in quite that context. I myself too was not so long ago questioning Claude Desktop about almost the same thing. How to track and migrate all changes from one installation (dev) to another (prod). How to commit, examine and review in-admin-made changes when working with the same PW site in a team. And I asked to compare with Rock Migrations and to propose something superior. The answer was in fact to offload "the entire scope of a ProcessWire installation (pages, templates, fields, modules, etc.)" to a file with a predefined schema. Then to build a tool to compare and to produce a diff, which could be applied to another installation. So today's blog post actually seems like a ground floor for this. I can present this document later if needed (but nowadays you can produce such for yourself in minutes) But me too wouldn't want to have AI be required to run these migration / apply those diffs. It might be true but still doesn't fit in team development workflow (if there will be one in the new brave AI coding world))) So maybe this is a time for us, humans and robots, to unite and create something awesome in joint effort? Humans may be not as productive. But they are imaginative. And they are the end users of PW still) P.S. Claude knows how to position himself correctly with all these compliments. I think we need to be careful with AI. Communicating with real people is, of course, less pleasant. But for now, it's still a necessity.

Good day! One of my templates has a list of allowed (whitelisted) url segments set (via "Which URL Segments do you want to allow?") . And all of them but one should end with a trailing slash for SEO reasons. The new url segment (called `sitemap.xml`) should work without trailing slash. Could you please suggest how this could be done?

This start to look like "The Expendables". The superheroes are back 😎

It is really a pleasure and an excitement to see you back, @Soma! I am sure something great is going to happen soon!

Thanks @robert! You support is lightning fast ⚡! I was just writing the 2nd issue in github when the 1st one was resolved)))

And about Repeater Matrix page classes. There were discussions to have custom classes for RM types... Is this possible?

Awesome! Want more of those! ‐-- Custom page classes really aren't a "view" layer in any form, and I suggest keeping all markup generation code within /site/templates/ and subdirectories within it. Would love to know more about how you implement the view layer. Components with several views.. Controllers for url segments and stuff like that...

Good day, @bernhard! First of all, I have to thank you for being who you are. A lone talented enthusiast trying to build a sustainable living on top of our beloved CMS. But not just making sites like the rest of us. But creating your little module-selling empire))) Taking on every hard problem ever put in front of a PW developer and solving it in no time. You have leaded the way for us for some many years. Everyone here has been following you in one way or another. And thus I feel sad about you taking this decision. Yet in the same time I can imagine the freedom you should feel after it. I really wish you good luck in any place your future journey will take you! I sounds like I am saying goodbye to someone leaving, but I am not. I am just saying that every end is the new beginning. What else I would love to invite you into doing is to analyze why this path of yours (creating a bunch of super cool module) didn't lead you to the place expected. Recently @kongondo, the only other prominent paid module creator I can remember, has done the same exit as you. Why is this? This question is of interest to me because I have many times thought about how I myself could build my income upon what I love and know - ProcessWire. Could it be, that PW is so much a DIY kind of thing, that most of us want to build something of our own and are not ready to subdue to modules authors' way of doing things (other than @ryan himself)? Or does everyone here enjoys opensource so much that proprietary is something to avoid? Or is it just simply not enough of target audience?