Zikula Community

• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: Jun 10, 2006
  • Posts: 28

  Posted: Apr 27, 2006 - 03:22 AM

  Since I currently run Multisites Postnuke, I decided to see if 0.800 can be
  set up much the same way as 0.7xx was, since there's been no mention of
  weither multisites will ever become a 'standard module'.
  
  With 0.800, comes a new config directory structure and changes in the old
  multisites coding to support it.
  
  ===========================================
  config/config.php
  
  
  
  =========================================
  config/whoisit.inc.php
  
  
  ===========================================
  
  config/parameters/test.hostsite/config.php
  (same as installed/created version with the following change)
  
  // ----------------------------------------------------------------------
  // if there is a personal_config.php in the folder where is config.php
  // we add it. (This HAS to be at the end, after all initialization.)
  // ----------------------------------------------------------------------
  include("config/parameters/whoisit.inc.php");
  if (file_exists('config/parameters/'.$serverName.'/personal_config.php')) {
  include('config/parameters/'.$serverName.'/personal_config.php');
  }
  
  ============================================
  
  So, the questions are:
  
  - is "WHERE_IS_PERSO" still valid under 0.800 (doesn't seem so) ?
  - will each host directory still access it's own 'themes' and 'images' dirs ?
  - are the above codings appropriate for 0.80 ?
  - are there any hidden 'gotchas' with multisites ?
  
  I'm testing 0.800 with the multisites coding and it seems to work fine.

  • 
  •  
• markwest
  
  

  • Rank: Team Member
  • Registered: Mar 18, 2002
  • Last visit: Oct 21, 2009
  • Posts: 6606

  Posted: Apr 27, 2006 - 03:30 AM

  There will be a multisites module with .80 but it will be a completely different impelmentation with a management module and support API's. Modules decide what table prefix to use via the API pnDBGetTablePrefix. Different directories for themes and images are a possibility. Themes can be enabled/disabled from the themes admin panel so this might not be a necessity.
  
  This will, however, be one of the last modules that gets worked on although a basic structure is currently in the ValueAddons repository.
  
  -Mark
  
  --
  Visit My homepage and Zikula themes.

  • 
  •  
• **unknown user**
  
  

  • Rank: Softmore
  • Registered: Mar 16, 2002
  • Last visit: Jun 26, 2009
  • Posts: 105

  Posted: Jun 16, 2006 - 07:46 AM

  Looking forward to this module as I think it's feature will be a huge plus.

  • 
  •  
• thesubmitter
  
  

  • Rank: Freshman
  • Registered: Jan 31, 2005
  • Last visit: Oct 21, 2009
  • Posts: 51

  Posted: Oct 08, 2006 - 07:00 PM

  Maybe this should go somewhere else but it'd be VERY cool if the upgrade was made multi site compatible. Upgrading from .75 - .762 was a huge headache just because I had to trace database changes and reincorporate them into the different pntables.php files + databases.

  • 
  •  
• markwest
  
  

  • Rank: Team Member
  • Registered: Mar 18, 2002
  • Last visit: Oct 21, 2009
  • Posts: 6606

  Posted: Oct 08, 2006 - 09:57 PM

  It will be very difficult, if not impossible, to make any new multi-site code compatable with the previous incarnation. This is because the old code is a complete hack - nothing more.
  
  The proposed new solution is a proper module that fully integrates with the PostNuke core making the whole process of setting up multiple sites easier. With the new code you shouldn't need to touch the PHP code at all.
  
  -Mark
  
  --
  Visit My homepage and Zikula themes.

  • 
  •  
•  
•  

Users on-line

• 0 users

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