Tools allows to supervise the extension installed in the different slave sites and also to synchronize the install/uninstall between the websites and their dependencies.

This can be helpfull when you want to install a specific extension in several website in a single step.
The same is available to un-install extensions.

With this facility it is no more required to re-install the extension in the specific slave sites manually.

Components

Components declared in Joomla Multiple Sites and User Sharing

Components name		Install	Share
Banners	com_banners
Content	com_content
Contact	com_contact
Multi Sites	com_multisites
Multi Sites Menu Item	com_multisitesmenuitem
Multi Sites Articles sharing	com_multisitescontent
News Feeds	com_newsfeeds
Polls	com_poll
Statistics
URLs (weblinks)	com_weblinks
System
Acajoom	com_acajoom
AceSEF	com_acesef
AdsManager	com_adsmanager
Advanced Modules	com_advancedmodules
AEC Subscription Manager	com_acctexp
Agora Forum	com_agora
ALFContact	com_alfcontact
ALinkExchanger	com_alinkexchanger
AlphaContent	com_alphacontent
AlphaUserPoints	com_alphauserpoints
Appointment Booking Pro v1.4x	com_rsappt_pro14
AvReloaded	com_avreloaded
Billets	com_billets
BreezingForms	com_facileforms
camelcitycontent2	com_camelcitycontent2
ccBoard	com_ccboard
Chrono Comments	com_chronocomments
Chrono Forms (Chrono contacts)	com_chronocontact
Civi CRM	com_civicrm
CK Forms	com_ckforms
Communicator	com_communicator
Communicator ACL	com_community_acl
Community Builder	com_comprofiler
Com-Properties	com_properties
Content Templater	com_contenttemplater
Custom Properties	com_customproperties
DOCman	com_docman
DT Menu	com_dtmenu
DT Register	com_dtregister
EventList	com_eventlist
Events	com_events
eXtplorer	com_extplorer		N/A
eWeather	com_eweather
Fabrik	com_fabrik
FAQ for Joomla!	com_faq2win
FireBoard Forum	com_fireboard
Front Page Plus	com_frontpageplus		N/A
Frontpage SlideShow	com_fpslideshow
Gavick PhotoSlide GK2	com_gk2_photoslide
Glossary	com_glossary
HD FLV Player	com_hdflvplayer
Helpdesk	com_helpdesk
Hot Property	com_hotproperty
hwdCommentsFix	com_hwdcommentsfix
hwdPhotoShare	com_hwdphotoshare
hwdRevenueManager	com_hwdrevenuemanager
hwdVideoShare	com_hwdrevenuemanager
IDoBlog	com_idoblog
Ignite Gallery	com_igallery
iJoomla Ad Agency	com_adagency
JCal Pro	com_jcalpro
JCE	com_jce
JComments	com_jcomments
JConnect	com_jconnect
JContentPlus	com_jcontentplus
JEvents MVC	com_jevents
JForms	com_jforms
JFusion	com_jfusion
Jobline	com_jobline
Job Grok Listing	com_jobgroklist
JomComment	com_jomcomment
JomSocial	com_community
Joom!Fish	com_joomfish
JoomDOC	com_joomdoc
JooMap	com_joomap
JoomGallery	com_joomgallery
Joomla Tags	com_tag
JoomSEF	com_sef
Joomla Advanced Message	com_jam
JoomlaComment	com_comment
Joomla Estate Agency	com_jea
joomlaXplorer	com_joomlaxplorer		N/A
Joomla Pack	com_joomlapack
JPortfolio	com_jportfolio
JRE - Cache extended	com_jrecache
J!Research	com_jresearch
JTAG Presentation for Slidshare	com_jtagpresentationforslidshare
Juga	com_juga
Jumi	com_jumi
JXtended Catalog	com_catalog
JXtended Labels	com_labels
K2	com_k2
Knowledgebase	com_kb
Kunena Forum	com_kunena
Leads Capture	com_leadscapture
LyftenBloggie	com_lyftenbloggie
Library Management	com_jlibman
Linkr	com_linkr
Mass content	com_masscontent
Mobile Entertainment	com_mobileentertainment
Mosets Tree	com_mtree
My Blog	com_myblog
NeoRecruit	com_neorecruit
noix ACL	com_noixacl
Pages and Items	com_pi_pages_and_items
Phoca Gallery	com_phocagallery
Phoca Guestbook	com_phocaguestbook
Phoca Maps	com_phocamaps
Phoca Restaurant Menu	com_phocamenu
Phoca SEF	com_phocasef
PollXT	com_pollxt
Power Slide Pro	com_powerslidepro
ProJoom Installer	com_pjinstaller
Query Cache	com_qcache
QuickFAQ	com_quickfaq
RawContent	com_rawcontent
Remository	com_remository
ReReplacer	com_rereplacer
RokCandy	com_rokcandy
RokDownloads	com_rokdownloads
RokModule	com_rokmodule
RokQuickCart	com_rokquickcart
Rquotes	com_rquotes
RSFirewall	com_rsfirewall
RSform!Pro	com_rsform
RSSeo	com_rsseo
Seminar	com_seminar
sh404SEF	com_sh404sef
Shipseeker	com_shipseeker
Smart Flash Header	com_novasfh
SmartSEF	com_smartsef
SmartSite	com_smartsite
SMF 2.x Bridge	com_smf
SOBI 2	com_sobi2
swMenuPro	com_swmenupro
Tag Meta	com_tagmeta
Taxonomy (Zaragoza)	com_taxonomy
uddeIM	com_uddeim
Versions	com_versions
VirtueMart	com_virtuemart
WATicketSystem	com_waticketsystem
WordPress mu	com_wpmu
Xmap	com_xmap
Zoo	com_zoo

Modules

Modules declared in Joomla Multiple Sites and User Sharing

Modules title	name	Install	Share
Custom HTML	mod_custom
Feed Display	mod_feed
Latest News	mod_latest
Login	mod_login
Logged in Users	mod_logged
Admin Menu	mod_menu
Popular Items	mod_popular
Items Stats	mod_stats
User Status	mod_status
Admin Submenu	mod_submenu
Title	mod_title
Acajoom Module	mod_acajoom
AEC Module	mod_acctexp
Active Groups	mod_activegroups
Activity Stream	mod_activitystream
Ad Agency Menu	mod_adagency_menu
Ad Agency Remote	mod_adagency_remote
Ad Agency Zone	mod_adagency_zone
Add to Menu	mod_addtomenu
AdsManager Ads	mod_adsmanager_ads
AdsManager Menu	mod_adsmanager_menu
AdsManager Search	mod_adsmanager_search
General button on control panel	mod_aupadmin
AllVideos Reloaded	mod_avreloaded
Open Support Tickets	mod_billets_open
ImageSlideShow	mod_briaskISS
Cache Cleaner	mod_cachecleaner
Catalog - Categories	mod_catalog_categories
Catalog - Category Cloud	mod_catalog_category_cloud
Catalog - Comparison	mod_catalog_comparison
Catalog - Items (Nodes)	mod_catalog_nodes
Catalog - Rated Items (Nodes)	mod_catalog_rated_nodes
CB Login	mod_cblogin
CB PB Latest	mod_cbpblatest
Core Design Login module	mod_cd_login
CKforms Form Display	mod_ckforms
Communicator Subscribe Module	mod_communicatorsubscribe
Community ACL Menu	mod_commacl_mainmenu
Community ACL Admin Menu	mod_commacl_menu
Dating Search	mod_datingsearch
DT Menu module	mod_dtmenu
DT Register Upcoming Events	mod_dt_upcoming_event
Fabrik form	mod_fabrik_form
Fabrik table	mod_fabrik_table
FLEXIcontent Tag Cloud	mod_flexitagcloud
Frontend-User-Access	mod_frontend_user_access
Frontpage SlideShow	mod_fpslideshow
Gavick News Image I	mod_gk_news_image_1
Gavick News Image III	mod_gk_news_image_3
Gavick News Image VI	mod_gk_news_image_6
googleWeather	mod_googleWeather
HDFLV Player	mod_hdflvplayer
Hello Me	mod_hellome
Hot Property - Agents	mod_hotproperty_agents
Hot Property - Companies	mod_hotproperty_companies
Hot Property - Feed	mod_hotproperty_feed
Hot Property - Manage	mod_hotproperty_manage
Hot Property - Properties	mod_hotproperty_properties
Hot Property - Search	mod_hotproperty_search
Hot Property - Types	mod_hotproperty_types
Video Categories	mod_hwd_vs_categories
Video Search	mod_hwd_vs_search
Videos	mod_hwd_vs_sql_datalists
Video Tags	mod_hwd_vs_sql_tags
hwdVideoShare Template Selector	mod_hwd_vs_template_selector
Video Charts	mod_hwd_vs_xml_datalists
Video Playlist	mod_hwd_vs_xml_vplaylist
JA Content Slider	mod_ja_contentslide
JA Slideshow2	mod_jaslideshow2
JCal Pro Latest Events	mod_jcalpro_latest_J15
JCal Pro Mini-calendar	mod_jcalpro_minical_J15
JCE Admin Control Panel	mod_jcequickicon
JComments Latest	mod_jcomments
JComments Latest Backend	mod_jcomments_latest_backend
JConnect Activity Module	mod_jconnect_activity
JContentPlus	mod_jcontentplus
JContentPlus - Calendar	mod_jcontentplus_calendar
JContentPlus - Latest news	mod_jcontentplus_latestnews
JContentPlus - Most read	mod_jcontentplus_mostread
JContentPlus - Random content	mod_jcontentplus_random_content
JContentPlus - Related Items	mod_jcontentplus_related
JContentPlus - Search	mod_jcontentplus_search
J!Analytics	mod_janalytics
JoomFish-Language Selection	mod_jflanguageselection
JFusion Activity Module	mod_jfusion_activity
JFusion Login Module	mod_jfusion_login
JFusion User Activity Module	mod_jfusion_user_activity
JFusion Whos Online Module	mod_jfusion_whosonline
JobGrok Postings	mod_jobgroklistpostings
JomSocial Connect	mod_jomsocialconnect
JoomDOC Latest Downloads	mod_joomdoc_latestdown
JoomDOC Most Downloaded	mod_joomdoc_mostdown
JoomlaPack Backup Notification Module	mod_jpadmin
Jumi	mod_jumi
JX Woopra	mod_jxwoopra
K2 Comments	mod_k2_comments
K2 Content	mod_k2_content
K2 Login	mod_k2_login
K2 Tools	mod_k2_tools
Latest Comments	mod_chronocomments
Labels - Label Cloud	mod_labels_cloud
Labels - Label List	mod_labels_list
Labels - Related Content	mod_labels_related_content
Labels Manager	mod_labels_manager
Labels Status	mod_labels_status
Latest Discussion	mod_latestdiscussion
Latest group walls	mod_latestgroupwalls
Latest Members	mod_latestmembers
Latest Tags	mod_latestTags
Menu noix	mod_mainmenu_noix
MiniFrontPage Module for J! 15	mod_minifrontpage
Most Popular Tags	mod_mostPopularTags
Most Read Tags	mod_mostReadTags
Myblog Latest Entry	mod_myblog_latest
Myblog Latest Entry with Introtext	mod_myblog_latestintro
Online Users	mod_onlineusers
Photo Comments	mod_photocomments
PollXT Module	mod_pollxt
Power Slide Pro Display Module	mod_powerslidepro
QuickFAQ Module	mod_quickfaq
RawContent Module	mod_rawcontent
Remository multi-purpose module	mod_remositorymulti
Remository Total Downloads	mod_remositorytotal
Remove Mootools 11	mod_removemootools11
RokAjaxSearch	mod_rokajaxsearch
Rokdownloads Latest Downloads	mod_rokdownloads_latest
RokDownloads Most Downloaded	mod_rokdownloads_most_downloaded
Rokdownloads Recently Updated	mod_rokdownloads_recent_updates
RokNavMenu	mod_roknavmenu
RokNewsPager	mod_roknewspager
RokSlideshow	mod_rokslideshow
RokStories	mod_rokstories
RokTabs	mod_roktabs
RokTwittie	mod_roktwittie
Rquotes Module	mod_rquotes
RSFirewall! Cpanel Module	mod_rsfirewall
RSForm! Pro Module	mod_rsform
RSform!Pro Frontend List	mod_rsform_list
Seminar Module	mod_seminar
Session Meter	mod_sestimer
ShipSeeker Module	mod_shipseeker
Simple Mp3 Bar	mod_simplemp3bar
sjsb ssi	mod_smfssi
Smart Flash Header	mod_novasfh
JomSocial Statistics	mod_statistics
Superfish Menu	mod_superfishmenu
swMenuPro Module	mod_swmenupro
Tag Cloud	mod_tagcloud
Top Members	mod_topmembers
Direct Translation	mod_translate
Video Comments	mod_videocomments
VirtueMart Module	mod_virtuemart
VirtueMart All-In-One	mod_virtuemart_allinone
VirtueMart Shopping Cart	mod_virtuemart_cart
VirtueMart Currency Selector	mod_virtuemart_currencies
VirtueMart Featured Products	mod_virtuemart_featureprod
VirtueMart Latest Products	mod_virtuemart_latestprod
VirtueMart Login	mod_virtuemart_login
VirtueMart Manufacturers	mod_virtuemart_manufacturers
VirtueMart Product Categories	mod_product_categories
VirtueMart Product Scroller	mod_productscroller
Email Reminders for ABPro and RBPro	mod_sv_reminders
SMS Reminders for ABPro	mod_sv_reminders_sms
VirtueMart Random Products	mod_virtuemart_randomprod
VirtueMart Search	mod_virtuemart_search
VirtueMart Top Ten Products	mod_virtuemart_topten
Vinaora Visitors Counter	mod_vvisit_counter
Zaragoza Clouds	mod_zonline_cloud
Zoo Item	mod_zooitem
Zoo Menu	mod_zoomenu

