Understanding site access pattern

Last modification: 2014-03-27 18:11:15

This is kinda tricky feature used by Live Helper Chat. It allows us to do the following tricks

  1. Have different languages by different site acces
  2. Have different design by different site access

How it is used?

Let's take for example this fragment from configuration

'lit' =>
      array (
        'locale' => 'lt_LT',
        'content_language' => 'lt',
          'dir_language' => 'ltr',
        'title' => '',
        'description' => '',
        'theme' =>
        array (
          0 => 'customtheme',
          1 => 'defaulttheme',

        ),
        'default_url' =>
        array (
          'module' => 'chat',
          'view' => 'startchat',
        ),
      ),

I would like to pay attention to the theme array. This theme array describe in what order to look for design files. So if you want to have completely different interface for two difference domains it would be logical just create another site access E.g exmaplecom . Example configuration

 

'exmaplecom' =>
      array (
        'locale' => 'lt_LT',
        'content_language' => 'lt',
          'dir_language' => 'ltr',
        'title' => '',
        'description' => '',
        'theme' =>
        array (
           
0 => 'examplecomtheme',
          1 => 'customtheme',
          2 => 'defaulttheme',

        ),
        'default_url' =>
        array (
          'module' => 'chat',
          'view' => 'startchat',
        ),
      ),

So in this case index.php/examplecom/chat/startchat will look for files first in examplecomtheme theme.

Support project

Developing application takes a lot of time. You can support application by donating. There is no company behind this application and it takes away my free time. Every donation matters and does not matter how small it is!


Paypal, one time donation
Monthly donation
Bitcoin
bc1q6gkl2hcwtn2g26em6axc7jehmn2hd9x8g7nzx9

USDT (Ethereum network)
0x45b92C4aa29EFD3252fD04fcDDe3e6Ef8b399D75