gerritvanaaken

Here is my final init.php code for bilingual password forgot. if (wire('session')->language) { wire('languages')->setLanguage(wire('session')->language); } $wire->addHookBefore('ProcessLogin::execute', function($event) { if (wire('input')->lang == 'fr') { wire('languages')->setLanguage(7085); wire('session')->language = 7085 } });

I’m such a noob! I used the hook with function parentheses. ProcessLogin::execute() is wrong. ProcessLogin::execute works totally fine. Thanks, case closed!

Hey @kixe Thanks for your answer. However, I couldn’t hook in correctly. I tried every hook from "ProcessLogin". The most suitable seemed "buildLoginForm" or "renderLoginForm", because I want the form itself to be translated. None of my hooking attempts seemed to be executed. This is from my init.php: $wire->addHookBefore('ProcessLogin::buildLoginForm()', function($event) { wire('log')->save('langlog', 'language should be: '.wire('input')->lang); if (wire('input')->lang == 'fr') { wire('languages')->setLanguage(7085); } }); I cannot explain why there is no log entry after visiting mysite.com/processwire/?forgot=1&lang=fr

If my backend has two languages, is there any way to force (via URL parameter?) which language will be displayed on the login page and the password forgot page?

Maybe I’ll just build the language-dependend "show/hide" switch as a hidden field, and then write a little bit of custom javascript to somehow make it very compact in the top right corner. Let’s see how that works out.

Brilliant, exactly what I needed!

Insane! Great, thank you. I submitted a pull request on github, because in my installation the created label was empty.

Of course that’s the obvious thing to do. But it takes a lot of space and makes my (already) complex repeatermatrix items even more complex... Any ideas for "hacking" oder "hooking" into these little icons in the top right corner?

Wouldn’t it be cool to have whole repeater items (or even repeater matrix items) language-specific. Some of my clients do have pages that are 90% identical in German and English, but there are some sections that should not appear in one or another language. I attached a concept screenshot. Would something like this be possible with some simple backend hooks and "hidden checkbox fields"? Or is it way more complicated?

My client could save some time if she could select multiple pages at once. Of yourse, we are using the standard page selector in multi-tree mode, but she has to select one page after another. Each time she has to open the site tree again and open the required subtree, finding the page she wants to select. Would be cool to let the tree open after selecting a page, so she could select multiple pages in one "tree session". Understand what I mean? Anybody any solution to this? Alternatively, maybe the site tree could keep its state with all the subtrees open, when you are re-open it again.

It’s a rather complex thing. We have 7 base types: Text, Teaserbox, Image(s), Video, Divider, Bike Teaser, Download(s), each of which comes with some additional options for the rendering in the template. I don’t know what the "depth" feature is The menu is rather simple, I add the bike images via javascript later, the rest is pretty much a standard menu.

Why not? We thought it looked good and shows the expandability ;-) No, the configurator is a separate application which is tightly connected to the internal "Warenwirtschaftssystem". It’s done by a different company.

Velotraum is a small German manufacturer, building rather costly, individually manufactured bicycles for both globetrotters and everyday bikers. We use RepeaterMatrix for long structured texts, and we use a lot of individual fields for metadata. We even built our own "preview" function for blog comments and included Textile light for blog comments, too. Have a look: velotraum.de

@flydev Awesome, works like a charm!

@louisstephens Thank you for your thoughts! Sure, I could use these "nested" queries to gather a "global comments array", which I would to sort by "created" afterwards. But these are too many steps and seems not very performance efficient.