Plugins

Plugins declared in Joomla Multiple Sites and User Sharing

Plugins title	name	Install	Share
Authentication - Community ACL	authentication/community_acl
Authentication - GMail	authentication/gmail
Authentication - jfusion	authentication/jfusion
Authentication - OpenID	authentication/openid
Authentication - SJSB	authentication/sjsb_authentication
Billets - Avatar (AMBRA)	billets/avatarambra
Billets - Avatar (CB)	billets/avatarcb
Billets - Avatar (FB)	billets/avatarfb
Billets - Display AMBRA.Subscriptions	billets/ambrasubs
Billets - Emails	billets/emails
Billets - Feedback History	billets/feedbackhistory
Billets - Feedback Statistics	billets/feedbackstats
Billets - For Follow-up	billets/forfollowup
Billets - Frequents	billets/frequents
Billets - Google Translate	billets/googletranslate
Billets - Menu	billets/menu
Billets - Open Tickets	billets/opentickets
Billets - Reply Above Line	billets/replyaboveline
Billets - Respond By Email	system/respondbyemail
Billets - Tools - Check Installation	billets/checkinstallation
Billets - Tools - Purge Old Files	billets/purgeoldfiles
community - Fabrik	community/fabrik
Contacts - Leads Capture	contact/contactsandleadscapture
Content - All Weblinks	content/all_weblinks
Content - AllVideos Reloaded	content/avreloaded
Content - MyBlog Azrul Video Mambot	content/azvideobot
Content - ChronoComments	content/ChronoComments
Content - ChronoContact	content/chronocontact
Content - CKforms Form Display	content/ckforms
Content - DefinitionBot	content/definitionbot
Content - Fabrik	content/fabrik
Content - Code Hightlighter (GeSHi)	content/geshi
Content - googleWeather	content/googleWeather
Content - Email Cloaking	content/emailcloak
Google Maps	content/plugin_googlemap2
Content - JComments	content/jcomments
Content - JIncludes	content/JIncludes
Content - JForm Embedder	content/jforms
Content - JFusion Discussion Bot	content/jfusion
Content - Jom Comment	content/jom_comment_bot
Content - JResearch Persistent Cited Records	content/jresearch_persistent_cited_records
Content - Linkr	content/linkr_content
Content - Load Module	content/loadmodule
Content - RSForm! Pro	content/mosrsform
Content - Optimizer	content/contentoptimizer
Content - Phoca Gallery	content/phocagallery
Content - DT Register EventLink	content/plug_dtregister
pure css tooltip	content/purecsstooltip
Content - RokDownloads Link	content/rokdownload
Content - AlphaUserPoints - Content	content/sysplgaup_content
Content - AlphaUserPoints - Raffle Registration	content/sysplgaup_raffle
Content - AlphaUserPoints - Reader to author	content/sysplgaup_reader2author
Content - Tags	content/tags
Content - Version	content/version
Content - Zaragoza Tags	content/zaragozatags
Editor - JoomlaFCK	editors/fckeditor
Editor Button - AddTags	editors-xtd/addTags
Editor Button - AllVideos Reloaded	editors-xtd/avreloaded
Editor Button - Content Templater	editors-xtd/contenttemplater
Editor Button - Fabrik	editors-xtd/fabrik
Editor Button - Image	editors-xtd/image
Editor Button - JoomDOC Link	editors-xtd/joomdoclink
Editor Button - JResearch Automatic Bibliography Generation	editors-xtd/jresearch_automatic_bibliography_generation
Editor Button - JResearch Automatic Citation	editors-xtd/jresearch_automatic_citation
Editor Button - Linkr	editors-xtd/linkr_button
Editor Button - Modules Anywhere	editors-xtd/modulesanywhere
Editor Button - Pagebreak	editors-xtd/pagebreak
Editor Button - RawContent	editors-xtd/rawcontent
Editor Button - Readmore	editors-xtd/readmore
Editor Button - RokCandy	editors-xtd/rokcandy_button
Editor Button - RokDownload Link	editors-xtd/rokdownload
Button - Versioning	editors-xtd/versioning
User - Joomla!	user/joomla
User - AlphaUserPoints - New user	user/sysplgaup_newregistered
MultiSites bridge for VirtueMart	multisites/virtuemart
AlphaContentSys	system/alphacontent
AlphaContent	content/alphacontent
Authentication - jfusion	authentication/jfusion
User - Jfusion	user/jfusion
Community - Allvideo	community/allvideo
Community - Eventlist	community/eventlist
Community - Feeds	community/feeds
Community - My fireboard updates	community/fireboard
Community - Friend's Location	community/friendslocation
Community - Groups	community/groups
Community - Input Processor	community/input
Community - Invite	community/invite
Community - JomComment	community/jomcomment
Content - Jumi	content/jumi
Community - My kunena updates	community/kunena
Community - Latest Photos	community/latestphoto
Community - My Articles	community/myarticles
Community - MyBlog	community/myblog
Community - MyBlog Toolbar	community/myblogtoolbar
Community - My Contacts	community/mycontacts
Community - My Google Ads	community/mygoogleads
Community - Nice Talk	community/nicetalk
Community - Seyret	community/seyret
Community - System	community/system
Community - My twitter updates	community/twitter
Community - Walls	community/walls
Community - Wordfilter	community/wordfilter
Content - Add Article Activity	content/articleactivity
Content - Author Link	content/authorLink
Content - Contentacroynm	content/contentacroynm
JCalPro Latest Events plugin	content/bot_jcalpro_latest_events
Content - JComments	content/jcomments.content
Content - Jfalternative	content/jfalternative
Content - Labels	content/labels
Content - Pages and Items	content/pages_and_items
Content - JContentPlus	content/jcontentplus
Content - RawContent	content/rawcontent
Content - RokBox	content/rokbox
Editor Button - JComments OFF	editors-xtd/jcommentsoff
Button - JContentPlus	editors-xtd/jcontentplus
Button - Xmap Link	editors-xtd/xmaplink
Hotproperty - Gallery	hotproperty/gallery
JAM - Template - Simple	jamtemplate/simple
JComments - Avatar	jcomments/jcomments.avatar
Joomfish - Missing_translation	joomfish/missing_translation
Mosets - Framework	mosets/framework
RokNavMenu - Boost	roknavmenu/boost
RokNavMenu - Extended Link	roknavmenu/extendedlink
Search - Catalog	search/catalog
Search - Categories	search/categories
Search - Communicator	search/communicator
Search - Fabrik	search/fabrik
Search - Hot Property	search/hotproperty
JCal Pro Search plugin	search/bot_jcalpro_search
Search - JComments	search/jcomments
Search - JComments	search/jcomments.search
Search - JContentPlus Categories	search/jcontentplus_categories
Search - JContentPlus Content	search/jcontentplus
Search - JContentPlus Sections	search/jcontentplus_sections
Search - Jfcategories	search/jfcategories
Search - Jfcontacts	search/jfcontacts
Search - Jfcontent	search/jfcontent
Search - JFjoomDOC	search/jfjoomdoc
Search - JoomDOC	search/joomdoc
Search - Jfnewsfeeds	search/jfnewsfeeds
Search - Jfsections	search/jfsections
Search - JFusion	search/jfusion
Search - JResearch	search/jresearch
Search - RokDownloads	search/rokdownloads
Search - Searchkb	search/searchkb
Search - Sections	search/sections
Search - Jfweblinks	search/jfweblinks
Search - K2	search/k2
Search - Newsfeeds	search/newsfeeds
Search - SearchTags	search/searchTags
Search - Zaragoza Tags	search/zaragozatags
Search - Zoo	search/zoosearch
sh404sef similar urls plugin	sh404sefcore/sh404sefsimilarurls
System - AceSE	system/acesef
System - AdminBar Docker	system/adminbardocker
System - Advanced Modules	system/advancedmodules
System - AEC ErrorHandler	system/aecerrorhandler
System - AEC Routing	system/aecrouting
System - AlphaUserPoints	system/alphauserpoints
System - AllVideos Reloaded	system/avreloaded
System - BetterPreview	system/betterpreview
System - Cache Cleaner	system/cachecleaner
System - Community ACL	system/community_acl
System - Debug	system/debug
System - DT Menu	system/dtmenu.system
System - Fabrik Sheduled Tasks	system/fabrikcron
System - JComments	system/jcomments
System - JCE Utilities	system/jceutilities
System - JComments	system/jcomments.system
JConnect ExApp Connector API	system/jconnect
System - JContentPlus RAW	system/jcontentplus_raw
System - Jfdatabase	system/jfdatabase
System - Jfrouter	system/jfrouter
System - JFusion	system/jfusion
System - Jomsocial Facebook Connect	system/jomsocialconnect
System - Jom Comment Sys	system/jom_commentsys_bot
System - JXtended Libraries	system/jxtended
System - ARTIO JoomSEF	system/joomsef
System - JResearch Load Cited Records	system/jresearch_load_cited_records
System - jSecure Authentication	system/jsecure
System - Jumi Router	system/jumirouter
System - K2_joomfish	system/k2_joomfish
System - K2_user	system/k2_user
System - Labels	system/labels
System - Media Object	system/mediaobject
System - Modules Anywhere	system/modulesanywhere
System - Mootools	system/mootools
MultiSites ID plugin	system/multisitesid
System - noixACL	system/noixacl
System - NoNumber! Elements	system/nonumberelements
System - OptimizeTables	system/optimizetables
System - ReReplacer	system/rereplacer
System - RokBox	system/rokbox
System - RokCandy	system/rokcandy_system
System - RokModuleOrder	system/rokmoduleorder
System - RokGZipper	system/rokgzipper
System - RSFirewall	system/rsfirewall
System - RSForm! Pro	system/rsform
System - RSForm!Pro Mapping	system/rsfpmappings
System - RSForm!Pro Migration	system/rsfpmigration
System - Rsfpgoogle	system/rsfpgoogle
System - Rsfprecaptcha	system/rsfprecaptcha
System - Rsfprsevents	system/rsfprsevents
System - Rsmail_rsformpro_subscription	system/rsmail_rsformpro_subscription
System - Rsseo	system/rsseo
System - SEF	system/sef
System - SJSB sessions fixer	system/sjsb_sessions
Search Replace	system/sr2win
System - sh404sef	system/shsef
System - Tag Meta	system/tagmeta
System - TagSef	system/tagSef
System - Wibiya Toolbar	system/wibiya
System - xAJAX	system/xajax
User - AEC authorization Access	user/aecaccess
User - AEC User	user/aecuser
User Registration Community AC	user/community_acl
User - Jfusion	user/jfusion
User - K2	user/k2
User - Hot Property	user/hotproperty
User - Huru Helpdesk - User Sync	user/huruhelpdesk_user_sync
User - JComments	user/jcomments
User - JConnect User Plugin	user/jconnect
User - noixACL	user/noixacl
User - SJSB	user/sjsb_user
XML-RPC - JContentPlus API	xmlrpc/jcontentplus

Creation of a new 'slave' site consists in creation of the directory where will be store the Joomla configuration.
You also have to provide the list of domain names attached to this site.

It is also possible to create a new website based on a "template websites".
As a website can also be managed by "front-end" user, there is also options to assign a website to a specifc user.

When selecting a "template website", it is also possible to specify a new website title, a new admin password and email.
It is also possible to customise some parameters such as the media folder, the image folder and the template (theme) folder

When selecting a template, JMS display the associated values to allow you change it if they does not correspond to the one you want for the new website.

To create a slave site, three pieces of information are required:

• a site identifier:  The identifier is used as directory name where Joomla will store the new configuration.php file created by the Joomla standard installation.
• a site status: This status indicates whether the websites can be used in production, or should be hidden. This status is also used in conjunction with ‘billable’ websites that can be created from the front-end. In this case, the website status can be synchronised with the order status.
  There is also a ‘payment reference’ field that display the payment reference used when creating a ‘billable’ website from the front-end.
  When the status is not “Confirmed”, the slave site will be considered as not present by JMS. This means that the list of domains will be ignored and navigating to this domain will show the master website.

