Search

I'm at a loss then, sorry

Just a quick note as it might be useful to others: Today I was pulling my hair off trying to understand why the LR rewrite rules where not working properly on a website, turned out that my real-estate filtering form was making a query like

?view=map&region=lombardia&price-from=100000&price-to=1600000

The problem was that the "region" parameter was conflicting with the $url-region parameter used by LR. Of course fixing was easy but finding the problem hard.

This pull request removes the Redirect mechanism. See the pull request for a discussion about it.

I want to create such structure:

http://example.com              -> landing page to select language
http://example.com/pt-br/       -> home in portuguese
http://example.com/en/          -> home in english
http://example.com/pt-br/page   -> page in portuguese
http://example.com/en/page      -> page in english

The default is having the same page in "/", "/pt-br" and "/en". How can I solve this?

I'm thinking in have the index page with Language Redirect DS unselected. When people visit "/", one template is showed. If people visit "/pt-br" or "en", the language param is created, and other template is shown. Is it a good solution?

You could use the version vladG mentioned above. It removes the redirect and allows the URL structure you mentioned. I'll incorporate his changes in the next version. See the discussion at GitHub for mor information.

Is anyone updating this extension for 2.3?

You might want to check out the issues list for in depth discussions about this extension

This extension is no longer a requirement for multilingual sites. All multilingual extensions depend on Frontend Localisation from 2.3 onwards.

All multilingual extensions depend on Frontend Localisation from 2.3 onwards.

mmm... maybe I should make gettext compatible as well :)

Is there a way to not have the language codes displayed in the url while not breaking compatibility with other extensions (eg. Frontend Localisation).

Thanks!

The codes are needed there to distinguish between languages. Why do you need them removed?

if making a site with member login etc. I think it is nicer to just store the language information, less clutter in the adressbar. Also when sharing links people will not be forced to a specific language (copy & paste).

I think there could possibly be a way. hooking an extension to add this parameter at the very beginning, however I doubt that your member would be properly initialized by then.

Also I am not sure what your site is about; however you have to consider search engines and SEO in most cases if you want to expose this information so separate urls/domains is essential in between languages. otherwise you would confuse google or only expose a singular language. What you should do probably make a check if the user is language German for example redirect the link to the german version using a 302 redirect.

good points... especially the seo stuff... thanks!

  • if you are working SEO you might want diffent page handles per language. if yes look at pagelhandles

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details