Fork me on GitHub

Upgrading to zikula...what about multisite use?  Bottom

Go to page 1 - 2 [+1]:

  • Why is it that zikula has no support for multisite use as did the postnuke 7 series. How do I upgrade without this functionality am I alone icon_confused or has a work around not requiring a distinct install for each subdomain been thought of... What was the reasoning for not considering multisite users.
  • I'm also eagerly awaiting multisite support on Zikula. The good news is that multisite support has not been forgotten - it's currently on the roadmap for 2.0.0.

    If you search for "multisite" in the forums, you'll find a tutorial that explains how to share selected DB tables between different installations. This means you still need to install Zikula for each site, but at least you can share tables (e.g. users).

    Note to devs: if you need any multisite beta testers (once you start working on 2.0.0), I'd be happy to help icon_smile

    stefaan
  • I have read the tutorial mentioned...Regrettably it is a cumbersome workaround not suitable for multi multi subdomains... Talk about throwing out the baby with the bathwater icon_confused . Users are being urged to upgrade but when the current release does not meet your requirements how can one? I know ...wait... hmm...support for postnuke 7 x ends in June 09 I believe.
  • Perhaps you can rsync the different installation except the pntables.php files ? it could be a workaround while waiting for the 2.0.

    http://translate.google.com/translate?u=http%3A%2F%2Fwww.postnuke-france.org%2Fmodule-Forum-viewtopic-topic-919.html&hl=en&ie=UTF8&sl=fr&tl=en



    edited by: mumuri, Jan 21, 2009 - 02:16 AM
  • mumuri

    Perhaps you can rsync the different installation except the pntables.php files ? it could be a workaround while waiting for the 2.0.

    http://translate.google.com/translate?u=http%3A%2F%2Fwww.postnuke-france.org%2Fmodule-Forum-viewtopic-topic-919.html&hl=en&ie=UTF8&sl=fr&tl=enedited by: mumuri, Jan 21, 2009 - 02:16 AM


    As I said "I have read the tutorial mentioned...Regrettably it is a cumbersome workaround not suitable for multi multi subdomains... " But thanks for reading anyway.
  • The problem here is that MultiSites on the 0.7 series was hacky
    and Mark West planned a MultiSites feature for Zikula too much different, this may lead that there's no upgrade path for 0.7x multisites anyways...
    recently, i have done a hack in the /config/config.php to detect different subdomains and set different tables, but i'm not sure if other 0.7x multisites stuff can be ported to Zikula in a "clean" way
    icon_confused

    --
    - Mateo T. -
    Mis principios... son mis fines
  • nestormateo

    The problem here is that MultiSites on the 0.7 series was hacky
    and Mark West planned a MultiSites feature for Zikula too much different, this may lead that there's no upgrade path for 0.7x multisites anyways...
    recently, i have done a hack in the /config/config.php to detect different subdomains and set different tables, but i'm not sure if other 0.7x multisites stuff can be ported to Zikula in a "clean" way
    icon_confused


    Please document the hack as it may serve to assist others. Whilst I agree that it may have been hackie (is that a word? hmm) at least it existed....
  • Nestormateo

    I would as would perhaps uthers be interested in how you managed to detect the different subdomains any chance of you documenting what you did?

    Also is there any reason why the 7x multisite philosophy would not work with Zikula.

    regards
  • Well,
    as said, the "philosophy" was a 'dirty' hack, not as clean as Zikula used to do stuff or support new features, that's why WHEREISPERSO was removed of the system (and i think there are some parts that still needs cleaning)

    Currently, i don't remember too much of the possibilities of the 0.764 MultiSites setup; i remember that there can be different themes per Site, share some tables and others not, and other things i guess, but what i did in Zikula was to change the working database only, with a simple check in the config.php:

    Code

    if (stristr(pnGetHost(), 'subdomainName')) {
    $PNConfig['DBInfo']['default']['dbname']      = 'database1';
    } else {
    $PNConfig['DBInfo']['default']['dbname']      = 'database2';
    }
    This was a solution just for 2 subdomains, sharing the same files, and can be done with a switch for many sites, but you'll be able to switch prefixes, databases, users or passwords, but no features like the old ones. To share some tables and not others, it's needed to modify the core and the treatment of the module's tables, to separate themes per site too, that's why it's hard to have the same features over Zikula.

    But if it's not too much trouble,
    can you list the MutilSites features that you need to upgrade to Zikula?

    --
    - Mateo T. -
    Mis principios... son mis fines
  • Thanks Mateo for your reply the features I am looking for in multi-sites are:

    Separate Themes, modules, permissions, blocks.

    Using the 7x multi-site I could dictate which tables where to be used by modifying the pntable file in each subdomain.


    regards
  • Well, real hard then.
    Now the pntables are modular and it's not that easy as override the "central" pntables.php values like in the 0.764 :-s Mark West thought more about this topic and MultiSites was initially planned for Zikula 1.5, but Mark got pretty busy and now... have to ask him about it, he's THE man in this matter icon_wink

    Greetings

    --
    - Mateo T. -
    Mis principios... son mis fines
  • I'll volunteer some thoughts as well. I'm also used to the .764 system, but I'll just list some use cases here. Perhaps there's another way to implement them, better aligned with the Zikula architecture:

    Users:
    - same login/pwd across subdomains
    - nice-to-have: single login (session valid across all subdomains)
    - all system mails and communication should originate from the "correct/current" subdomain (or, if not possible, from a selected "master" domain. (You don't want a user resetting his password on RedSite to get mails from BlueSite - some users might only visit/know RedSite).

    Permissions
    - same groups across sites (you can simply define different groups, e.g. BlueAdmins and RedAdmins)
    - separate permissions (you don't want RedAdmins to have admin access on BlueSite)

    Modules
    - same modules & tables across subdomains (for example, News from different sites can be stored in a single table, using Categories to filter according to site)
    - nice-to-have: option to use separate, per-site tables for some modules

    Blocks
    - Shared blocks ok (you can just create Red & Blue blocks)
    - separate block placement!

    Theme
    - separate themes

    "WhereAmI"
    - some kind of intelligent mechanism to determine the site used by the visitor, available in modules and module templates - one silly example: use red font when on RedSite

    I'd be happy to help testing/debugging (highly motivated to get this feature - but too much architecture related to code myself)

    stefaan
  • A more useful/less trivial example for the "WhereAmI" functionality - filter news based on site. e.g. on RedSite, only show news from category "RedNews".

    stefaan
  • Mateo, can you please take a look at the PM I sent you? I'm trying to do some multisite according to your idea, but I'd need some more guidelines. Thanks.
  • Will this be supported in the upcoming version?

    --
    Bollywood Babes

Go to page 1 - 2 [+1]:

This list is based on users active over the last 60 minutes.