Ivan Gretsky

I mean pull request in the module repo - https://github.com/kongondo/MenuBuilder/pulls Thanks for the code! I've seen it. But didn't try yet. A github pull request is just an easier way to deal with code change proposals.

Great! Did you create a PR, so we can like it and make it easier for @kongondo to fix this for all of us?

Good day @teppo! Another question from me) I am building a solution based on PW and Wireframe, that needs the theming functionality. That is switching theme (default views) for all the views and components. Layouts and partials probably too. Is there an easy way to achieve this with current code? Maybe a couple of hooks? I can see two ways how it could work. Put `alternative-default.php` everywhere the `default.php` files are and somehow tell Wireframe to use those prefixed files. If there is another view except the default one, the prefix should work as well. Like `alternative-json.php`. Probably an option should be available whether to fallback to defaults without the prefix or not. Create an overrides or theme folder somewhere and have somehow point Wireframe to use views from there. For my personal need the 1st approach seems to be a better one. But just maybe it is easy enough to provide possibility for both? Thanks!

Thanks for sharing. I am still wrapping my head around the concept. I it passing variables to a specific view... seems like it. But I am not sure I quite understand what problem does it solve. If you would like to discuss it, a real-world example would help)

How are you doing, @kongondo! Your module is a blast! Still finding some really cool ways to use it to control how menus could be controlled from the admin. The thing that really worries me is that the module seems to be not fully compatible with newer versions of php. https://github.com/kongondo/MenuBuilder/issues/48 https://github.com/kongondo/MenuBuilder/issues/54 Is there a chance you could find some time to upgrade it anytime soon? Or are you willing to accept PRs with fixes? I can see one that is not dealt with yet, so curious if me or someone else should try to come up with solutions with compatibility problems? Thanks!

Good day, @Robin S! Thanks for the module! I've used it with a great pleasure on my single-language sites. But now I need to set things up for the ML site. How would you suggest to do that? I think I would need both language-dependant labels AND urls. Is it better to handle this with hooks, or there could be a way to do it from the UI?

They need to get us used to some more obscure syntax before they introduce the next logical step - mandatory compilation. So be happy they are boiling the frog slowly and we still have a few more happy years just scripting.

Good day @teppo! How is it going? I am using Wireframe as a basis for almost all sites I work with. So really hope you're doing fine) Are there any new great plans for this module? There is a function to create Wireframe folder structure from admin. I was wondering could it be done via API? Need this for a setup script. I know it is not hard to create folders in cli, but a one liner using API would be just neat.

Hey @olivetree! You can use Remote development plugin for VS Code. This way you can work on your staging (or prod if you like cowbow coding)) from a locally installed VS Code via ssh. It install VS Code server on a remote machine and connects to it. So you do not need to have anything but VS Code locally. There is similar thing in PhpStorm I know nothing more about)

In case you really need to build tailwindcss without node and running npm install for whatever reason you can use this https://tailwindcss.com/blog/standalone-cli. Just download a binary, put it somewhere and call with proper arguments. To make it easy in VS Code create a task.

Thanks for a great explanation (as always). I guessed almost everything) I also place the source scss/js in templates/static. Before that I used to put the sources in site/static-src and put the generated files in templates/static. I guess, resources could be a better name for the sources. At least it is a standard place to have them as I use Wireframe (and love it).

So I am here thinking about this again, @teppo. Didn't find an explanation anywhere still. Could you please explain your idea behind those folders?

Hi! 'columnWidth' should do that. You can look up these here.

Glad you're having a good time on our continent, Ryan! Nice choice! It is so cool you are about to celebrate your first half of a century! Seems like you're having a great life so far. But you didn't have all those 50 years to work on PW pitifully, as you had to spend time on childhood and etcetera. Your next half centuries you won't have this excuse))) So waiting for the things to come! Congratulations to @Robin S! Your modules really make the ecosystem a place to thrive! Thank you!

It seems that you're seeing the main problem in those plants' pages presentation in admin. You do not want to see all those 10 thousand pages in a tree. I can relate to that. One possible solution would be to use Page Lister. This way you would see all those pages in a list no matter where they are in a tree. You would be able to search those pages by any their fields. Basic version is included in the core (see the screenshot below). A more powerful Pro version is a cool thing to have though and 100% worth its money. You can still have the pages in the tree hierarchy, or have all the plants under one common parent and linked to categories via page reference fields.

Good day @horst! I've tried to fix the issue, bit with no luck. Did you have a chance to look into it? For now I will try some another module. Maybe it will fix the issue in this case. Or if it doesn't we will know the problem is elsewhere.

Sometimes the best thing you can do for the project you work hard on is to get away from it for a while. When you come back, you'll notice a lot of new shining edges (or the ones to be polished) and almost definitely have lots of new shining ideas about it. So please do this little PW detox to keep it new and sparkling for yourself and all of us!