• a List of domain names: This is the list of domain names that will be routed to the correct slave site.

• owner: this allows you to assign a user to the website. Only the websites having an owner defined can be displayed in the front-end.
• expiration date: this allows you to define a publishing date for the website. When the date is not present, this means it will always be displayed.
  To modify a date, use the button just after the field to select or clear the date.

 In addition to the required site definitions, it is possible to define parameters to duplicate a reference database based on a “template website,” or specific rules.
The idea behind this is to define rules that will be used when replicating the table present in the reference database.
For the moment, the replication is performed in the same database.
The replication consists of copying all the tables having the Joomla prefix of the “source DB” into a new table prefix defined here (manage site) or in a template.
At the same time, it is possible to customise the new database and its associated Joomla configuration file.
Below are the parameters of the Database and/or Joomla configuration file that can be configured.

• a template website: This combo box lists the available templates defined in the “template” menu.
  A template is defined by:
  • Its name (or master DB)
  • A DB name
  • A rule that describes the new “to” DB prefix

• the new DB prefix: when present, or when a template is selected with a table prefix rule, this unlocks the fields that allow you to customize the database and also trigger the creation of the Joomla configuration file.
• the new site title: This allows you to specify a new website title. This replaces the website title that was present in the “from template website” that is replicated to create this new website.
• the new admin email: This allows you to give a new email address to the “admin” user selected in the template. When there is no template (or a template without an “admin user” selected), the first “Super Administrator” user is used to setup a new email address.
• the new admin password: This allows you to define a new administrator password to the “admin user” selected in the template. When there is no template (or a template without an “admin user” selected), the first “Super Administrator” user is assigned the password.
• the new media folder: This allows you to specify a new Joomla Global Configuration, system settings, and media folder settings.
  When specified, the “source” media folder is copied into the new location.
  The source media folder is either the source path defined in the “template website” database, or when there is no database, the path defined in the master website.
• the new image folder: This allows you to specify a new Joomla Global Configuration – system – image folder settings.
  When specified, the “source” image folder is copied into the new location.
  The source image folder is either the source path defined in the “template website” database or when there is no database, the path defined in the master website.
• the new theme folder: This allows you to define a specific “template” or theme front-end directory. When it is specified, a new directory “/template” directory is created and the content will be either a copy (for Windows servers) or a symbolic link (for Unix servers) to all the templates present in the source template directory.
  The source theme folder is either the theme folder from the “template website” (when selected) or from master website.

When a website is already defined, additional information is displayed. The information displayed from the Joomla configuration is:

• DB server name;
• DB name;
• DB table prefix;
• DB login or User name;
• DB password.

Create a new "Website template" allow to define the generic parameters that must be used to replicate the website.

The “website template” is used to define the rules for:

• Which database must be used as reference database to create the new slave site?
  In fact, in the template, you select an existing slave site where all the information, such as the database and the configuration file, will be used and replicated to create the new slave site.
• You also have to define the rules on how to create a unique table prefix
• The rule to create a unique site ID.
• The “generic” domain name must also be specified.
  It is possible to use sub-directory which is computed based on some parameters provided by the user. In particular, it is possible to define a domain name alias.
• When you decide to publish the template to the front-end to allow dynamic slave site creation, it is required to specify which user will be used as administrator.

Other parameters can also be specified to customize the slave site that will be created with the temple. You can also define:

