Leaderboard

Hei, I'm wondering how easy it is to get support from someone in a Nordic country. Not that being in the Nordics is required, but it would be my first attempt.

Hi friends! And thanks for ProcessWire! There's an inconvenience in ProcessWire file translation process which, I think, deserves a topic here. It's a common case to have same translatable phrases in different translatable files. Using a translation context (in fact, a separate file holding all that phrases) is also a common case, at least for me. Generally i call that context I18N_GLOBAL. So my typical translation may look like this: <?=__( 'Accept', I18N_GLOBAL )?> The problem is that ProcessWire translation interface is context-agnostic. If You have to translate multiple files containing the same 'Accept'-related piece of code, it will be always treated as not translated yet, even if I18N_GLOBAL file is already translated. Quite annoying, especially if You have lots of phrases to translate. So dear Santa, could You please make translation interface context-aware and to mark all the phrases (in all the files) which already have translation in my I18N_GLOBAL file as translated? Or maybe I missed something, and there's a possibility to tweak some settings and achieve this? Thanks in advance for any possible advice or idea )

@Lutz I think this is addressed in https://github.com/processwire/processwire/commit/24fc229be563de0157ed18ee199dfab889286169 , but this was already fixed in 3.0.184 so I wonder if this is something new?

Great module! Thx! Just a question: dragging the bars is not updating the percentage in the number field for me. ? video-screen.webm

I am a profields user so I will take I look. Can you give an example of the call that is throwing the error? Never mind, I see the issue. When I grab the unformatted field value for the event gives back the combo field itself, not the image subfield within the combo. I'll see what I can figure out.

Ok, good to know. It's probably just easier to use a 'normal' method (CSS & radio buttons or the like). Thanks for the info.

To extend on Horst's answer: you could use a NOT selector with multiple ids separated by a pipe, to exclude them from the result like $expertises = $pages->find("template=case-type, sort=sort, ,id!=123|443|3035");