Single pages & multilanguage

Permalink 1 user found helpful
Hi !

I'm working on a website which requires a member registration.

I could use "/register" single page for the registration form, but this website is available in 4 languages, so I can't have just one single page for that.

I must create 4 "/register" single pages to have different urls ("/register", "/inscription", "/registrar", ...).

So, I think single pages are logicals in a context of monolingual website and for dashboard pages too. But useless for multilanguages websites or not very clear about their functions.

What do you think about that? Could you advice ?

Thanks

moosh

moosh
View Replies:
peterrr replied on at Permalink Reply
Ah that's funny. I have exactly the same issue with the page_not_found single page. I was thinking of just duplicating them and do redirects after I checked for the language with the multilingual helper.
moosh replied on at Permalink Reply
moosh
Oh :)

Yes it's not very clear.

Single pages are logical for dashboard pages and system pages (404, 403) because these pages must be available at one unique url.

But as said in the documentation page (http://www.concrete5.org/documentation/developers/pages/single-pages), "multiple login pages makes little sense" is wrong because you can have different login pages requiring a different urls and names in a multilangual website. Same comment for "register" page.

Single pages makes little sense and should be renamed "Dashboard pages" or "System pages".

"login" and "register" should be a core block which can be added anywhere.

Actually, in a multilangual website, I need to make a single page for each language if I need a different url or name for a register page or login page.

Best,

moosh
Mainio replied on at Permalink Reply
Mainio
With Language Manager you can bypass this issue because it can display those single pages with the language that is detected from your visitor's browser:
http://www.concrete5.org/marketplace/addons/language-manager/...

Other way that I can come up with quickly is setting a session variable that would keep track of the selected language and then translate the single pages accordingly to that.
moosh replied on at Permalink Reply
moosh
Hi Mainio,

Yes. Using t() function we can bypass this problem but the right problem is the url which is the same for all languages!

Best,
Mainio replied on at Permalink Reply
Mainio
Oh, okay!

Then yes, you probably need own pages for that. Other option would be to setup some custom paths that just display those pages. So e.g. requests for /registrar would be "mapped" actually to /register and just display that page in different language.
moosh replied on at Permalink Reply
moosh
Yes, but not the good solution in the end.

We are ok that they are not really useful for the frontend at this stage of progress of concrete5 and sites increasingly multilingual, right ?
Mainio replied on at Permalink Reply
Mainio
Yes, I would think that the number of multilingual sites is growing at the same pace as the main system.

To support this feeling, there are increasing amount of people reporting the multilingual bugs and discussing about multilingual issues. At least in Germany they seem to be quite active on those issues.
moosh replied on at Permalink Reply
moosh
Yes that's right!

Thank you Antti for your support.

I hope the core team will see this post.

Best,