Search the Community
Showing results for tags 'language support'.
Found 4 results
I want to make a language switcher for my site header but I don't want to use the LanguageSupportPageNames module, in this website case I prefer using path siterootpath/services for English and siterootpath/es/services for Spanish, but I can't print the path without $page->localurl() and that function seems to be only available in the LanguageSupportPageNames module .. too if I put siterootpath/es/ in the browser this causes me a 404 error.. How to do this, please?
I am manually duplicating a 2.7.x site in a 3.0.33 installation, and have run into a couple issues. First, with my language support, a couple of my languages (German, Finnish, English) have the correct url segment (de, fi, en). The rest (French, Italian, Polish, Portuguese, Spanish) all have their url segment showing as 'en' even though I have set them properly under Setup / Languages (I even tried to change these and it did nothing). Second issue: as I create a page of a certain template, the Title and name I input on the initial creation/template selection page is not saved, and instead I get an auto-gen'd name and the title is blank after I click Save. I haven't experienced this with any other templates, and I don't see anything odd about the template settings. If I didn't have a couple hundred of these pages to add to the site, I wouldn't mind figuring it out later, but with that quantity I'd like to sort it out at the start. Creating the page (the template is auto-selected because of the parent page): Then after it's saved, the Content Tab has no Title entered and the Setup tab has the default name: Appreciate any insight from someone who may have run into this already! Thanks!
Hi everyone, I want to use the core module PagePathHistory in a Processwire instance with multi-language URLs/page names activated through the core module LanguageSupportPageNames. From looking at that old Post by Ryan I was pretty sure that it should work without any problems and was surprised that actually it doesn't. PagePathHistory only saves entries to it's DB table when the page name in the main language changes, not when any of the other language names change. Looking at the code this is no suprise as PagePathHistory only hooks Pages::moved(), Pages::renamed() and Pages::deleted(), none of which would be triggered by a change in a language page name. Starry-eyed I started to implement the missing language-awareness in the module, how hard can it be, eh? ...pretty quickly it turned out that this isn't that simple, so I decided to first ask for some help and guidance. Does anyone maybe already work out a solution for this particular problem or something similiar? The problem with the implementation is that after saving a page with changes to language names, there still has to be a means of accessing the old names. For the default language name this is pretty simple because it's saved as $page->namePrevious. For language names the module would have to deposit the original names for later to build the PagePathHistory-URLs. I've been looking through all hookable functions in core classes/modules but haven't found the best place to hook into to implement this functionality. Does anyone have an idea where this would be done best? Any help is appreciated. Thanks a lot in advance Marc