@kongondo, could you please write what is so exciting about Omakub? I am a long time fan of DHH and all the Basecamp stuff. But the Omakub just appeared to me to be more of a hype type of thing.

Hey, @kongondo! This is the true Linux way. You get into something strange that looks bad pretty soon. And you curse your decision to get into Linux. And then you read. And you understand. And you fix. And you come out stronger and smarter and with a self esteem at the roof level. And then the cycle repeats)) Just don't get away before you feel the vibe. The problems are often with drivers. Not all hardware is compatible. At least out of the box. P.S. They say there is less and less of this nowadays. Not to the point it is not Linux anymore though)

I've seen it on 3.0.219. Just upgraded to the latest dev (3.0.241) and it is got even worse - can't open module config in admin at all:

@horst, how do you do? I do not have WireMailRouter on none of my sites either. Sorry. But I have a bug with my new installation. And it seems to be a long standing - see here. Could you please look into it?

@sodesign, you do not need to create process module for it. You can put this Repeater Matrix menu builder field on any template. For example, on home page. Or create a dedicated template and page for the settings and put it there. You can make a link to it in the top menu with this module (to make it easy). Then you will use these field's value wherever you need to render menu: <?php $menuBuilder = $pages->get('/settings-page/')->menu_builder;

Good day Wire-cli users! I am here to say thanks to @flydevfor his recent small but game-changing fix. This now allows to automate PW installation via script more easily. And you don't have to have Wire-cli installed globally. # clone the repo git clone https://github.com/wirecli/wire-cli.git # update vendors composer update -d wire-cli/ # check if the tool is working php wire-cli/wirecli -V # install PW php wire-cli/wirecli new --force [...other options here] @Jonathan Lahijani, I remember you were interested in this.

When I was in school I had a PHP 4 book. A printed book made of paper. And a Macromedia Dreamweaver book too. When I started to learn webdev with Joomla! I consulted a lot with my former classmate. And occasionally asked something on a forum. When I thought about getting into Drupal I watched a lot of Youtube tutorials. When I started to learn PW the forum was my best friend and I spent hours here. And then the docs got better - I started to read those before going to sleep. And then I learned to read the source code and to find it interesting enough to do it instead of watching Youtube. When I started to learn htmx I had to join their discord. It was nice there and the answers came quickly. But I couldn't find anything by myself. When I needed to get a jumpstart on Laravel, I got my Laracasts account and started to read the docs again. When I need to get my head around some vue stuff I know not enough about I ask Cursor AI and it gives me quick answers most of which really help me to move forward. What's that all about? I do not know yet. Is that about I am old and TOO old to learn something on TikToc? Is that about our lives getting more digital, fragmented and quick? Is it about loosing local real-world in-person communications to around-the-globe communities and AI or making the world "be as one" through better means of communications and freedom of consciousness? Is it about each generation living in its own media and making it the part of the message? There is some room for interpretation here. But I've spent so much time in PW forms, and got so much out of it, and put so much of myself into it I tend to prefer it over "other stuff". I do not know if it is the forum principle itself, its size (not so big and cozy), the great people here or something else. Many times in the past I was even a bit angry on Ryan for him not push PW on every platform and occasion. For PW not grow fast enough and conquer the webdev world. But now I kind of think it is for the good. You can't be this and that in the same time, you can't be everything for everybody. And even if you could It probably wouldn't make you more happy. I do not know how to end this. No moral in the end. Just sending love to all yall here! Go see and join all pinkary, bluish and yellowish places wherever they are. And come back here to tell us about them 😉

Good question, @wbmnfktr! When I came to PW from Joomla! that had an extension for everything including ecommerce and forums, I was kind of expecting PW to be the same. And I was waiting for a good shop and forum to be developed (by someone but me)) But time passes. I am not so idealistic now. I use ProcessWire for sites and some apps. I use other tools for online shops. I do not use nothing for forums as nobody I do stuff for really needs them. For a documentation site I would use VitePress, Docusaurus or MkDocs as they allow a more easy collaboration via github or such. Ryan doesn't use PW as a forum engine or to sell modules. But he does for the docs. But maybe he shouldn't so the community could participate @teppo uses PW for weekly.pw and wireframe site. I like the former and would argue about the latter for the same reasons. @kongondo uses PW for his site but VitePress for the docs. He is using PW and his own Padloper to sell stuff (he should!). @bernhard seem to do everything in PW with some of his numerous modules. Are forum and ecommerce coming?)) I would say that for the recipes the current collaborative approach is quite good. And it better be ready on Astro or you-name-it SSG than be in development in PW. But! I really love to see passionate people push the limits of possible with the tools of their choice. And would love to see recipes still in github to collaborate on, but wisely imported to PW. Especially if there is any additional value in that like more advanced filtering, interlinking or a form for less technical people to commit recipes. P.S. Frankly, I would go the easy way and stay on whatever tool is already in place. PW is great for some sort of things, but not for all.