Jump to content
Pierre-Luc

Autodetect Language

Recommended Posts

On GitHubhttps://github.com/plauclair/AutodetectLanguage
PW's Modules repohttp://modules.processwire.com/modules/autodetect-language/
 
This ProcessWire 2.x module tries finds a best match between HTTP_ACCEPT_LANGUAGE and currently installed languages.
 
If a match is found, the user will be redirected from the requested page to the same page in his preferred language. This match occurs only on the first page load, and will work with default caching on. If no match is found, the website will revert back to the "default" language.
 
Installation info and more details on GitHub. Please submit any bug on the bug tracker, as it is easier to track different issues.

  • Like 12

Share this post


Link to post
Share on other sites

I just pushed version 1.0.3. This version introduces a new option: "Do not detect language if GET parameter is set". You can now set a GET parameter to prevent language redirection on some requests with this parameter. For example, if this parameter is set to "nodetect" and the user requests "http://example.com/de/?nodetect", the plugin will not redirect the user to the user's preferred language or fall back to default.

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

have you tested this great  :) module with ProCache (or default cache only)?

On production I see a strange behaviour (= it does not work, no redirect) but if I clear or disable ProCache it works well.

My default language isn't EN but IT, so it should redirect always to /en/ with a browser with HTTP_ACCEPT_LANGUAGE  != it.

Thanks

Share this post


Link to post
Share on other sites

Nope, unfortunately I don't typically use ProCache on my projects. My understanding is that ProCache completely bypasses the typical rendering procedure, and this module hooks to Page::render so they might not be compatible. I would suggest contacting support and see if there's a way to hook into it, I'd be glad to implement this.

Share this post


Link to post
Share on other sites

Thread opened in ProCache forum  :)

Tried also with this but no luck..

Share this post


Link to post
Share on other sites

ProCache bypasses PHP all together, so there cannot be any dynamic functionality.

  • Like 1

Share this post


Link to post
Share on other sites

:(

Aside from ProCache.. another little question.

My default system language is it (customer request) but for all request outside it browser I want to fallback to en.

With defaultSiteLanguageCode set to en all the call from it browser are redirected to en (because not match it -> "default").

Does it make sense for you?

- defaultSiteLanguageCode -> it

- fallbackSiteLanguageCode -> en

Or something similar..

Thanks

Share this post


Link to post
Share on other sites

And.. add a check for not active language (e.g. fr): so when a language is visible but not active translator can translate pages in backend but the module does not redirect on the /fr/ page.

Share this post


Link to post
Share on other sites

@Pierre-Luc, thanks for your module, but I always thought that redirect to a language automatically isn't good and Google seems to support this:

https://support.google.com/webmasters/answer/182192?hl=en

Avoid automatic redirection based on the user’s perceived language. These redirections could prevent users (and search engines) from viewing all the versions of your site.

What do you guys think?

Share this post


Link to post
Share on other sites

The problem for google is that the crawler most likely will be redirected everytime it visits your site, depending on how "first visit" detection is implemented. For real users it's bad if you just autodetect the language without letting them change the language afterwards, everything else is no problem.

Share this post


Link to post
Share on other sites

Hey Sérgio, I've read that too but after doing some research it's really not as clear cut at StackOverflow might want it to be. :P

As far as I know crawlers don't use Accept-Language typically, and the plugin does absolutely no redirection when it is not set so it should not change their behaviour. This is what Google's documentation says, and others too, and it's also why I implemented the plugin the way it is implemented.

From the "Location-aware crawling" page from Google, you can read this:

If your website has pages that return different content based on the perceived country or preferred language of the visitor (i.e., you have locale-adaptive pages), Google might not crawl, index, or rank all of your locale-adaptive content. This is because the default IP addresses of the Googlebot crawler appear to be based in the USA. In addition, the crawler sends HTTP requests without setting Accept-Language in the request header.

This means that if your website is serving purely based on Accept-Language, there might be trouble cause Google isn't sending any typically, I've seen this happen in the past. The plugin does none of this, it's in your hands to implement a good solution.

What you want to do :

  • DO use <link> with hreflang to help the crawlers find other pages.
  • Don't serve multiple languages from the same URL — always use lang.example.com/.. or example.com/lang/.. It's confusing to users not to and they can't send pages to their friends in the "right" language.
  • Don't use GET parameters to set anything language related.
  • Don't prevent the user (or crawlers) from switching languages and become trapped in a language that isn't their own — aka always have a language switcher in a prominent place and don't detect more than once.
  • Read all the "International" section very carefully and find a solution that works for you. Localization is not an easy topic. 

Note tough that Google tells you what alternative methods supported (tough there's a huge red warning box at the top of the page) :

Currently, Googlebot recognizes a number of signals and hints to determine if your website serves locale-specific content:

  • 1) Serving different content on the same URL—based on the user’s perceived country (geolocation)
  • 2) Serving different content on the same URL—based on the Accept-Language field set by the user’s browser in the HTTP request header
  • 3) Completely blocking access to requests from specific countries

