The media object

The cornerstone of WEDIA XMS, multi site and cross media capacities of WEDIA WMS

Section(s): configuration, data model, data sharing, learning

An unavoidable object

In the WMS context, the media object represents a website. Each instace media of media represents one website. All of content objects should have a media child property on the media object.

In a media, we define the langs in which the website can be contributed and separately the langs in which it is currently available in Front Office. This allows you to add a new language to an existing online site, translating or contributing in that language, and when ready activate the new language.

A media also defines information about the layout and site model it should use for rendering in FO. It might carry on some site information as the logo, the favicon, ...

In the WMS context, thanks to the WMS_BO_multisite plugin, the media property will automatically be used as a filter depending on user's current media context (selected media on the top right combo box). As well, thanks to WMS_FO_multisite plugin, contents are filtered on the current website.

On the front office, the media is determined primarily thanks to the server name of the request. This allows us to get an information about the media without having extra query parameters.

Structure overview

Here is a screen shot of today media structure. Let's comment all of its properties:

Media structure fields description

id	name	description
1	id	WEDIA XMS engine native property
2	created	WEDIA XMS engine native property
3	modified	WEDIA XMS engine native property
4	owner	WEDIA XMS engine native property
5	parent	WEDIA XMS engine native property
6	child	WEDIA XMS engine native property
7	status	WEDIA XMS engine native property
8	name	Name of the media - name of the site. This is to give a functional name to a site.
9	activated	WEDIA XMS engine native property
10	group	child on mediagroup. Allows to regroup media in groups. Usefull for sharing content.
11	defaultlang	Child on lang. Lang to be used as a default when cannot be determined from the URL
12	langs	Child multi on lang. Langs in which contents can be created inside a media. Notice that a user will only be able to contribute in languages that are common between the media langs and the user contribution langs.
13	activatedlangs	Child multi on lang. Langs available in FO.
14	separator_0	graphical separator
15	model	child on sitemodel. Which sitemodel must be used for rendering this site.
16	logo	the image logo of the site
17	separator_1	domain separator
18	domainnames	/ separated list of domains that the site should respond to (eg: /www.mysite.com/mysite.com/)
19	googleaccount	google account to use for google analytics (requires the WMS_FO_GoogleAnalytics plugin)
20	domainlang	A collection of domainlang for specializing domains for a specific lang (eg: uk.mysite.com, fr.mysite.com... ) will be discussed further.
21	basepath	base path for resources (overrides the site model datas)
22	css	css file to use in fo for screen (overrudes the site model one)
23	cssprint	css file to use in fo for print(overrudes the site model one)
24	contentobjects	objects known to be contentobjects in that site (if empty all structured marked as contentobject will be used). Usefull for drawing the quick create box on BO dashboard (coma separated list)
25	separator_2	goodies separator
26	fckstyle	xml file for fck authorized styles. This will override the sitemodel configuration. This property can be overriden for each property.
27	fcktemplate	xml file for fck authorized templates This will override the sitemodel configuration. This property can be overriden for each property.
28	fosearchableobjects	Objects that can be searched in FO (coma separated list)
29	fckeditorareacss	css to use in fckeditor. Overrides the sitemodel default one
30	excludetemplates	templates to be excluded from the model
31	favicon	favicon to use.