• A deployment folder (this is only available for unix platform [not windows] because it will use Symbolic Links that are not available on windows.
  This field can be used when the hosting provider provides tools like Cpanel, Plesk, or other applications that assign a specific directory for each domain by default. As some customers may encounter difficulties setting up those tools, JMS provides the functionality to deploy a slave site into a specific folder, and it will create symbolic links on the master directory.
  Also see the “folders and files” panel that can be used to customise the deployment.
• A new media folder;
• A new image folder;
• A new theme (template) folder

With the “website template” you can also define some rules on the directory structure that you want for a slave site when it is created.

When working on Unix platform, it is possible to create a “root” website directory that is based on Symbolic Links. The objective of the “Symbolic Links” is to provide the possibility to have a specific disk work space for the slave Website and increase the security when the slave sites are available from the front-end. This give for example the possibility to have specific templates folders deployed for the customers and not share them for all the slave sites.

• ID:  This is the identifier of the template.
• Group:  When defining a menu entry to allow front-end user create slave sites, it is possible to filter the template displayed on a specific group name.
  Enter any text you want to use to group some template into a same menu here. You could use this group field to create a category of templates or whatever.
• Validity:  This parameter gives you the possibility to define a validity duration when you propose a “billable” website service. When present, it may be used to compute a slave site expiration date.
• SKU:  This is a field you can use when you develop a bridge with your eShop or shopping cart system. In the case of “MultiSites for VirtueMart”, we have used this parameter to specify an external reference to a product defined in VirtueMart. This allows you to use the VirtueMart shopping cart system to place an order of a “billable” slave site.
• Title:  This is template title that is displayed to the front-end user that created the slave site.
• Description:  Free text that allows you to describe the template. This text is displayed to the “front-end” when a user selects the template.
• List of domain:  This field is mandatory when you want to show this template into the front-end.
  Define the rule to create the new domain name here.
  You can use multiple keywords in the definition of a domain. See next section for an exhaustive list of keywords available.
  You could define rules like:
  • http://{site_url}/u{user_id}{site_prefix}
  • http://{site_url}/{site_alias}

Where:

• {site_url} : define the current URL of the website
• {user_id} : define the Joomla user identifier
• {site_prefix} : Is a prefix introduced by the front-end user when it creates a slave site.
• {site_alias} : Is an alias introduced by the front-end user when it creates a slave site.

• Template site:  This field is mandatory when you want to show this template into the front-end.
  It is used to select an existing slave site that will be replicated when creating a new slave site.
• To site ID:  This field is mandatory when you want to show this template into the front-end.
  It is used to define the rule for the creation of the slave site identifier.
  You could use for example a rule such as:
  • u{user_id}{site_prefix}
• Admin user:  This field is mandatory when you want to show this template into the front-end.
  It allows you to select the “admin user” that will be available to the front-end user and for which the administrator email and password can be setup during the slave sites creation.
• New DB prefix:  This field is mandatory when you want to show this template into the front-end.
  It is used to define the rule for the creation of the new database table prefix.
  You could use, for example, a rule such as:
  • u{user_id}{site_prefix}
• Deployment folder:  This field is only available for “non Windows” systems – probably Unix platform. When present, it allows to specify where the slave site will be deployed. In this case, it is possible to define Symbolic Links or other rules in the “Files and Folders” panel as described in another section.
• Path to media folder:  This field can be used when you want to use a specific media folder. When specified, it duplicates the media folder associated with the “template website,” and also updates the new database with the new path.
  The new slave site Joomla / Global Configuration / Server panel is changed with the parameter with this new media folder path
• Path to image  folder:  This field can be used when you want to use a specific image folder. When specified, it duplicate the image folder associated to the “template website” and also updates the new database with the new path.
  The new slave site Joomla / Global Configuration / Server panel is changed with the parameter with this new image folder path
• Themes folder:  This field can be used when you want to have a specific themes folder for the slave sites.
  In case of Windows platform, this duplicates the “template site” themes folder.
  On non Windows – probably Unix, this creates Symbolic Links on the “template site” themes folder. We have chosen to create “Symbolic Links” instead of duplication to simplify the maintenance and allow reduce the number of place where template must be updated. This can help some companies that use JMS to propose “themes” to their customers. They could have only one place where to maintain the “themes”.

Keywords available to create generic slave sites

• {user_id} : define the Joomla user identifier.
• {site_id} : This is the site identifier.
• {site_alias} : Is an alias introduced by the front-end user when they create a slave site.
• {root} : Absolute path where is installed the current website
• {multisites} : Absolute path to the multisites directory.
  Equivalent to {root}/multisites
• {site_dir} : Absolute path of the site directory.
  Equivalent to {multisites}/{site_id}
• {rel_site_dir} : Relative path of the site directory.
  Equivalent to multisites/{site_id};
• {site_domain} : Field domain fo the site;
• {site_url} : define the current URL of the website;
• {site_prefix} : Is a prefix introduced by the front-end user when they create a slave site;
• {rnd_psw_6} to {rnd_psw_10} : Random password on a length of 6 to 10 characters;
• {rnd_psw} : Random password on a length of 8 characters

 New Folder and files

The “folder and files” panel is used to customise the new slave site root directory structure.
When working on Unix platform, this is used to create a replication of the master website using “Symbolic Links”. In this case (Unix), this allows a domain to be mapped to another directory than the master website. This can be helpful for plesk or cpanel users, or any other Unix tools that propose by default a specific directory for each domain.
With this tool, it is also possible to decide to copy or create a directory from a tar.gz file.
Some files and folders cannot be customized because they have a specific processing.

This concern:

• the “index.php” and “index2.php” that can not be a link because this may crash website. We create a basic PHP include of the original file present in the master directory for those files.
• The cache folder, the log folder, the tmp folder, the media folder, the image folder, and the themes folder.

The site manager allows to create 'slave' sites that are associated to one or more domain names.

When you want to create a new website, you can either enter some information here, or make reference to a “website template” that contains the rules to create the new website. The definition of a “website template” is given in chapter “Website template” management.”

The "websites templates" define some generic parameters that may be used to compute some specific parameters such as:

• media folder
• image folder
• template (themes) folder
• table prefix

Settings are used to order website quota to allow creating front-end websites using the 'billable' functionalities.

When you want to use the functionality of “billable” front-end websites, it is required to buy quota on www.jms2win.com.
The interface that you can use to buy quota is present in Settings menu.
This menu shows you the current number of “billable” front-end websites that have been created and your current website quota.
The website quota you have already purchased and that is attached to your “jms2win” login. Therefore, you can share your website quota between multiple JMS master installation.
 

Create a new "Website template" allow to define the generic parameters that must be used to replicate the website.

The “website template” is used to define the rules for:

• Which database must be used as reference database to create the new slave site? In fact, in the template, you select an existing slave site where all the information, such as the database and the configuration file, will be used and replicated to create the new slave site.
• You also have to define the rules on how to create a unique table prefix
• The rule to create a unique site ID.
• The “generic” domain name must also be specified.
  It is possible to use sub-directory which is computed based on some parameters provided by the user. In particular, it is possible to define a domain name alias.
• When you decide to publish the template to the front-end to allow dynamic slave site creation, it is required to specify which user will be used as administrator.

Other parameters can also be specified to customize the slave site that will be created with the temple. You can also define:

• A deployment folder (this is only available for unix platform [not windows] because it will use Symbolic Links that are not available on windows.
  This field can be used when the hosting provider provides tools like Cpanel, Plesk, or other applications that assign a specific directory for each domain by default. As some customers may encounter difficulties setting up those tools, JMS provides the functionality to deploy a slave site into a specific folder, and it will create symbolic links on the master directory.
  Also see the “folders and files” panel that can be used to customise the deployment.
• A new media folder;
• A new image folder;
• A new theme (template) folder

With the “website template” you can also define some rules on the directory structure that you want for a slave site when it is created.

When working on Unix platform, it is possible to create a “root” website directory that is based on Symbolic Links. The objective of the “Symbolic Links” is to provide the possibility to have a specific disk work space for the slave Website and increase the security when the slave sites are available from the front-end. This give for example the possibility to have specific templates folders deployed for the customers and not share them for all the slave sites.

• ID:  This is the identifier of the template.
• Group:  When defining a menu entry to allow front-end user create slave sites, it is possible to filter the template displayed on a specific group name.
  Enter any text you want to use to group some template into a same menu here. You could use this group field to create a category of templates or whatever.
• Validity:  This parameter gives you the possibility to define a validity duration when you propose a “billable” website service. When present, it may be used to compute a slave site expiration date.
• SKU:  This is a field you can use when you develop a bridge with your eShop or shopping cart system. In the case of “MultiSites for VirtueMart”, we have used this parameter to specify an external reference to a product defined in VirtueMart. This allows you to use the VirtueMart shopping cart system to place an order of a “billable” slave site.
• Title:  This is template title that is displayed to the front-end user that created the slave site.
• Description:  Free text that allows you to describe the template. This text is displayed to the “front-end” when a user selects the template.
• List of domain:  This field is mandatory when you want to show this template into the front-end.
  Define the rule to create the new domain name here.
  You can use multiple keywords in the definition of a domain. See next section for an exhaustive list of keywords available.
  You could define rules like:
  • http://{site_url}/u{user_id}{site_prefix}
  • http://{site_url}/{site_alias}

Where:

• {site_url} : define the current URL of the website
• {user_id} : define the Joomla user identifier
• {site_prefix} : Is a prefix introduced by the front-end user when it creates a slave site.
• {site_alias} : Is an alias introduced by the front-end user when it creates a slave site.

• Template site:  This field is mandatory when you want to show this template into the front-end.
  It is used to select an existing slave site that will be replicated when creating a new slave site.
• To site ID:  This field is mandatory when you want to show this template into the front-end.
  It is used to define the rule for the creation of the slave site identifier.
  You could use for example a rule such as:
  • u{user_id}{site_prefix}
• Admin user:  This field is mandatory when you want to show this template into the front-end.
  It allows you to select the “admin user” that will be available to the front-end user and for which the administrator email and password can be setup during the slave sites creation.
• New DB prefix:  This field is mandatory when you want to show this template into the front-end.
  It is used to define the rule for the creation of the new database table prefix.
  You could use, for example, a rule such as:
  • u{user_id}{site_prefix}
• Deployment folder:  This field is only available for “non Windows” systems – probably Unix platform. When present, it allows to specify where the slave site will be deployed. In this case, it is possible to define Symbolic Links or other rules in the “Files and Folders” panel as described in another section.
• Path to media folder:  This field can be used when you want to use a specific media folder. When specified, it duplicates the media folder associated with the “template website,” and also updates the new database with the new path.
  The new slave site Joomla / Global Configuration / Server panel is changed with the parameter with this new media folder path
• Path to image  folder:  This field can be used when you want to use a specific image folder. When specified, it duplicate the image folder associated to the “template website” and also updates the new database with the new path.
  The new slave site Joomla / Global Configuration / Server panel is changed with the parameter with this new image folder path
• Themes folder:  This field can be used when you want to have a specific themes folder for the slave sites.
  In case of Windows platform, this duplicates the “template site” themes folder.
  On non Windows – probably Unix, this creates Symbolic Links on the “template site” themes folder. We have chosen to create “Symbolic Links” instead of duplication to simplify the maintenance and allow reduce the number of place where template must be updated. This can help some companies that use JMS to propose “themes” to their customers. They could have only one place where to maintain the “themes”.

Keywords available to create generic slave sites

• {user_id} : define the Joomla user identifier.
• {site_id} : This is the site identifier.
• {site_alias} : Is an alias introduced by the front-end user when they create a slave site.
• {root} : Absolute path where is installed the current website
• {multisites} : Absolute path to the multisites directory.
  Equivalent to {root}/multisites
• {site_dir} : Absolute path of the site directory.
  Equivalent to {multisites}/{site_id}
• {rel_site_dir} : Relative path of the site directory.
  Equivalent to multisites/{site_id}
• {site_domain} : Field domain fo the site
• {site_url} : define the current URL of the website
• {site_prefix} : Is a prefix introduced by the front-end user when they create a slave site.

 New Folder and files

The “folder and files” panel is used to customise the new slave site root directory structure.
When working on Unix platform, this is used to create a replication of the master website using “Symbolic Links”. In this case (Unix), this allows a domain to be mapped to another directory than the master website. This can be helpful for plesk or cpanel users, or any other Unix tools that propose by default a specific directory for each domain.
With this tool, it is also possible to decide to copy or create a directory from a tar.gz file.
Some files and folders cannot be customized because they have a specific processing.

This concern:

• the “index.php” and “index2.php” that can not be a link because this may crash website. We create a basic PHP include of the original file present in the master directory for those files.
• The cache folder, the log folder, the tmp folder, the media folder, the image folder, and the themes folder.

Creation of a new 'slave' site consists in creation of the directory where will be store the Joomla configuration.
You also have to provide the list of domain names attached to this site.

It is also possible to create a new website based on a "template websites".
As a website can also be managed by "front-end" user, there is also options to assign a website to a specifc user.

When selecting a "template website", it is also possible to specify a new website title, a new admin password and email.
It is also possible to customise some parameters such as the media folder, the image folder and the template (theme) folder

When selecting a template, JMS display the associated values to allow you change it if they does not correspond to the one you want for the new website.

To create a slave site, three pieces of information are required:

• a site identifier:  The identifier is used as directory name where Joomla will store the new configuration.php file created by the Joomla standard installation.
• a site status: This status indicates whether the websites can be used in production, or should be hidden. This status is also used in conjunction with ‘billable’ websites that can be created from the front-end. In this case, the website status can be synchronised with the order status.
  There is also a ‘payment reference’ field that display the payment reference used when creating a ‘billable’ website from the front-end.
  When the status is not “Confirmed”, the slave site will be considered as not present by JMS. This means that the list of domains will be ignored and navigating to this domain will show the master website.

• a List of domain names: This is the list of domain names that will be routed to the correct slave site.

• owner: this allows you to assign a user to the website. Only the websites having an owner defined can be displayed in the front-end.
• expiration date: this allows you to define a publishing date for the website. When the date is not present, this means it will always be displayed.
  To modify a date, use the button just after the field to select or clear the date.

 In addition to the required site definitions, it is possible to define parameters to duplicate a reference database based on a “template website,” or specific rules.
The idea behind this is to define rules that will be used when replicating the table present in the reference database.
For the moment, the replication is performed in the same database.
The replication consists of copying all the tables having the Joomla prefix of the “source DB” into a new table prefix defined here (manage site) or in a template.
At the same time, it is possible to customise the new database and its associated Joomla configuration file.
Below are the parameters of the Database and/or Joomla configuration file that can be configured.

• a template website: This combo box lists the available templates defined in the “template” menu.
  A template is defined by:
  • Its name (or master DB)
  • A DB name
  • A rule that describes the new “to” DB prefix

• the new DB prefix: when present, or when a template is selected with a table prefix rule, this unlocks the fields that allow you to customize the database and also trigger the creation of the Joomla configuration file.
• the new site title: This allows you to specify a new website title. This replaces the website title that was present in the “from template website” that is replicated to create this new website.
• the new admin email: This allows you to give a new email address to the “admin” user selected in the template. When there is no template (or a template without an “admin user” selected), the first “Super Administrator” user is used to setup a new email address.
• the new admin password: This allows you to define a new administrator password to the “admin user” selected in the template. When there is no template (or a template without an “admin user” selected), the first “Super Administrator” user is assigned the password.
• the new media folder: This allows you to specify a new Joomla Global Configuration, system settings, and media folder settings.
  When specified, the “source” media folder is copied into the new location.
  The source media folder is either the source path defined in the “template website” database, or when there is no database, the path defined in the master website.
• the new image folder: This allows you to specify a new Joomla Global Configuration – system – image folder settings.
  When specified, the “source” image folder is copied into the new location.
  The source image folder is either the source path defined in the “template website” database or when there is no database, the path defined in the master website.
• the new theme folder: This allows you to define a specific “template” or theme front-end directory. When it is specified, a new directory “/template” directory is created and the content will be either a copy (for Windows servers) or a symbolic link (for Unix servers) to all the templates present in the source template directory.
  The source theme folder is either the theme folder from the “template website” (when selected) or from master website.

When a website is already defined, additional information is displayed. The information displayed from the Joomla configuration is:

• DB server name;
• DB name;
• DB table prefix;
• DB login or User name;
• DB password.

The site manager allows to create 'slave' sites that are associated to one or more domain names.

When you want to create a new website, you can either enter some information here, or make reference to a “website template” that contains the rules to create the new website. The definition of a “website template” is given in chapter “Website template” management.”

The "websites templates" define some generic parameters that may be used to compute some specific parameters such as:

• media folder
• image folder
• template (themes) folder
• table prefix

Deletion of a site consists in removing the directory where the Joomla configuration is stored.

By default, JMS does not delete the table associated to a website.
When the parameter "Delete database content" is set to YES, this delete all tables corresponding to the website prefix as it is defined in the Joomla configuration. So if you share the same DB for multiple websites, this only delete the table corresponding to the website that will be deleted.

This function checks if all the patches are installed.

At the top of the screen, you have two version number.
- The JMS version number;
- The patch definition versoin number. This latest number can be modified when using the "Check for Update" menu.

This check patches provide a report on a list of files that must be patched to work correctly in "Multi Sites" environment.
Beside each files, JMS provides the possible action that will be taken to correct a problem.

When calling "Install", the operation starts to make a backup of the current file into a "administrator/com_multisites/backup" directory and after it applies the patch.
The backup is used by "un-install" to restore the original file.

Website template is a feature that allows you to define generic rules that are used to create new web sites. The rules are very important when you want to use the “front-end” slave sites dynamic creation.

When you propose to your front-end “registered users” the possibility to create slave sites, the “website template” is used to compute the parameter that would normally be introduced by the JMS administrator when using the “site manager”.

The Website template manager allows to create 'websties templates' that will be to create new websites.

The template can either be used by the administrator to create new websites or by the front-end to create websites.

With the "Websites template", you define which slave site must be used as a reference to create another websites.
The "Websites template" can be pre-configured with specific extensions that will avoid to re-install them on all the websites that will be derived from this template.

In addition, it is possible to define some rules on based on some keywords to create new media folder, image folder, template, ...

Joobi JSetup is an extension encrypted with IonCube.

The installation of this extension into a slave site is not easy due to the way this extension is working and due to its encryption.

We have identified a method to re-install it into a slave site.

JMS does allow to re-install the extension into a slave site because JSetup delete its temporary component that is used for the installation.
Therefore JMS refuse to re-isntall it into a slave site because it does not find it in the master website.

The procedure consist in a partial installation of JSetup in the master website to let the JSetup temporary installation component "Joobi Installer" remaining on the master website.
So you install JSetup in the master website and stop when it ask you accept the license and click on "next" button to complete the installation.

Once you have the "Joobi Installer" present in the master website, you can now re-install JSetup in a slave site.

If will ask you again to accept the license and click on the next button.

Once you have installed JSetup in the slave site, the result will be that JSetup will delete on the disk the "joobi installer" that will cause your master website not able to use it anymore. At this moment, you can Uninstall "joobi installer" in the master website and re-install it for another slave site.

When you will try re-isntall again the JSetup in a second slave site, JSetup will detect that some files are already present on the disk and will propose you to un-install them for your current slave site (ie slave no 2). You can un-install them and re-install just after.

When done, you will have a second slave site installed with JSetup.

You have to repeat the master "joobi installer" uninstallation and partial re-installation to allow re-install JSetup in each slave site.

Based on the information provided by one of our customers, here it is the procedure he has communicated to us concerning the configuration of lighthttpd.conf.
The information provided below was not checked and is provided AS IS in hope this will help other customers

 1.- Enabled mod_simple_vhost en your /etc/lighttpd/lighttpd.conf

server.modules  = (
                                "mod_alias",
                                "mod_access",
                                "mod_fastcgi",
                                "mod_simple_vhost",
                                "mod_accesslog" )
2.- Configure a Virtual Host for your Parent Site
     $HTTP["host"]=~ "joomla.puebla.gob.mx"{
                                 server.document-root = "/var/www/lighttpd/puebla"
      }

3.- Configure your Slave Sites using vhost sintaxys for the same Document root
     $HTTP["host"]=~ "joomla.sep.puebla.gob.mx"{
        simple-vhost.server-root = "/var/www/lighttpd"
        simple-vhost.document-root = "puebla"
      }
4.- Restart lighttpd "/etd/init.d/lighttpd restart"

Get a new download ID for the latest version

To receive a new download ID corresponding to the product you have ordered, you have a special "get latest version" menu that is available when you are logged into JMS.
http://www.jms2win.com/get-latest-version

Select (check box) the product for which you want to receive a new download ID and click on "get latest version" button in the top right.

This will resend youan email with the new download ID corresponding to the selected producted.

Here we show in a video how to get the latest version.

How to update Joomla Multi Sites

Normally, you can install JMS over a current one.
Nevertheless, It is advised to "uninstall" the JMS patches with current version of JMS before installing the new JMS version.
When the new JMS version is installed, you can re-install the JMS patches.

Uninstall the JMS patches is also recommanded when you want to update Joomla itself.
This reduce a risk of inconsistency between the patches that are present and the patches that are missing due to the Joomla update (new files installed by Joomla).

When using Joomla Multi Sites on a Windows Platform, it is required that all the domain and sub-domain share the same directory path.

When you define the domain or sub-domain, you must be checked the permission of the directory that you have create allow to be accessible via Internet. For that, the security permission must include the user "Internet Guest Account".

The second element is to share the same directory path than the master website.

For that, in IIS, when you have a look in the property of the domain or sub-domain that you have defined, you have to check the "home directory".
The local path must have a value identical to the one of your master website.
This is the path that JMS display you when you create a new slave site.

You may also have to check the permission of the domain or sub-domain to ensure that you allow to execute PHP script.
Otherwise, only HTML files can be displayed by your domain or sub-domain.

The following procedure is a summary of the full procedure described by one of our customer and present in the PDF "How to configure JMS with IX Web Hosting". This ful document contain screenshot that can be helpfull.

In summary the operation consist to setup a domain as usual in IX WebHosting and retreive the "HTML Directory Name" that must be used by JMS in the deploy diirectory field. This assume that Symbolic Links is allowed in JMS.

• Login in IX Web Hosting
• Select Hosting Products menu / Manage 
• Click on "Domains" present in the section "Main"
• Click on "Add a new domain" button in bottom right
• Enter the domain name
• When done, edit the domain that you have just created to retreive the "HTML Directory Name" that must be used in JMS deploy directory
• Return in "main" section and select "Web Options" to setup your domain to recognize index.php by default
• Enable MultiViews
• Go now in "Tools" section and start "File Manager"
• Remove or rename the index.html

This message may appears when try to access a slave site that you have created into JMS and when you have deployed your website into a specific directory.

In this case, JMS creates several Symbolic Links into the deployed directory and in particular a Symbolic Link on the installation directory.

The problem may comes on the fact that apaches is not configured to follow the symbolic link and therefore that the installation PHP files can not be founded.

When you are using the ".htaccess" provided by Joomla it normally contain a statement like
Options +FollowSymLinks

This statement inform apache to follow the symbolic links.

If you don't use the  ".htaccess", you may have to directly enable the FollowSymLinks into the apache configuration file.

The present GoDaddy domain configuration is based on the configuration of a customer.

Thsi procedure shows you how to configure several domain to share the same directory path than the master domain.

The steps described below are:

• Login to the "Hosting Management" -> "My Hosting Account"
• Manage the Hosting: Select "My Products" menu, option "Hosting"and in "Control Panel" click on the link "Manage Account"
• Go in the "Domain Management".
  - Open the "Setting" panel;
  - Click on icon "Domain Management" to display the list of domain that are currently attached to your account.
• Clik on button "Add Domain" (top right)
• Enter your "domain name" and specify its "folder".
  For Joomla Mulii Sites, put here the same folder than the one used by your master domain.

Login

Manage account

Domain Management

 Add Domain

 Domain name and folder definition

Here below, we present how to configure a domain or a sub-domain on DreamHost web hosting.
The ScreenShots have been provided by a customers that use Joomla Multi Sites.

In summary, the operation consists in:

• Go in "Manage Domain" and click on "Add New Domain / Sub-Domain)
• When you arrive in the "Manage Domains"
  • "Host to domain": Enter the domain or sub-domain you want to host
  • "Specify your web directory": Change the default value by the directory path of your master website.
    For example
    if you have a "domain.com" with directory "/home/username/domain.com".
    When you define a "subdomain.domain.com" must change the path to "/home/username/domain.com".

Here are the screenshots that illustrate this case

Manage Domain

Specify Website Directory

Some customers use Plesk for the administration of their domains.

Most Plesk users know how to create a domain but not necessary how to provide a specific folder for this domain.
In general the users create a domain that has its own folder.

When working on Unix platform, Joomla Multi Sites Version 1.1.x or higher offers you the possibility to deploy a website in a different directory than the master but only if the Symbolic Links is supported by your hosting provider and if you have the permission to create such links between the directories.
In this case, you can specify the directory that is created by Plesk from within Jommla Multi Sites.

If you want to use the same directory as the master website (as we recommend), the procedure below is provided by one of our customers.
We are providing it to help Plesk users in the configuration of their system.
We cannot guarantee the accuracy.

In summary:

• Login into Plesk
• Click on Domain
• Click on the Master domain on which you want to add alias
• Click on "domain alias" 
• Add the different slave sites as an alias domain of your master.
  As the slave sites are defined as an alias (synomym) of the master website, they automatically also use the same path of the master websites. This means that they share the same files and folder of the Joomla Installation.

 Login into plesk

Click on the domain

Click on the "master-domaincom" to enter in the DNS definition of this domain

Click on Add Domain Alias to declare the slave sites as a synonym (alias) of the master website

Joomla Multi Sites (Version 1.0.x and also Version 1.1.x when Symbolic Links is not available) requires that ALL the domains and sub-domains SHARE the same directory (The Joomla Installation - Files and Folders).

The procedure below describes how to check if the Domain Hosting is correctly configured for each of the domains that you want that Joomla Multi Sites manage.

This procedure does NOT require Joomla Multi Sites and can be tested totally independently without anything else than the "hello world" files that you can be download here.

The objective is to install a "hello word" file into the directory of your master domain and check if you can see also this files from the domain that will be used as slave domain.

The hello.zip file contain:

• hello.txt : This file contain "Hello world";
• hello.php : This file is a php script that:
  • display the text "Hello world script";
  • display the current path where it is installed
  • test if the Symbolic Links are available on your environment
    This last point is important when your different domains are located and defined into separated directories.
    In this case, the Symbolic Links could be (conditional) used to create a bridge between the master directory and the slave directory. Perhaps you will encounter permission problem to create the bridge between the master and slave directory.
  • When the slave sites is located into another directory than the master website AND the Symbolic Links is present then this script also allow you to test the creation of the bridge between the Slave Site and the Master Website.
    This allows you to verify if the Joomla Multi Site Symbolic Link feature present in the version 1.1.x can be used.

If you want to see a sample of results of those scripts and therefore the expected results here are some links that you can use.
Master website URL:

• http://master.demo.jms2win.com/hello.txt
• http://master.demo.jms2win.com/hello.php

• http://slave1.demo.jms2win.com/hello.txt
• http://slave1.demo.jms2win.com/hello.php

Notice the both Master and Slave websites display exactly the same "The current path is".
This is because the Domain hosting share the SAME path (share the same joomla installation - share the same files and folders)

"Hello world" Installation and test procedure

• Unzip the hello.zip file into the root of domain you will consider as it will be your master websites.
• Enter the URL http://www.master_domain.com/hello.txt
  You should see the "Hello world" text displayed.
  • If you see the "Hello world" text, you can repeat the operation with the script "hello.php"
    http://www.master_domain.com/hello.php
    This script will display "Hello world script" and additinoal information such as the path where it is installed and if the Symbolic Links are available
• Now that you know the the"hello" files are correctly installed on the master website, you can check the slave site domain hosting configuration
• If the "hello.php" display that "Symbolic Links IS NOT OK", this means that is mandatory to map all the slave sites into the same path than the master website. The path is the one displayed by "hello.php" script.
• If the "hello.php" display that "Symbolic Links is PRESENT", this means that it should be possible to have the slave sites deployed into an external directory. Perhaps you will encounter later problem with permission.

Test that slave sites are mapped in the same directory than the master website

The objectif is to check that you can see the "hello.txt" file from the other slave domain.
To help you, the "hello.php" script display the path that must be used when you setup the slave domain into your Domain Hosting tools.

You can have different scenario:

Case of another domain than the master domain

He this is the case of "www.slave-domain.com" and "www.master-domain.com".
In this case, it is necessary to ensure that both domain (slave and master) use the same full path.

GoDaddy - Domain and Sub-domain setting with the same folder path

This is a summary of the steps to configure GoDaddy:

• Login to the "Hosting Management" -> "My Hosting Account"
• Manage the Hosting: Select "My Products" menu, option "Hosting"and in "Control Panel" click on the link "Manage Account"
• Go in the "Domain Management".
  - Open the "Setting" panel;
  - Click on icon "Domain Management" to display the list of domain that are currently attached to your account.
• Clik on button "Add Domain" (top right)
• Enter your "domain name" and specify its "folder".
  For Joomla Mulii Sites, put here the same folder than the one used by your master domain.

 See also Godaddy Configuration here.

CPanel  - Same path using AddOn Domain

When using CPanel, this can be achieved with AddOn domain where you can specify the path that must be used by the domain. Becarefull if you are using different CPanel account. In this case, it is probable that path will be different as they will be relative to each account. You probably will have to consider using Symbolic Links to create a link between the different accounts.
In summary:

• Go in CPanel and select AddOn domain
• Once in the AddOn Domains, then you will see an interface similar to this:
  Create an AddOn domain
  • New domain: the “slave site” name
  • Document Root: This is the root where the Master Site with the installed component is installed.
    This is also the path that is displayed by JMS after it has created the slave site (see the message in blue in the top)

See also CPanel Configuration here. For screen shot provided by one of our customer: click here

When you have configured your CPanel, you can test the "hello.txt" file and "hello.php" scripts.

Plesk - Create an alias domain on the master domain
When using Plesk tool to configure the Hosting Domains, this can be achieved in defining domain alias on the master domain.
When you define an alias, this automatically use the same path than your master domain as it is defined as a synonym (an alias).
The procedure conisists in:

• Login into Plesk
• Click on Domain
• Click on the master domain to manage it
• Click on "alias domain" to create alias on the master domain
• Create entries for the slaves domain.

To have a more detailled description of this procedure and screen shot, see How to configure Plesk alias domain.

Case of sub-domains using the same domain than the master domain

He this is the case of "slave1.master-domain.com".
In this case, you can generally defined the sub-domain (slave1) as a Hosting Domain alias of your (master-domain.com).
When you define an alias, this automatically use the same path than your master domain as it is defined as a synonym (an alias).

YES, with JMS 1.2.x, it is now possible to share the users between several website.
With this new feature, you can share the standard Joomla users but also a limited number of extension such as:

• VirtueMart users;
• Full VritueMart including the catalog, prices, ...
• Full Community Builder
• Full JomSocial
• Full SOBI2

This is not an exhaustive list.

Joomla multisite version 1.2.x also share the sessions (Single Sign-in). That means for example that you don't have to login again when you go from one website to another website.

In previous version JMS 1.0.x or JMS 1.1.x, it was NOT possible to share the users.

Yes and No.

NO

because JMS only share the files and folders present on the disk. It shares the Joomla Installation.

The each websites used its own content or at least different table prefix when it shares the same database.

This means that articles, news, forum, users or whatever that is stored in the database is totally independent.

YES

because we have developped a special component “Articles Sharing for Joomla Multi Sites” that allow to display the articles, categories, sections from any websites defined with Joomla Multi Sites.
With this extensin, you don't need anymore to replicate or use special extension to synchronise the websites.

This “Articles Sharing” consists in a new menu type “Multi Sites articles sharing” that works like the standard Joomla menu type “Articles” except it adds the possibility to select the websites where the articles, categories, or sections are located.
“Articles Sharing for Joomla Multi Sites” only display the articles.
The menu type implemented are:
-    Multi Sites articles layout;
-    Multi Sites Category Blog Layout;
-    Multi Sites Category List Layout;
-    Multi Sites Front Page Blog Layout;
-    Multi Sites Section Blog Layout;
-    Multi Sites Sections Layout;
It does not allow to edit or submit articles.
“Archives” is not implemented.

The "articles sharing" required with JMS 1.1.5 or higher.

YES, we have redo the test with Joomla 1.5.8 and it is working.
We already have customers that have updated with success their Joomla and now working with the version 1.5.8.

Joomla Multi Sites requires that all the websites (master websites and all the slave sites) share the same Joomla Installation folder.

This mean that you have to setup each domain to be mapped on the same folder.

In the procedure below, we summarize the different steps to folllow.
We also provide you a link to a document provided by one of our customer that explain with screen shot, the different steps he followed to configure CPanel.

In summary:

• Go in CPanel and select AddOn domain
• Once in the AddOn Domains, then you will see an interface similar to this:
  Create an AddOn domain
  • New domain: the “slave site” name
  • Document Root: This is the root where the Master Site with the installed component is installed.
    This is also the path that is displayed by JMS after it has created the slave site (see the message in blue in the top)

Sometimes, you install a slave site and you forget to install the "sample data" or you change your mind after the installation.

The procedure below give you different alternatives to recreate a database with the sample data

Solution 1: Delete the sites and recreate it.

This probably the faster method and that can be done using JMS interface.

Solution 2: Create a second site that use the same DB name and table prefix

This solution consists in creating another slave site in using the same db name and table prefix than the previous one. When it is installed, you can delete the second site.
This solution is slower because it requires to declare the new domain or sub-domain.

Solution 3: Delete the configuration present in the specific site directory.

This solution consists in a manual deletion of the file configuration.php present in the directory multisites/xxx where xxx is the site id.
When you connect again into the slave site, it will request a new installation.
This solution is very fast but require a direct access to the file. (You need an FTP tool, telnet, or a direct access to the file)

Sometime when sharing a large number of websites, it is welcome to have specific folders for Media or Images.
In Joomla global configuration, it is possible to change the default Media and Images folder present in the system panel.

If you want to change those default value for a slave site, it is suggested to point on a directory that contains a duplication of the original Media / Images folder in aim to provide a default set of images. 

Those setting are saved in the database and are specific to a website.

Joomla FTP Layer is a feature introduced in Joomla 1.5 to resolve some permission problem experienced by many Linux/Unix host Users.

Some Hosting provider or Shared hosting servers or simply server may have a high security level that does not autorize to write files or create directories.

With Joomla 1.5 and FTP Layer, it is now possible to use FTP to create directories or simply write files.
To use the FTP Layer, some parameters must be specified such as the URL or IP address, the user name and the password.

The FTP Layer can be setup during the installation or changed in the Global Configuratoin (if you can write it).
If you have already installed Joomla and the FTP Layer is not enable and you can not modify it using the Global configuration, the only solution consists in updating the "configuration.php" file manually. (Probably using an FTP connection or telnet).

Standard Joomla has the possibility to specify a table prefix for all the tables created for a website.
By default, the table prefix is jos_ but can be modified when multiple websites share the same database.

Joomla Multi Sites uses also this feature that consists in using different table prefix when multiple websites wants to share the same database.

The configuration of the table prefix can be specified at the installation as show below or after the installation in using the adminitration global configuration panel.

Some customers have reported a problem during the standard Joomla installation.

If you received an error like:

Undefined index: DBtype in /home/heinoset/muut_html/joomla/installation/installer/models/model.php on line 764

This is due to a problem when installing the sample data or trying to migrate some data from an older joomla database.
To solve this problem, it is recommended to install joomla without the sample data.

This problem is reported with Joomla Multi Sites 1.0.8 and affect also all previous versions.

This issue is solved in Patch Definition versoin 1.0.7 or higher.

Joomla multisites is sensitive to permission as it needs to update some core Joomla files.
When working in Windows environement, the FTP Layer can not be used to solve the permission problem.
An alternative solution consist in giving ALL rights to IIS during the installation of JMS.

The  procedure below describe how to change the permission in Internet Information Service (IIS).
This procedure consists in:

• Add the user everyone to main directory of the website
• Give to the user everyone the permission "WRITE"
• Install Joomla Multi Sites
• Remove the user everyone to restore the IIS normal rights.

Start Administrative tool - Internet Information Service (IIS) manager

Select the permission menu

First select the directory where you want to change the permission. In our case, we have selected the root directory of our website.
Click the right button to see the contextual menu.

Add the "everyone" user

Here the objective is to add the user "everyone" with the "write" permission

First click ADD to add a new user

Enter the "everyone" and check it exists and is correctly spelled.

Set write permission to the "everyone" user

Here the objective is to add the user "everyone" with the "write" permission

NOW YOU CAN INSTALL Joomla Multi Sites.

Don't forget to DELETE the user "EveryOne" when the installation is done.

Keep 'jos_' table prefix for the websites is possible when only one site uses this database.
When one or more slave sites share the same database, the 'jos_' table prefix CAN NOT be used because all the users present in the jos_users are deleted during the installation of a slave site. (Whatever the table prefix chosen during the installation procedure).

Some person wants to install Joomla Multi Sites on an existing websites that is already installed using the 'jos_' table as prefix.
This is possible if ALL the slave sites are installed using one or multiple databases other than the master site database.

In that case, the slave sites will use diffrerent table prefix and never use the 'jos_' table prefix.
As any 'jos_' table is present in the slave database, there is no risk to delete the jos_users present in the slave database.
If you want to keep 'jos_' table prefix for the slave sites, you will have to create as many slave database than there are slave sites.

In conclusion, each time you want to use 'jos_' as table prefix for a website, this website must be alone to use this database.
When you share a same database for multiple website, you can NEVER use 'jos_' table prefix to prevent the jos_users record deletion during the installation of a slave site.

YES, it is possible to see JMS working in a demo environment.
You have a description of this demonstration environment in the document "demo installation".
We invite you to read this document that show you all the steps of a typical installation and will give the URL of the master and slave sites.

In addition, we have live installation.
This www.jms2win.com is already a slave site of our company website.
www.faq2win.com is another slave site that share the same database than www.jms2win.com

NO, a trial version of JMS is not available.
It is not possible to create a special JMS that will not provide all the functionalities or give the full functionalities for a limited period of time.
As this is a component developped in PHP, it is difficult to protect this code. Event with obfuscation.

To help you have a better idea on how JMS is working, you have different video present in the tutorial that illustrate some cases:

• Tutorial Step 0 present the concept of joomla multisite
• Tutorial step 9 present how to create a slave site into a sub-directory of the master website.
• Tutorial step 13 present how to create a slave site from the front-end.
  It uses the "website template" to define the replicate rules that must be applied to create the new slave sites.

For people that want to test this component, we have a "demo" website that can be used on case by case basis to test the installation of specific extensions.
We give the administrator password to the potential customer that have doubt concerning the installation of some extensions.
As there is only one demo environment and we have to reset it each time a new customer want to test his specific extension, this explain why we deliver the login and password for a limited period of time and on case by case basis.

When an error message “Unable to write entry” appears, this means that joomla try to extract files from an archive (tar.gz) file and that the destination is write protected.
This can happen when some files of the list of patches have the "Read only" attribute or when the owner is different than the current one.

The action consist to check the permission and owner of each files present in the patches list.
Starting with Joomla Multi Sites version 1.0.4, additional checks are now performed to report the user on potential permission problem.

Some customers have reported some difficulties when using Joomla Fantastico that protect files and give different owner between joomla standard files and the extensions.

YES, with JMS 1.2.x, it is now possible to share the users between several website.
With this new feature, you can share the standard Joomla users but also a limited number of extension such as:

• VirtueMart users;
• Full VritueMart including the catalog, prices, ...
• Full Community Builder
• Full JomSocial
• Full SOBI2

This is not an exhaustive list.

In JMS 1.0.x or JMS 1.1.x, it was NOT possible share the user.

YES, each web sites can select its own default template.
As each sites use its own database or at least diffrent table prefix, the customisation each sites is independant.
The only exception concern the extension that save their configuration information on disk rather than in database.
Sometime we have to provide a patch for such extensions to let them use separate configuration.

YES, all websites share the same Joomla Installation.
In fact, a new 'multisites' directory is created and store all the 'configuration.php' parameters associeted to each website.
In such maner that we a domain is called, Joomla Multi Site select the appropriate 'conifiguration.php' file to connect the database and proceed with the request.

• RS Events,
• iJoomla SEO

• RS Events,
• RS Form

Joomla 1.6 RC1 compatibility

With the new Joomla 1.6 RC1 it is now possible to remove almost all the patches installed by Jms Multisites and now it is possible to simply adding files to extends Joomla functionlaities or overwrite some of them.

So now, most of the patches consists in adding files to the Joomla 1.6.
Also bundled with Joomla 1.6 RC1 installation directory

New extension compatibilities

It is bundled with the Jms Multisites Patch definition 1.2.51 that adds the definitions for :

• RS Events,
• iJoomla SEO

and also adds the Joomla 1.5 sharing definition for:

• RS Events,
• RS Form

This patches definition now include:

• FLEXIaccess,
• HotelGuide,
• jShareEasy,
• JV-LinkDirectory,
• JV-LinkExchanger

Joomla 1.6 compatibility

This Jms Multi Sites version add the Joomla 1.6 compatibility in the "tool" menu.

Now it is possible to install,share and uninstall joomla 1.6 extension using the "tool" menu.

It is also bundled with Joomla 1.6 beta 15 installation file.

Add customisation

When a large number of slave site needs to be managed, the time to compare the number of tables that are present in the master with all the slave site DB may be high.

So now, it is possible to disable the "refresh icon" to speed-up refresh of the list of slave site present in the manage site.
The parameter is MULTISITES_REFRESH_DISABLED and can be in the "multisites.cfg.php" file.

Here it is a sample value:

Bundled with Patch definition 1.2.50

The new patches defined now include:

• FLEXIaccess,
• HotelGuide,
• jShareEasy,
• JV-LinkDirectory,
• JV-LinkExchanger

This Jms Multisites patches definition add a patch for the All Video download script. The patch computes the "document root" directory based on the deployed directory. The sitePath "document root" directory was not correct when using Symbolic Link.

It also add the JMS Tools (install) definitions for :

• All Video,
• Ninja Content 1.5 (Ninja 1.5, Nooku Framework, Koowa system plugin)

This Jms Multi Sites version is partial compatibility with Joomla 1.6 beta 14.

It also force the alias field in lowercase.

A new keyword {user_email} is added.

Bundled with jms multi site patch definition 1.2.49

Add a patch for the All Video download script to compute the "document root" directory based on the deployed directory. The sitePath "document root" directory is not correct when using Symbolic Link.

Add JMS Tools (install) definitions for :

• JoomlaWorks All Video,
• Ninja Content 1.5 (Ninja 1.5, Nooku Framework, Koowa system plugin)

With Joomla 1.5.22, the jms multisite need an update of an existing patch is used to allow sharing the users sessions between subdomains and subdirectories.

This JMS Multisites patch definition include:

• The fix in the new session management present in Joomla 1.5.22
• Add JMS Tools (install) definitions for :
  - Copyright Current Year,
  - jDownloads,
  - JW Tabs & Slides Module

This Jms Multisite version add the compatibility with Joomla 1.5.22 and also a partial compatibility with Joomla 1.6 beta 13.
It fixes severa screen rendering to work with Joomla 1.6 beta 13.

It is also bundled with jms multi site patch definition 1.2.48 that :

• Include the fix for an existing patch that accept to share the sessions between subdomains or subdirectories and that is now compatible with Joomla 1.5.22.
• Add JMS Tools (install) definitions for :
  - Copyright Current Year,
  - jDownloads,
  - JW Tabs & Slides Module

Jms Multisites Patches definition 1.2.47

• Tiendra

• Tiendra:
• This is a release candidate.
  You may have a limitation when using reference to joomla articles that will not be shared,
• Joomla Estate Agency

Add partial Joomla 1.6 beta 12 compatibility.

Bundled with Jms Multisites Patch definition 1.2.47

• Tiendra

• Tiendra:
• This is a release candidate.
  You may have a limitation when using reference to joomla articles that will not be shared,
• Joomla Estate Agency

• Auctions,
• Restaurant Guide,
• CodeCitation plugin,
• Versioning Workflow

• Auctions,
  Allow a full sharing of the auctions and also the possibility to only share the actions users info
• Restaurant Guide
  with limitation on the Linked Articles that can not be used as the articles are not shared

Bundled with Jms Multisites Patch definition 1.2.46

• Auctions,
• Restaurant Guide,
• CodeCitation plugin,
• Versioning Workflow

• Auctions (full sharing and only user sharing),
• Restaurant Guide
  with limitation on the Linked Articles that can not be used as the articles are not shared

This Jms Multisites patch definition add a patch for Mobile Joomla to allow speciifc configuration for each slave sites.

It also add the JMS Tools (install) definitions for :

• CB Search plugin,
• ai Sobi Search

This JMS Multisites version is partial compatibility with Joomla 1.6 beta 11.

It is also Bundled with Patch definition 1.2.45 that:

• Add patch for Mobile Joomla
• Add JMS Tools (install) definitions for :
  - CB Search plugin,
  - ai Sobi Search

When the SEF is enabled, Joomla does not cleanup all the parameters when they are already present in the menu item id definition.

In this "Article Sharing for JMS" we have added a cleanup of the parameters when they are already present in the menu item id.

So now the "site_id" parameter can be hidden when its value is the same as the menu item definition corresponding to the SEF URL computed based on the alias.

This "Article Sharing for JMS" version 1.0.12 require JMS Multisites 1.2.34 or higher. Otherwise you will get a fatal PHP error due to call to a "multisitesfactory" file that is only available wtih JMS Multisites 1.2.34 or higher.

Also purge all the converted files to remove the older caches. Otherwise you will  get a duplicate "routing" definition error message.

Kunena 1.6 renames its tables names. The new patch defined the new "#__kunena%" tables name as synonym of the old "#__fb%" table names.
If you want to install Kunena 1.6, this patches definition is required.

• Add JMS Tools (install) definitions for :
  - AceSEF plugin,
  - Categories module,
  - Joomdle,
  - JoomFish SEF,
  - Kunena 1.6,
  - Scheduler
• Add Joomla 1.5 sharing definition for:
  - Kunena 1.6,
  - Scheduler
• Add Joomla 1.6 sharing definition for:
  - Kunena 1.6

Partial compatibility with Joomla 1.6 beta 10

We added the Joomla 1.6 beta 10 original file and in particular its new installation directory that is required to create fresh slave sites.

Bundled with Jms Multi Sites Patches definition 1.2.44

Kunena 1.6 renames its tables names. The new patch defined the new "#__kunena%" tables name as synonym of the old "#__fb%" table names.
If you want to install Kunena 1.6, this patches definition is required.

• Add JMS Tools (install) definitions for :
  - AceSEF plugin,
  - Categories module,
  - Joomdle,
  - JoomFish SEF,
  - Kunena 1.6,
  - Scheduler
• Add Joomla 1.5 sharing definition for:
  - Kunena 1.6,
  - Scheduler
• Add Joomla 1.6 sharing definition for:
  - Kunena 1.6

En the SEF is enabled, the routing might be called from any extension.

This fix ensure that the MultisitesContent routing cache file is always stored in the multisites content directory and in the directory from which the multisitescontent is called.

Update the AceSEF patch to be compatible with AceSEF version 1.5.x

The new patch try to identify the signature of AceSEF 1.3.x and 1.5.x to apply the patches that correspond to the appropriate version of AceSEF.

The new patch is required due to refactoring of AceSEF 1.5.x.

This new patch is required for AceSEF 1.5.x or an error may be raised during the installation of the patches and result by the "uninstall" of all patches with the impossibilty to re-install the patches.

Front-end website creation when SEF is enabled.

When the core Joomla SEF is enable, joomla may produce wrong encoding/decoding SEF url.
The problem occurs in the <Form action that are not processed by the Joomla SEF system plugin and that may have different URL than the one compute by the URL present in the menus.

To align the URL between the menu computed by Joomla and the URL present in the front-end website creation forms, we have computed all the form actions to provide the same SEF urls than the menu.

We also modified the internal redirection URL to compute the same menu SEF url and help Joomla decode them with the same algorithm.

The new SEF url compute in the front-end were tested on Joomla 1.5 and 1.6.
It also works with AceSEF, sh404SEF and JoomFish.
Remarks:

• In case of sh404SEF, don't forget to setup the Joomla 1.0.x "live_site" parameter in the configuration.php that is required by sh404SEF to display correctly the stylesheet and other images. See sh404SEF documentation.
• In case of JoomFish and SEF enabled it is recommended to install a fix concerning the HTML <base tag when # anchor is used.
  See http://www.metamodpro.com/software/jfsef for the download of the fix.

Bundled with Patch definition 1.2.43

Update the AceSEF patch to be compatible with AceSEF version 1.5.x

This JMS Multisites Patches definition 1.2.42

• Fix the patch concerning the Global Configuration in Joomla 1.6.
• Add JMS Tools (install) definitions for :
  - Multisites Content Modules (NewsFlash and LatestNews),
  - Multisites Contact,
  - BreezingForms >= 1.7.2 (formelly Facile Forms),
  - Listbingo,
  - Projectfork,
  - RSTickets! Pro,
  - Community Builder Profile Pro + Magic Window,
  - Grid
• Add sharing definition for:
  - Ignite Gallery,
  - Community Builder Profile Pro + Magic Window

Joomla 1.6 beta 9 compatibility.

• installation language conversion to avoid convert leading and trailing quotes in _QQ_
• Partially fix the problem relative to load of new layouts in the back-end
• Fix some patches for Joomla 1.6
• Fix the front-end layout selection for Joomla 1.6

Bundled with Patch definition 1.2.42

• Fix the patch concerning the Global Configuration in Joomla 1.6.
• Add JMS Tools (install) definitions for :
  - Multisites Content Modules (NewsFlash and LatestNews),
  - Multisites Contact,
  - BreezingForms >= 1.7.2 (formelly Facile Forms),
  - Listbingo,
  - Projectfork,
  - RSTickets! Pro,
  - Community Builder Profile Pro + Magic Window,
  - Grid
• Add sharing definition for:
  - Ignite Gallery,
  - Community Builder Profile Pro + Magic Window

Core Enhancement

• Add an internal routine to get the first domain name based on its site id that can be used by mutlisites modules or plugins
• Improve the SEF processing to bypass standard Joomla SEF url error resolution that may affect the website creation from the front-end when SEF is enabled.
  The problem is due to the standard Joomla 1.5 SEF processing that does not resolve correctly the URL to their aliases when parameters are present.This may result by using the default processing instead of the action required. In addition, Joomla does not route the normal URL to their process when "non" SEF redirection url are used and that SEF is enabled.

Bundled with Jms Multisites Patch definition 1.2.41

• Modify the SH404SEF patch to be complient with version 2.0.
  Some patches where moved into other files after they have refactor their code to use MVC.
• Add JMS Tools (install) definitions for :
  - Multisites patches for Mighty,
  - Disqus Comment System for Joomla!,
  - Scribe,
  - SEF Title Prefix and Suffix,
  - some sh404SEF plugins,
  - Simply Links,
  - WysiwygPro3

Partial Joomla 1.6.0 beta 6 compatibility

• Fix a problem to reset the DB error number and that we put in a new Multisites Database adapters
• Fix the submenu display after that Joomla change the behavior in beta 6

Improve the Front-End website creation

• Always check the validity expiration to be able redirect the user to the expired URL when it is present;
• Improve some SEF url when redirecting the user to other multisites actions.
  There is still a know problem when editing a slave site from the list of slave site and when the SEF is enabled.
  In this case, the data are not send by the form to the server. Use a normal input submit button instead of the joomla javascript submitform routine can solve the problem.
• Fix some minor HTML syntax error when editing a Front-end website definition.
  A table row TR were not correctly closed.

Bundled with Jms Multisites Patch definition 1.2.41

• Modify the SH404SEF patch to be complient with version 2.0.
  Some patches where moved into other files after they have refactor their code to use MVC.
• Add JMS Tools (install) definitions for :
  - Multisites patches for Mighty,
  - Disqus Comment System for Joomla!,
  - Scribe,
  - SEF Title Prefix and Suffix,
  - some sh404SEF plugins,
  - Simply Links,
  - WysiwygPro3

JMS multisites patches definition

• Add JMS Tools (install) definitions for :
  - Ninja Content,
  - Simple Caddy,
  - Sourcerer,
  - redEVENT,
  - redFORM,
  - Multisites Search plugins (Multisites Content + Multisites Categories + Multisites Sections);
• Add sharing definition for:
  - Simple Caddy,
  - redEVENT,
  - redFORM.

Joomla 1.6.0 Beta 5 partial compatibility

We still consider this JMS Multisites Version as an alpha version for Joomla 1.6 event if it is stable for Joomla 1.5.
Here are the changes performed to increase the compatibility with Joomla 1.6 beta 5:

• Remove one Joomla 1.6 database patch that is replaced by new MultisitesDatabase API that allow update the protected JDatabase table prefix.
• Improve Joomla 1.6 beta 5 language file conversion to use "_QQ_" for the quote character.
• Modify the "Site" element to autorize multiple selection and also make it compatible with Joomla 1.6 beta 5.
  The "Site" element is used to display the list of JMS Multisites in the extension like "Article Sharing for JMS" or "Multisites Menu Item" and also in "Multisites Search" plugins.
• Modify the "Layout" element to make it compatible with Joomla 1.6 beta 5.
  The "Layout" element is used in the menu when defining a website creation form the front-end and to allow selecting a layout.
• Make the front-end compatible with Joomla 1.6 beta 5.

Other JMS multisites changes

• Fix a bug in JMS tools introduced in 1.2.33 concerning the action to share a component.
  The new possibility to exclude some share tables from a generic list were resulted in the impossibility to share the extension from the JMS Tools.
• Bundled with Joomla 1.5.20 files
• Bundled with Patch definition 1.2.40
  Add JMS Tools (install) definitions for :
  - Ninja Content,
  - Simple Caddy,
  - Sourcerer,
  - redEVENT,
  - redFORM,
  - Multisites Search plugins (MultisitesContent + MultisitesCategories + MultisitesSections);
• Add sharing definition for:
  - Simple Caddy,
  - redEVENT,
  - redFORM.

Bundled with JMS Multisites Patch definition version 1.2.39

Add/modify patches

• Fix the patch for Community Builder 1.2.3 that moved some code into another source.
  If you try install the previous patch on CB 1.2.3, this result by the uninstall of all the patches.
  So it is required to use the JMS Multisites patch definition 1.2.39 or higher with CB 1.2.3.

• Fix the patch for the Sermon Speaker 3.4.1.
  In fact with version 3.4.1, the patch is no more required. Now they save the configuration into the DB.

• Add patch for CssJsCompress.

Add JMS Tools (install) definitions for :

• CssJsCompress,
• Annonces,
• Djf Acl,
• EstateAgent,
• jSecure Authentication,
• MooFAQ
• QuickContent,
• PU Arcade,
• AjaxChat,
• Add also some plugin for JomSocial 1.8.3

Add sharing definition for:

• Annonces,
• JVideo,
• PU Arcade,
• AjaxChat
• JEvent with default excluded.

JMS Multisites version 1.2.33 is now partially compatibility with Joomla 1.6 beta 5.

It is now possible install JMS Multisites on joomla 1.6 beta 5.
We still consider this JMS Multisites version as an alpha version for joomla 1.6 even if this is the same stable code used with joomla 1.5.
The reason is that Joomla has changed plenty API that sometimes require that we implement specific things for joomla 1.6.
For the moment, it is possible :

• to install JMS Multisites on joomla 1.6 beta 5
• to create "fresh" slave site and install extension from the slave site. You can NOT uninstall an extension.
• to replicate existing slave site
• to display the extension installed (JMS Tools). The installation from JMS tools does not work.

Front-end website creation

Add a check when an alias link is already present on the disk with another value.
In this case this report an error and the slave site is not created.

Bundled with JMS Multisites Patch definition version 1.2.39

Add/modify patches

• Fix the patch for Community Builder 1.2.3 that moved some code into another source.
  If you try install the previous patch on CB 1.2.3, this result by the uninstall of all the patches.
  So it is required to use the JMS Multisites patch definition 1.2.39 or higher with CB 1.2.3.

• Add patch for CssJsCompress.

• Fix the patch for the Sermon Speaker 3.4.1.
  In fact with version 3.4.1, the patch is no more required. Now they save the configuration into the DB.

Add JMS Tools (install) definitions for :

• Annonces,
• CssJsCompress,
• Djf Acl,
• EstateAgent,
• jSecure Authentication,
• MooFAQ
• QuickContent,
• PU Arcade,
• AjaxChat,
• Add also some plugin for JomSocial 1.8.3

Add sharing definition for:

• Annonces,
• JVideo,
• PU Arcade,
• AjaxChat
• JEvent with default excluded.

This Jms multisites patch definition adds someJoomla 1.6.0 beta 3 compatibility.

It also add JMS Tools (install) definitions for :

• Joomla Flash Uploader,
• synk,
• Akeeba Backup,
• Blue Flame Forms For Joomla,
• Extended Menu,
• JB FAQ, JB Slideshow,
• JEV Location,
• Spec Images,
• JVideo!,
• JoomLoc
  Remark:
  Incompatibility with RocketThemes RokDownloadBundle version 1.0.1
  The new RokDownload component is packaged into a RokDownloadBundle that install the RokDownload component as a core joomla component.
  JMS Multisites does not provide interface to install "core component" that normally are the one present when installing the joomla cms.

• JoomLoc

Joomla 1.6 beta 3 partial compatibility

This Jms multisites version contain several update to provide a partial compatibility with Joomla 1.6 beta 3.
Between the Joomla 1.6 alpha and beta a lot of refactory were performed by Joomla and that have broken some Joomla 1.5 / 1.6 compatibility.

This version reduce the compatibility problem between Joomla 1.5 and 1.6 but some Jms Multisites functionality are still not working with Joomla 1.6. We know that the JMS tools and the layout are still not working and that the new Joomla 1.6 submenu processing provide identical text for all the submenu. In addition, the language files processing were totally rewritten by Joomla and now it is no more allowed to enter html tags into the language file.
All these issues are not yet solved.
This is the reason why we still consider this Jms Multisites version as a alpha version event if the JMS kernel is not modified and is identical between Joomla 1.5 and 1.6.

Jms Multisites bug fixes

• When updating an existing slave site, check if it was located in a flat structure to force this format in case where the letter tree is enabled. This allow to resave the configuration using the same format.
• Fix the delete of a slave site when using the letter tree to avoid delete recursivelly all slave site under a give letter tree entry.
• Fix the computation of the list of slave sites when this processed is called from a website where the then "multisites" directory is a link.
• Fix a bug introduced when implementing the "letter tree" concerning the filtering of slave site and that affect the list of slave site that can be displayed in the front-end.
• Remove a warning in the "installation" to hide a warning on set_time_limit() when the call to this function not allowed by a server that have the safe mode enabled.
• Add the possibility to UpdateStatus on All the websites.

Bundled with Jms Multisites Patch definition version 1.2.38

• Add Joomla 1.6.0 beta 2 compatibility.
• Add JMS Tools (install) definitions for :
  - Joomla Flash Uploader, synk, Akeeba Backup, Blue Flame Forms For Joomla, Extended Menu, JB FAQ, JB Slideshow, JEV Location, Spec Images, JVideo!, JoomLoc
  Remark:
  Incompatibility with RocketThemes RokDownloadBundle version 1.0.1
  The new RokDownload component is packaged into a RokDownloadBundle that install the RokDownload component as a core joomla component.
  JMS Multisites does not provide interface to install "core component" that normally are the one present when installing the joomla cms.µ
• Add sharing definition for:
  - JoomLoc

This Jms Multisites patch definition 1.2.37 fix a bug introduced in a patch modified in 1.2.36 when replacing an existing patch by a new one.

When the patch is not correctly installed, it may happen that the access to the standard Joomla "manage template" is corrupted.

The new fix recover the last backup file and reapply the patch correctly on it.

Modify several patches to take in account the new Jms multisites "letter tree" directory structure.

Add also the Jms Multisites patch definitions for :

• JS Testimonials

Modify the patch concerning the "administrator/index.php" file to take in account the new letter tree directory structure used when there are a lot of slave sites.

JMS multiistes patch definitions for :

• QContact,
• Multisites Affiliate (coming soon),
• GroupJive,
• JoomLeague,
• myApi,
• OSE Webmail
• Seo Links,
• Update Manager,
• VM Emails Manager,
• WebmapPlus

Also add the sharing definition for:

• GroupJive

This Jms Mulitisites version :

• Adds the keyword {site_id_letters} and give now the possibility to call a plugin process additional keywords.
• Gives the possibility to create a special plugin to define external DBSharing and DBTable definitions that will complete the JMS Multisites one.
• Speed up the patches loading to avoid reading it several time.

Is bundled with Joomla 1.5.18 original files (installation)

Contain the Jms Multisites Patch Definition 1.2.36 that:

• Modify several existing patches to take in account the new letter tree directory structure

• Add JMS Tools (install) definitions for :
  - JS Testimonials

New low level directory structure

We have introduced a new way to save the Jms Multisites slave site description on the disk to allow record a lot of slave sites definition and reduce the impact on the OS performance. Now, it is possible to store the Jms Multisites slave sites configuration using a set of directories using a tree of letters to speedup the files access.

By default this new low level directory structure is not enabled and is a parameter present in the "multisites.cfg.php" files.

This new way to save the multisites configuration file may be usefull when proposing a huge number of websites creation from the front-end. (ie. 10,000 slave sites an perhaps 1 million or more slave sites). This functionality is already live with a customer who expect more than 1 million slave sites and that use a multisites affiliate program that we have developed.

To speedup the processing when the Top Level Domain definition is not required, we also add a parameter in the "multisites.cfg.php" file to disable the computation required to identify pattern like "co.uk", "co.au", "co.za", ...

When installing an update of Jms Multisites, we know detect if a "multisites.cfg.php" is already present to avoid replacing it.
The "mutlisites.cfg.php" file is only created when not present and based based on the "multisites.cfg-dist.php" file.

New multisites.cfg.php parameters are:

• MULTISITES_TLD_PARSING   Give the possibility to disable the Top Level Domain (TLD) computation to speedup the Multisites processing.
  When none of the slave sites contain domain with TLD composed of several words like co.uk co.za, co.au, ...
• MULTISITES_LETTER_TREE   Use a letter tree to have the Multisites "Slave site" configuration and therefore reduce the number of files/folders at each level.
  When not defined, it is assume this is false and use the default flat directory structure.

Plugin and contributor customization.

Possibility to create contributor patches

Call plugin function to give the opportunity to contributor write specific patches that could be appended to Jms Multisites.
A free plugin for the YooThemes WARP framework is provide with the contribution of Brett Bruce that written the patches and that we encapsulated into this new plugin facility.
- Add the possibility to add contributors patches. Call plugin multisites to defined the patches.
Possibility to implement the functions coreFunctions2Backup() & files2Path().

Keyword customisation

We have added in standard new keywords:

• {user_login}
• {user_name}
• {site_id_letters}

It also exists now the possibility to implement plugins to process additional customer specific keywords.

Front-end new facilities

• Add the possibilty to create a slave site with an anonymous users (not logged).
• dd the possibility to redirect to a specific URL in case of error.
• Add new "OnBeforeSave" Multisites plugin functions that is called before saving a front-end slave sites.
• Add possibility to flag all the field in the front-end edit.
• Add a new function in the Util API to allow rebuild the Multistes master index.

Fix PHP 5.3 Compatibility

- Fix warning message reported by some "preg_split" and introduced when adding the PHP 5.3 compatibility

Bundled with Jms Multisites Patch Definition 1.2.35.

Modify several existing patches to take in account the new letter tree directory structure used when there are a lot of slave sites.

• Add JMS Tools (install) definitions for :
  - QContact,
  - Multisites Affiliate (coming soon),
  - GroupJive,
  - JoomLeague,
  - myApi,
  - OSE Webmail
  - Seo Links, £
  - Update Manager,
  - VM Emails Manager,
  - WebmapPlus

• Add sharing definition for:
  - GroupJive

This Jms multisites version is just bundled with the latest joomla 1.5.17 original files that are published by joomla to fix some bug introduced in the joomla 1.5.16.

It is recommended that you update Jms multisites to a version 1.2.27 or higher before the installation of a joomla 1.5.16 or higher.

Jms multisites Patch Definition 1.2.33.

Includes the fix concerning the bug introduced by Joomla in the version 1.5.16 and that does not allow to login.
The behavior is that Joomla 1.5.16 loop on the login when called from a "localhost". Some side effect were also noticed in live site.
The fix consists in applying the patches that Joomla has published with (medium/high level) and that will be probably released in Joomla 1.5.17.
With Jms multisites, you can already benefit of this fix that had the sided effect to prevent any login.
See the joomla bug tracker published at
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=20221

Also add several cross-check on joomla patches installed to improve consistency when joomla restore or replace existing files that remove Jms multisites patches.
A side effect detected is an infinite loop when installing the joomla patches from version 1.5.15 to 1.5.16.
The infinite loop is due to the fact that the installation directory exists (restored by JMS) and when updating 1.5.15 to 1.5.16 some Jms multisites patches are partially removed that create a "ping pong" between the administrator/index.php and the installation/index.php

Add JMS Tools (install) definitions for :

• Job Grok Application,
• Kuneri Mobile Joomla,
• ninjaXplorer
• Quick Jump Extended,
• WEBO Site SpeedUp,
• aiContactSafe,
• Rentalot

Add sharing definition for:

• Job Grok Application

This Jms Multi Sites version add:

• Bundled with the Joomla 1.5.16 installation and orginal files.
• the PHP 5.3 compatibility and remove all the deprecated functions like ereg and split.
• a fix on a minor problem when computing the "TLD" (Top Level Domain) when shared extension and that may happon on some PHP environment.

Bundled with Patch Definition 1.2.33.

That include the fix concerning the bug introduced by Joomla in the version 1.5.16 and that does not allow to login.
The behavior is that Joomla 1.5.16 loop on the login when called from a "localhost". Some side effect were also noticed in live site.
The fix consists in applying the patches that Joomla has published with (medium/high level) and that will be probably released in Joomla 1.5.17.
With Jms multisites, you can already benefit of this fix that had the sided effect to prevent any login.
See the joomla bug tracker published at
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=20221

Also add several cross-check on joomla patches installed to improve consistency when joomla restore or replace existing files that remove Jms multisites patches.
A side effect detected is an infinite loop when installing the joomla patches from version 1.5.15 to 1.5.16.
The infinite loop is due to the fact that the installation directory exists (restored by JMS) and when updating 1.5.15 to 1.5.16 some Jms multisites patches are partially removed that create a "ping pong" between the administrator/index.php and the installation/index.php

Add JMS Tools (install) definitions for :

• Job Grok Application,
• Kuneri Mobile Joomla,
• ninjaXplorer
• Quick Jump Extended,
• WEBO Site SpeedUp,
• aiContactSafe,
• Rentalot

Add sharing definition for:

• Job Grok Application

We strongly recommend to install the Jms multisites patches 1.2.33 or better install Jms multisites 1.2.27 before installing the Joomla 1.5.16.

To get the latest version, see the FAQ http://www.jms2win.com/faq#sec-122

• Joomla Quiz,
• JUMultithumb,
• wbAdvert

Add sharing definition for:

• Joomla Quiz.
  Not tested and not guarantee. Just a candidate for sharing.
• Shipseeker.
  Any problem relative to this extension must be reported to the author of this extension that provide the support

• the possibility to create website from the front-end that share a whole website.
• a new API function to retreive the website information when used in plugin or external component or modules.
• a fix on a fatal error that occurs when the joomla JFile class is not declared.
  Add the "import" of this declaration.

Bundled with Patch Definition 1.2.32.

Add JMS Tools (install) definitions for :

• Joomla Quiz,
• JUMultithumb,
• wbAdvert

Add sharing definition for:

• Joomla Quiz.
  Not tested and not guarantee. Just a candidate for sharing.
• Shipseeker.
  Any problem relative to this extension must be reported to the author of this extension that provide the support

In Jms Multisites for joomla 1.2.23, we have introduced the generation of a new "secret" value when creating the slave site.

This has a side effect on the "Single Sign-In" that result by different session_id for each domain and therefore disabled the Single Sign-In.

In this version, we have removed the generation of the "secret" value to keep the same value than the master.

Therefore the JReviews extension that expect to have different secret values to have specific configuration now share the configuration.

If you have created slave site with Jms Multisite 1.2.23, you can update all the slave site configuration.php file manually to copy the value in the secret present in the master configuration.php file. The objective is to use the same secret value for all the slave sites.

This Jms multisites patch definition add the install definitions for :

• Add and fix DOCMan 1.5.4 modules and plugins,
• ARI Quiz,
• Vodes,
• Jobs

Add sharing definition for:

• Vodes,
• Jobs

Enhance the sharing table parsing when creating a website.

When creating a slave site, it may happen that some existing view contain additional statement like "select ..... from `dbname`.`tablename` WITH CASCADED CHECK OPTION'.
To retreive the retreiving "FROM table name" present in a statement we add a cross-check
that select the word that is preceded with the word "from".

Bundled with Patch Definition 1.2.31.

Add JMS Tools (install) definitions for :

• Add and fix DOCMan 1.5.4 modules and plugins,
• ARI Quiz,
• Vodes,
• Jobs

Add sharing definition for:

• Vodes,
• Jobs

This JMS multisite Patch Definition 1.2.30 adds the "install" definitions for :

• DOCMan 1.5.4 modules and plugins,
• Mutlisites Meta tag,
• CEdit,
• Click Head,
• JReviews & S2Framework. Nnot guaranteed as it uses ioncube and tests were not possible
  You must consider this definition as experimental and require new fresh slave site or slave site built with JMS 1.2.23 kernel only.
  It is not possible to use JReviews on slave sites created with prior JMS version 1.2.23. The update is not working.
  With existing slave site, you may have to modify the secret word manually in the configuration.php file.

Enhance the Jms Multisites interface with "New Like" and search filtering

"New like" button is used when you want to create a new slave site or template like an existing definition.
In this case, you select the slave site or template definition that you want to use when creating the "new" definition.
This maybe helpfull when creating a Jms templates where you have to setup the "folders and files" actions.
You can re-use an existing definition that is moreless identical to the one that you want to create.

Also add in the "manage site" a search filter that allow quickly find a specific slave site definition.
This maybe usefull when you have several hundred of websites.
The search is applied on fields:

• Site ID
• Site name
• Domains
• DB host name
• DB name
• DB Prefix

Remove the older compatibility with Joomla < 1.5.10.

To reduce the packaging distribution we have removed from Jms multisite for joomla all the original files of joomla 1.5.9 and lower that was present in the distribution in case where the backup failed and it was not possible to retreive the original definition.
So there is no more "rescue" algorithm available in Jms to restore original joomla files in case of "uninstall" or patches installation failure.
We have considered that older Joomla < 1.5.10 was not very secured and decided to stop the distribution of rescue patches.
This does not mean that Jms will not work with older version of joomla. There is no more rescue (or backup) guarantee with older joomla versions. Up to the user perform backup themselve in case of failure with older joomla < 1.5.10.

Specific cache management

Joomla uses the "secret" field present in the "configuration.php" file to compute a cache file name.
In case where you replicate an existing website, Jms multisite uses the existing "configuration.php" file to create the new "configuration.php" file for the specific slave site.
This patch consists in generating a new "secret" value with the objective to have specific "cache" files event when sharing the same cache directory. This may be usefull for "Windows" platform that can not use the Symbolic Link and may not be able to have a specific "cache" directory.
Some extension like "JReviews" also use the "secret" value to store their own configuration file on the disk.

Bundled with Jms Multi Sites Patch Definition 1.2.30 and 1.2.29

Patch definition 1.2.30
Add JMS Tools (install) definitions for :

• DOCMan 1.5.4 modules and plugins,
• Mutlisites Meta tag,
• CEdit,
• Click Head,
• JReviews & S2Framework. Nnot guaranteed as it uses ioncube and tests were not possible
  You must consider this definition as experimental and require new fresh slave site or slave site built with JMS 1.2.23 kernel only.
  It is not possible to use JReviews on slave sites created with prior JMS version 1.2.23. The update is not working.
  With existing slave site, you may have to modify the secret word manually in the configuration.php file.

Patch Definition 1.2.29:

Add fix for the YooThemes "yoo_vox" to allow reading the appropriate multisites "params_xxxx.ini" file.
Add JMS Tools (install) definitions for :

• Frontpage SlideShow 2.x
• Ninjaboard,
• Ozio Gallery 2,
• Picasa Slideshow,
• Slimbox,
• Very Simple Image Gallery Plugin,
• YOOTools:
  YOOaccordion, YOOcarousel, YOOdrawer, YOOeffects, YOOgallery, YOOholidays, YOOiecheck, YOOlogin, YOOmaps, YOOscroller, YOOsearch, YOOslider, YOOsnapshots, YOOtooltip, YOOtoppanel, YOOtweet