In each case :

1) AutoDetect language isn't a location (geo-ip or else) aware plugin.

2) Discussed earlier, wouldn't recommend for various reasons but might still work. Google says "usually don't".

3) That's the firewall's job! :P

However, if you guys still follow best practices and have trouble being indexed, I'm open to look at more "advanced" solutions. …But more complexity means more points of failure and that's something I usually want to avoid. Just want something that's accessible to beginners and works in the most common cases. :)

  • Like 2

Share this post


Link to post
Share on other sites

Hi Pierre-Luc,

first, thank you for this nice module!

I added a new variable 'noBackend' which allows to test if the page requested belongs to the backend. As I configure the language for login user explicitly, I wanted to have a possibility to prevent admin pages from being redirected, without using a GET parameter.

Shall I send you a patch?

Cheers Oliver

Share this post


Link to post
Share on other sites

Hi oliverx, that's a nice addition. Send me a patch (in a new issue) or pull request on GitHub, I'll review it and incorporate it in the next few days. If you're not on GitHub send it over at info@plauclair.me

Thanks!

Share this post


Link to post
Share on other sites

As far as I know crawlers don't use Accept-Language typically,

I had a problem with Wordpress recently. After the Google Update from last week, all translated pages got dropped from the index and their content was replaced with the default EN language content. A mega disaster. A fix was to switch off automatic language redirection (WPML).

I am mentioning this here, because if this module is crafted on the above mentioned assumption that crawlers don't use Accept-Language, it might be interesting whether this is still the case and what the consequences are, if not.

 I am not a SEO specialist but I found this brand new article from 2016:

https://support.google.com/webmasters/answer/6144055?hl=en

If your site alters its content based on any Accept-Language field set by browsers’ HTTP headers, Googlebot uses a variety of signals to try to crawl your content using different Accept-Language HTTP headers. This means Google is more likely to discover, index, and rank your content in the different languages your site supports.

So, what do you think?

Share this post


Link to post
Share on other sites

Hard to say without seeing the <head> on the specific pages you're talking about.

Google still says this though: IMPORTANT: We continue to support and recommend using separate locale URL configurations and annotating them with rel=alternate hreflang annotations.

 
Discovering based accept-language is one thing (this targets the users), you should still use the hreflang tags and <html lang="…"> (this targets crawlers). This will give better results as it's not prone to interpretation I believe. I haven't seen anything weird on the sites I use the plugin on yet, but will be monitoring. 
  • Like 1

Share this post


Link to post
Share on other sites

Hi

Does upgrade to PW 3.x is planned?

Thanks

Share this post


Link to post
Share on other sites

running PW3.0.98 and simply cant find a way to default the lang to fr-FR on the front end. Hoped this module would do the magic but can only ever get en-EN on enter to the site in a private session. Guest user lang is fr. Something else I need to be doing?

Share this post


Link to post
Share on other sites

I used this way very often in the past @benbyf

<?php

// create /site/modules/LanguageDefault
// create file LanguageDefault.module
// refresh modules in PW admin

// https://processwire-recipes.com/recipes/change-homepages-default-language/

class LanguageDefault extends WireData implements Module {

    /**
     * getModuleInfo is a module required by all modules to tell ProcessWire about them
     *
     * @return array
     *
     */
    public static function getModuleInfo() {

        return array(
            'title' => 'LanguageDefault', 
            'version' => 1, 
            'summary' => 'A work around to changing the default language.',
            'href' => 'https://processwire.com/talk/topic/9322-change-default-language-for-homepage/?p=89717',
            'singular' => true, 
            'autoload' => true, 
        );
    }

    /**
     * Initialize the module
     *
     * ProcessWire calls this when the module is loaded. For 'autoload' modules, this will be called
     * when ProcessWire's API is ready. As a result, this is a good place to attach hooks. 
     *
     */
    public function init() {
        $this->session->addHookBefore('redirect', $this, 'setDefaultLanguage'); 
    }

    public function setDefaultLanguage($event) {
        if ($this->page->id == 1 && $event->arguments(0) == $this->page->localUrl('default')) {
          $event->arguments(0, $this->page->localUrl('de'));
        }
    }

}

Found at: https://processwire-recipes.com/recipes/change-homepages-default-language/

  • Like 2

Share this post


Link to post
Share on other sites

Yes... no... maybe... most of my PW sites are in german, so if I get this wrong, it's my fault. Otherwise I missed a thought. 😉 

But yes, it would be nice to set a "real default" language in PW and therefore a PW-wise session/redirect.

Nontheless this snippet saves me most of the time if I miss-configured something.

 

Hope this helps in your case.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...