Redirect users to context based on browser language setting

24,544 Posts

BobRay Reply #31, 13 years, 8 months ago

I've used the default browser on my Android phone to work in the Manager a number of times, so it's not completely unusable, at least for Android.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

☆ A M B ☆
179 Posts

mindeffects Reply #32, 13 years, 8 months ago

Quote from: BobRay at Jan 27, 2013, 05:28 PM

I've used the default browser on my Android phone to work in the Manager a number of times, so it's not completely unusable, at least for Android.

No, it is not completely unusable on an iPad. But you will reach a deadend pretty soon, e.g. how do you do a right click? Can you change a system setting? Why are those not normal input fields anyway? Why must the wheel be reinvented?

MINDEFFECTS – DESIGN for PRINT, WEB and MEDIA
http://twitter.com/mindeffects · http://www.facebook.com/mindeffects · http://www.youtube.com/mindeffects/ · skype://mindeffects_oliver

24,544 Posts

BobRay Reply #33, 13 years, 8 months ago

Excellent questions.

I wonder if more recent versions of ExtJS are more mobile-friendly.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

☆ A M B ☆
24,524 Posts

sottwell Reply #34, 13 years, 8 months ago

I've never liked extjs. Too cute and clever. Easter eggs are fun sometimes, but rather annoying to have to hunt for them to find needed functionality. It would be much better to have a little "edit" icon if you don't want to show the input field. As it is, you have to guess - double-click? right-click? isn't an editable field at all? Click save? Click off the field? Enter?

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

☆ A M B ☆
179 Posts

mindeffects Reply #35, 13 years, 8 months ago

Quote from: BobRay

Excellent questions. I wonder if more recent versions of ExtJS are more mobile-friendly.

I don't know. But I wonder anyway if a backend really needs such a monatrous JS library. For some great UX/UI experience a lightwight might be just all you need. Keep the things simple, efficient and fast! And the users will be happy.
Quote from: sottwell at Jan 27, 2013, 11:08 PM

I've never liked extjs. Too cute and clever. Easter eggs are fun sometimes, but rather annoying to have to hunt for them to find needed functionality. It would be much better to have a little "edit" icon if you don't want to show the input field. As it is, you have to guess - double-click? right-click? isn't an editable field at all? Click save? Click off the field? Enter?

Icons would be one thing, maybe. On the other hand, I like the hidden layer of option, if it was somehow a little more intuitive and consistent ("edit" or "update", one is enough and that is edit). The popup option also have more space for real text, because I don't want to imagine an icon for "hide from menu". ;-)
But I would want to start on a much more basic level. Those grids could be just a bunch of input field. Click, cursor blinks, do something finished. Advance with the tabs key and maybe autosave-on-leave.
The list-boxes could be just simple selects. I allways takes me two or three attempts to change a media source of a TV, because the extjs dropdown behaves like a moron. Those little things are just nagging.
Since this discussion already when sooo off topic, I would like to add another thing here: You guys, Bob and Susan, where in Utrecht. This was more then 3 month ago. I get the feeling that nothings much of the things discussed there are making their ways into the development timeline. You both are some of those "heavy weight" users with a history to the project. You have some influence – and may it only be like a "friends of MODX for a long time" thing. What's happening at MODX? Are there any official statements about a roadmap and stuff? Whe are we, where are we heading? There are so many little things that need to be improved to make MODX even more awesome. But those little things are in the user interface – the part of a system that developers often don't take to much care of. If MODX really wants to stop hiding in plain sunlight, the user interface has to become tighter, more for the user then against him! Arrangig TVs is a major things when you are creating custom interfaces. I can drag'n'drop my dashboard widgets, but not my TVs. C'mon, seriously. The list of Utrecht has many of those little naggers. But is the list getting shorter?
I know, the core team is not that large, but since I am not a developer I cannot help the guys here. But I get the feeling that although they are listening nothing much happens. I hope I am wrong, but the feeling just doesn't feel so good. Before the work of a better ecommerce solution starts, the regular features have to be straightened. No new roadwork until the old ones are finished.

MINDEFFECTS – DESIGN for PRINT, WEB and MEDIA
http://twitter.com/mindeffects · http://www.facebook.com/mindeffects · http://www.youtube.com/mindeffects/ · skype://mindeffects_oliver

