Ivan Gretsky

Hmm. I took that for granted. Though that existing data structure could be used. Visually mapped to. Sorry for asking questions without doing my part to investigate first.

Wow! Looks super cool! 🎉 Well, reads) Could you please add some screenshots or a video? And a questions right away (I have not install or use the module yet). Are Repeater and Repeater Matrix fields handled somehow? We've got content builder builder based on Repeater Matrix.

Good day, PWmates! I just had a super productive and mega fast support session with @FireWire. Great thanks to you, man! I almost forgot how pleasant is it to be here, in the supportive and friendly PW community. I am 12 year around and this great spirit is not going nowhere) Happy New Year to all of us here, where we unite and make at least a little corner of the world a better place! P.S. And if you think this post is late to the party check this out))

Good day, @robert! Thanks for the module! @FireWire has updated Fluency for DeepL API v. 2.0 which uses different authentication method. Could you please write if ProcessTranslatePage has already done that in v. 1.0? If not are you planning to update?

That is what I thought. Thanks for extra research and tips.

What I was thinking about is PW image field creates variations of image (scaled down, resized and so on). And it does so not on image load, but during render. @maximus, you surely know about this. And PW puts all those into the same folder for all image fields of the same page. So I was wondering if and how this field handles those cases. I guess it does not as it is file field, not image. Or am I wrong?

Hmm, I must have imagined your field was an image field, not a file field. My bad.

Haven't tried the profile or field, but the walks in Switzerland videos are truly awesome) Wonder if page variations are being created well on the fly. Is it taken care of?

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.