MultiSite BO Management

One platform, one Back Office, multiple web sites

Section(s): back office, data sharing, plugin, standard plugin

This plugin responsible for handling multisite functionalities in the BO :

• Restraign access to medias for which user was granted
• Filtering contents by media
• Drawing the media drop down
• Ability to have different roles for a single user regarding the current contributed media
• Additional FCKEditor configuring options Media access filters can be disabled for specific role ids

Plugin parameters

disableForRoles : Coma separated list of role ids for which the media filtering is not activated.

This parameter should contain at least one role id, otherwise no role will be able to grant users on newly created media. Usually, the role id 4 (Technical administrator) is allowed to view all medias. Another role (23, Functional Administrator in WMS standard) is also allowed to view all medias. This role is dediacated to creating and managing medias, langs, users.

Entry points

• /bov2/init/initialize_before.jspz :
  • Initialize generic bases
  • Initialize media base_edit_list
  • Initialize active media
  • initialize content objects specific to activeMedia (list of objects known as Content Objects in the current media)
• /bov2/init/initializeBaseWhereExtended_before.jspz : initializes template bases, activeObject base_list, other objects base_edit_list and base_search_list.
• /bov2/init/initialize_after.jspz : user initializations
• /bov2/menu/menuContributeur_before.jspz : uses currentrole surfer property as surfer_current_roleid
• /bov2/dataedit/properties/html/html_fckeditor_after.jspz : Allows multisite specific initializations for setting FCK config files

Description

List of medias for which the user has been granted is obtained thanks to the usermedia collection on user. This object also gives the role of a user on a specific media. This filter can be disabled for a list of roles by specifying their ids in the disableForRoles parameter.

The generic initialized bases are :

• base_list_object_media_filtered : add constraint : media child or child multiple property contains surfer media property or is 0 (shared content)
• base_list_object_mediagroup_filtered : add constraint : mediagroup child property is equal to surfer mediagroup property
• base_list_object_shared_filtered : add constraint : sharegroup property is equal to 1
• base_list_object_mediashare_filtered : combination of base_list_object_mediagroup_filtered and base_list_object_shared_filtered

media base_edit_list base (base_edit_list_media) is initialized using usermedia collection.

Contents Objects are initialized by using (in order of priority) :

1. the coma separated list of objectnames in contentobjects media property
2. the coma separated list of objectnames in contentobjects media's model property
3. objects marked as content objects in their structure configuration will be used

Template base is set to list only templates associated to current model activeObject base is set to filter on current media or group shared other objects base is set to filter on current media or group shared

User is initialized to have the activeMedia ID as a surfer property and role for active media as surfer currentrole property

General FCK Editor configuration can easily be specialised for a sitemodel or a media using objects media and sitemodel. Nevertheless, you might want to have a specific behavior (for a field in a model). This can be done easily by defining custom files for overriding csseditorarea (by setting fckEditorareacss request attribute) fcktemplate (by setting fckTemplateLink request attribute) fckstyle (by setting fckStyleLink request attribute) toolbar (by setting fieldCustomToolbar request attribute)

FCKEditor exemples

For all HTML properties named foo in sitemodel bar, we want specific css xml styles and xml templates files. We will create in /SAN/_ _perso/bov2/dataedit/properties/bar_foo_fckstyle.jsp which will only contain one line to set in the fckStyleLink request attribute the SAN based path to the fckstyle.xml file to use.

/SAN/__perso/bov2/dataedit/properties/bar_foo_fcktemplate.jsp which will only contain one line to set in the fckTemplateLink request attribute the SAN based path to the fcktemplate.xml file to use.

/SAN/__perso/bov2/dataedit/properties/bar_foo_fckeditorareacss.jsp which will only contain one line to set in the fckEditorareacss request attribute the SAN based path to the fckeditorstyle.css file to use.

/SAN/__perso/bov2/dataedit/properties/bar_foo_fcktoolbar.jsp which will only contain one line to set in the fieldCustomToolbar request attribute the name of the toolbar to use in this context.

Of course, if you want to limit these specificities to one object named foobar, those 4 JSPs would be in the /SAN/__perso/objects/foobar/bov2/dataedit/properties/ directory.