-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multilanguage page urls #1
Comments
@rolandtoth You probably already know this, but if you enable the AdminLangSwitcher module included with the AdminOnSteriods module and change the admin language to something else like German then the processwire-fieldtype-assisted-url module will prefix the url's with the German versions of the selected page. Is that what you were hoping for? I'm not sure what would be the best way to allow a user to choose what language?
I don't know if any of this is possible. I'm new to Processwire and multilingual so I'm probably missing something. I just thought I would throw out some ideas. |
All I did when I orginially implemented this module was to trigger the add-link-dialogue ProcessWire opens, when you click the corrensponding button in the CKE richtext editor and grab the results. I never used multilanguage sites in ProcessWire, so I don't know what this dialogue does if you are in a multilanguage scenario. |
I spun up a development site using the multilingual profile. All the options(page in the assisted-url dialog will will use the user's language by default. Currently the only way to choose a page in a different language is to the AdminLangSwitcher module, but that reloads the entire page. I submitted some ideas that might help this at rolandtoth/AdminOnSteroids#22. |
Thanks for the module, been using it on some sites and it's a great help.
However, on a multilanguage site if I "Select a page", always the URL of the default language is what I get, not the localized URL.
Using a Page field and selecting a page works just fine, the localized URL is given back.
The text was updated successfully, but these errors were encountered: