Erbenos

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Erbenos

  • Rank
    Jr. Member
  1. Sorry, I didn't login for quite a while. I am using TemplateEngineBlade module.
  2. Zdravím, kdybych našel nějaký problém či hrubku, nahlásím/opravím. Díky za češtinu
  3. Actually the intro to the article you linked was just what I needed. I guess I should have been more thoughtful about having an option to use translation context. If I just edit the files like this: it works. I can simply edit the template files in Language translator since the compiled templates also inherit the translation context, dummy me. Thanks a lot
  4. Hello, recently i came across this issue. Basically, I am using TemplateEngineBlade module which allows me to use Blade templating engine in my templates. I needed to translate strings like '__(<your string>)', but since the module compiles the templates into its own directory (as highlighted in screenshots), the language translator find the function call in 2 files: Template where the code is written Modules 'compiled'/cache directory where the templates are in their compiled state Now, I actually have to translate the string in its compiled directory else it doesn't work at all. But since that filename changes often it is not usable at all. I tryed prepending all templates with a file (for example _init.php) and getting all translatable strings there which works but not for the use cases where i need to get same string translated in multiple languages in a single page - I would have to create separate variables. Does anyone have any idea which would help me work around my issue? Thanks
  5. Yep, but I dont actually use utf-8 addresses, I just needed to redirect them to 404, because without this option, it wasn't working.
  6. Whoa... this is kind of funny. There is setting specifically for what I want just below: # ----------------------------------------------------------------------------------------------- # 14. OPTIONAL: Send URLs with non-ASCII name-format characters to 404 page (optimization) # ----------------------------------------------------------------------------------------------- RewriteCond %{REQUEST_URI} "[^-_.a-zA-Z0-9/~]" RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?it=/http404/ [L,QSA] One may wonder how does he have utf8 page names and correct 404 redirects but oh well, this is just what i needed.
  7. I actually use your jumplinks plugin for redirecting old rules to the new ones. As @BitPoet said, I ll check encoding and will come back with an answer. Thanks everyone. Update: File is in UTF-8
  8. Yes, that exact line:
  9. Thank you, but that didn't fix it for me. I chanched htaccess, restarted Apache and nothing changed.
  10. Hello, I encountered interesting behaviour yesterday. I have custom module, which serves as 404 redirect which works like this: $this->addHookAfter("ProcessPageView::pageNotFound", $this, "hook404Page"); And in hook404Page function I return 404 page. The problem is while this does work for: http://testsite.dev/nonpage It doesn't work for non standard URL like these: http://testsite.dev/něnpage Any idea why? Thanks.
  11. Hello, how would one integrate SOAP service/client into the admin section of ProcessWire site? I would really appreciate some hints. Thank you.