☆ A M B ☆
350 Posts

Menno Pietersen Reply #36, 13 years, 8 months ago

Quote from: mindeffects at Jan 26, 2013, 05:32 PM

Yep. Maybe this setting keeps Menno's script from working.

P.S.: I am on the iPad today, so I could not use the manager (C'mon, WTF?!) to look it up.

I am afraid Redirector is still not working with allow_forward_across_contexts turned on... Any link from Redirector goeds to the English page.

MODX Ambassador (NL) | Responsive web design specialist, developer & speaker
DESIGNfromWITHIN, MPThemes and Any Screen Size
Follow me on Twitter | Read my blog | My code on GitHub

24,544 Posts

BobRay Reply #37, 13 years, 8 months ago

Contrary to what you might think, Susan and I are mostly out of the loop when it comes to the roadmap. For the most part, we have to look at what's happening at GitHub so see what's going on, just like everyone else.

https://github.com/modxcms/revolution

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

☆ A M B ☆
179 Posts

mindeffects Reply #38, 13 years, 8 months ago

Menno, maybe this guy here as some ideas:
https://forums.modx.com/thread/82047/modx-revo-multilanguage-issue-with-web-context#dis-post-452764

P.S.: I like the "language redirect within htaccess".

MINDEFFECTS – DESIGN for PRINT, WEB and MEDIA
http://twitter.com/mindeffects · http://www.facebook.com/mindeffects · http://www.youtube.com/mindeffects/ · skype://mindeffects_oliver

☆ A M B ☆
350 Posts

Menno Pietersen Reply #39, 13 years, 8 months ago

Thanks mindeffects, I have seen that post and that is also not working for me....

MODX Ambassador (NL) | Responsive web design specialist, developer & speaker
DESIGNfromWITHIN, MPThemes and Any Screen Size
Follow me on Twitter | Read my blog | My code on GitHub

180 Posts

troubadour Reply #40, 11 years, 10 months ago

Hi !

i have a little problem lik Menno...

when i go to my website like www.website.com i would like to be redirected to the /fr/ context (i use babel). But it doesn't work.
so the url show www.website.com and once i click a link in the menu, i go to www.website.com/fr/page.html
if i click the base_url link, i go back to www.website.com/fr/ no problem.

the problem is really the landing page, to go directly to the default context, or better, to the context based on the language of browser' visitor.

i tried this plugin :

<?php
//make sure the plugin does not run on the mgr context (the manager)
  if ( $modx->context->get( 'key' ) != 'mgr') {
    /**
     * grab the current context from the request "c" parameter (or context_param_alias from system settings)
     * the alternative .htaccess friendly URL rewrite rule must be activated
     */
    $cntxt_param = $modx->getOption('context_param_alias', null, 'c');
    if ( isset( $_REQUEST[$cntxt_param] ) && $_REQUEST[$cntxt_param] != '' ) {
      switch ( $_REQUEST[$cntxt_param] ) {
            
        case 'en':
          //switch the context
          $modx->switchContext('web');
          //set the cultureKey
          $modx->setOption('cultureKey', 'en');
          break;
            
        case 'fr':
          $modx->switchContext('fr');
          $modx->setOption('cultureKey', 'fr');
          break;
            
       case 'de':
          $modx->switchContext('de');
          $modx->setOption('cultureKey', 'de');
          break;
  
       case 'it':
          $modx->switchContext('it');
          $modx->setOption('cultureKey', 'it');
          break;
            
        default:
          switch ( $_SERVER['HTTP_ACCEPT_LANGUAGE'] ) {
        
           case 'fr':
              $modx->switchContext('fr');
              $modx->setOption('cultureKey', 'fr');
              break;
                
           case 'de':
              $modx->switchContext('de');
              $modx->setOption('cultureKey', 'de');
              break;
         
           case 'it':
              $modx->switchContext('it');
              $modx->setOption('cultureKey', 'it');
              break;
                
            default:
              $modx->switchContext('web');
              //set the cultureKey
              $modx->setOption('cultureKey', 'en');
              break;
          }
      }
    }
  }

but it doesn't work for me. do i need to change something more in .htaccess file ?

thanks for your help !