Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 02 2016 07:14
    shashidharg opened #2
  • Jun 29 2015 19:21

    steverobbins on master

    Adding media template (compare)

  • Jun 29 2015 19:16
    steverobbins closed #1
  • Jun 29 2015 19:16
    steverobbins commented #1
  • Jun 29 2015 19:15

    steverobbins on master

    Adding link to installation ins… (compare)

  • Jun 29 2015 19:14

    steverobbins on master

    Adding vagrant install file (compare)

  • Jun 27 2015 23:13
    assaka commented #1
  • Jun 01 2015 17:02
    steverobbins commented #1
Steve Robbins
@steverobbins
You in Hawaii or something?
Hamid el Abassi
@assaka
no netherlands
;-)
europe
Hamid el Abassi
@assaka
hahaha ok i will keep it in mind and hope to talk to you tomorrow :-)
thanks for your input
Steve Robbins
@steverobbins
Glad to share
Hamid el Abassi
@assaka
i appreciate it
have a good day :smile:
bye
Hamid el Abassi
@assaka
hi
was wondering if caching and indexing is also individual for each client
Steve Robbins
@steverobbins
@assaka Yes. Each client has their own var directory so they will have their own file system caching. They also have their own local.xmls so you can set up separate redis/memcache services.
They also have separate databases, so reindexing one client won't affect the other.
Hamid el Abassi
@assaka
and what about a separate skin and template directory
Steve Robbins
@steverobbins
They will share the same base/default and rwd/default, but you can give each client their own theme like you normally would
Hamid el Abassi
@assaka
in the core_config_options?
Steve Robbins
@steverobbins
Through the admin, System > Config > Design
Hamid el Abassi
@assaka
but then every clients sees all the themes right
i just want a theme called assaka for example and make it exclusively available for assaka
Steve Robbins
@steverobbins
They're on separate DBs so they can be different. But yes, clientA could technically switch to clientB's theme
Hamid el Abassi
@assaka
the same goes for the skin folder then
Steve Robbins
@steverobbins
Yup
Hamid el Abassi
@assaka
that is an issue then because i don't want my changes in my theme be available for others
:-)
Steve Robbins
@steverobbins
You could build a small module that restricts how admins choose their package and theme. Or remove it from the admin group's access
Hamid el Abassi
@assaka
and what about this
   $this->_data['design_dir']  = $this->_data['app_dir'] . DS . 'design' . DS . $this->getClientCode();
Steve Robbins
@steverobbins
Then you would need to duplicate all the base/default and rwd/default files for each client.
Hamid el Abassi
@assaka
yes but that is true
Steve Robbins
@steverobbins
Community modules often have files in base too. This breaks the idea of being able to install a module once and have it work for all
Hamid el Abassi
@assaka
and what if we override the template path
i guess in Layout
wait i will try and find the place
Hamid el Abassi
@assaka
maybe this one
public function setTheme()
in core_model_design_package
Steve Robbins
@steverobbins
What if your client hasn't multiple stores/themes?
Hamid el Abassi
@assaka
then you override the paths to the skin
i am just thinking out loud :-)
i guess for example override the method getSkinUrl
Hamid el Abassi
@assaka
i am going to bed now ;-)
i will keep searching
here is another possible place:
public function getLayoutFilename($file, array $params=array())
{
$params['_type'] = 'layout';
return $this->getFilename($file, $params);
}
public function getTemplateFilename($file, array $params=array())
{
    $params['_type'] = 'template';
    return $this->getFilename($file, $params);
}

public function getLocaleFileName($file, array $params=array())
{
    $params['_type'] = 'locale';
    return $this->getFilename($file, $params);
}
public function getLayoutFilename($file, array $params=array())
{
$params['_type'] = 'layout';
return $this->getFilename($file, $params);
}
Hamid el Abassi
@assaka
could this be a solution?
Steve Robbins
@steverobbins
I'm not really concerned about this issue.
I would just block the client from changing the theme in the admin. That doesn't happen often anyway
Hamid el Abassi
@assaka
maybe that could also be a solution