Ivan Gretsky

Thanks, @teppo! This is cool reminder about the Wireframe::page() function. This is super useful to render repeaters as part of another page. I am rendering RepeaterMatrix page for a login (another take on this one). So I was hoping to create a controller and set of views for a RM page to separate the logiс. I cannot use a dedicated page for this. I am wondering, maybe there is a way to render custom content Wireframe way without being tied to a page? I am in a PageRender hook trying to change the output for the unauthorized. Would like to render custom view in a custom layout without a page (and a template). Now I try to have this stuff in another template's controller in a url segment handler. But this doesn't feel right)

Thank you friends! This approach works. The only thing I had to change using $input->setUrlSegment(1, "segment"); instead of dynamic property setting to get rid of warnings in PHP 8.2.

Thanks Iskender! But that is not exactly what I am after. I need to render a page Page::renderPage hook and replace the output with another page render. wire()->addHookBefore('Page::renderPage', function (HookEvent $event) { /* CONDITIONS CHECKING */ $event->removeHook(null); // Remove this hook so we do not get caught up in a loop. See https://processwire.com/api/ref/wire/remove-hook/ $someOtherPage = wire()->pages->get(...); // Get the page to be rendered instead of the current one $event->return = $someOtherPage->render(); // HERE I NEED TO RENDER A PAGE OTPUT FOR AN URL SEGMENT INSTEAD OF REGULAR RENDER $event->replace = true; ...

Good day @teppo and fellow wireframers. I would like to render RepeaterMatrixPage items with wireframe. Tried to do it the regular way by adding wireframe as an alternative template file to their system templates and creating a contoller. But that didn't work out. Just maybe it is easy to achieve with some additional hook?

Good day! I need to render a page output for a given url segment from API. There is a way to render a page with $page->render() and now with $page->renderPage(). But I can't find a way to render a page passing in an url segment. So the output would be not of site.com/page but of site.com/page/urlsegment to make it more clear. Please share your ideas.

I have created an issue about the same bug a few hours ago: https://github.com/processwire/processwire-issues/issues/2160

A hint for whomever used PageRender::renderPage to achieve what is now available with Page::renderPage(). See here to fix your code, which would be broken after the update. A rare time I ever needed to adjust code for a new version. PW is super stable in that regard.

Good day, whoever needs this years later) This trick for hook is obsolete after the newly introduces Page::renderPage hook (see here). That is great, but it does break the old way of getting page with the line quoted above. Change the code to something like this: wire()->addHookBefore('Page::renderPage', function (HookEvent $event) { $page = $event->object; ...

Always wanted those on Page. Even before custom classes existed. Great addition! I think that custom classes truly need more introduction and use cases. So eagerly waiting for Ryan's upcoming blog post.

Back to the basics. Great stuff! Most of the forum posts are about new features. But I really enjoy reading about how to use PW, tips and tricks and such. Would love to see more of those and from Ryan himself especially.

Hi, @Jonathan Lahijani! I am pretty sure that your existing setup is superior for the multiproject needs of yours comparing to ddev. You try to standardize while ddev is all for making something custom. I would play with some new php stuff on ddev to keep up with the hype. But would stay with you current setup for the paid work.

Good day @ryan! After the launch of the redesigned admin theme and site I had private conversations with some community members about it. And I have to say that they were pretty harsh about it. Some of us are choosing words here in the forums keeping hard thoughts to ourselves. Was it the right move? Was it made with enough consideration? Didn't it cost too much breaking things that worked? Is it possible to rollback somehow? This is what at least some of us here are silently thinking. Ryan, a lot of us here like myself have always relied on your vision and gut. You have managed to deliver exactly what was needed so many times. We want to believe the redesign is the right move too and we are just are too accustomed to the familiar and struggling to change opinions... So let me ask this. You see the google analytics metrics, downloads and stuff. Maybe you can measure something else like forums activity rate. How did it change with the redesign? Did you get what you expected?

Good morning everyone! Congratulations with the new look! This redesign effort is something we've been waiting for a long time! I am reading the new site from mobile and I rediscover a lot of great content I forgot existed. I think the navigation logic is improved greatly. Surely, there are visible bugs and glitches here and there. And I didn't see the new site from the desktop yet. But new look is modern and cool. I remember getting used to the last redesign. It was a pain. We as people have hard times seeing something we love change. But the world has to move on) And I am pretty sure here it is for the good! Another amazing thing is that an international community-driven team of volunteers has been working on a redesign. This is so cool and I hope to see more of such for PW in every aspect of its development (like in fixing those bugs and glitches)). Great thanks to the volunteers!

Great! I was waiting for this moment since the times stars were not yet rounded in k's)) Congrats, everyone! But I still want to encourage everyone reading this go and check it their ⭐ is there and properly counted. And add it if not. We are heading for 2k))

And now... someone is going to be the one to change that 3-digit count to a beautiful 1000. Who is that going to be? I am a little jelous I can't be the one.

And here goes another friend of mine! Only 2 more to go! Seems like we won't need the whole weekend😎

@kaz, pages in PW are just a storage mechanism. They are called pages historically, but are often used as nodes, data items etc. Using pages as values for selects is a recommended way to go in PW. So @virtualgadjo's advice is a great one and a best practice. So do not hesitate and use it. See the 1st sentence of the official docs here : "While we usually recommend using the Page Fieldtype for selectable options..." P.S. Please star ProcessWire on github!

@harmvandeven, @thomas, join us! Got the game! I hope we're not getting banned for spam)

+2 !!! +3 !!!!! Hey, I know those 3 by names... Community! Start to show your power!!!

Nice challenge! Pinging my friends and colleagues. Already +1 )))

Good day, everybody! Sorry for not answering in this thread. Going through some not so easy times here. And working on this module is out of my reach for now. More to that the leaflet site is not even accessible from Russia (this is where I am at) as the lib author is in Ukraine. You can guess why. But maybe I have got a way around. Just maybe you noticed that the module repo is under the FriendsOfProcessWire organization. I was hoping to gather a team of PW loving devs under this org and support some important but abandoned modules there. This plan didn't work out (yet?) but we can try to make it work. If someone here in this topic feels willing and capable to take care of FieldtypeLeafletMapMarker (at least for a while), please write to me a PM and we will decide how to go on. I was always wishing a more productive community cooperation around PW and just maybe it is time))) P.S. I am now out of town so might not answer quickly. But I will)

I am using Bookstack too for some docs. But I really do not think it should be used for community maintained docs for an open source project. Those should be open for commits from everyone. I think that VitePress or Docusaurus or Mkdocs or even some php static site generator. The docs are markdown in the repo and contributing is just a PR.

Not so fluent with composer. So consulted the docs. Seems like composer update --with-all-dependencies will do it.

What a twist!!!

I have not tested the module with PR merged. Just seen it in the last moment before creating an issue in github repo about compatibility. I am waiting for @robert to share his thoughts on this. Maybe he is already in the process of working with your PR. Will ping him on github too.