OTHER SETTINGS

Asset Link Behavior: When the link to the asset is clicked, it can be dis-

played in the Asset Publisher or in the portlet to which the asset belongs, such as the Blogs or Message Boards.

Maximum Items to Display: You can display 1-100 items.

Pagination Type: Select Simple or Regular. Simple shows previous and

next navigation; regular includes a way of selecting the page to which you'd like to navigate.

Exclude Assets with 0 Views: If an asset has not been viewed, exclude it

from the list.

Show Available Locales: Since content can be localized, you can have

different versions of it based on locale. This will show the locales available, enabling the user to view the content in the language of his or her choice.

Enable Conversion To: If you have enabled Liferay Portal's

OpenOffice.org integration, you can allow your users to convert the content to one of several formats, including PDF.

Below these options are the same ones in the Web Content Display port- let: enable print, enable comments, enable ratings, etc.

Show Metadata: Allows you to select from the available metadata types

(see below).

Enable RSS Subscription: This gives users the ability to subscribe to the

content via RSS Feeds.

The Display Settings section of the Asset Publisher has numerous options to help you configure how your content selections are displayed to your users. Even though there are many choices, its easy to go through the options and quickly adjust the ones that apply to you. You'll want to use the Asset Publisher to query for mixed assets in the portal that have relevant informa- tion for your users.

Summary

This chapter has been your guide to Liferay Web Content Management. We've seen how pages are created and managed in Liferay communities and organizations. It is easy to create whole page hierarchies without ever leav- ing your browser. You can import and export pages using LAR archives, and these can also be used to transfer a site from one Liferay Portal server to an- other.

Liferay CMS also includes a powerful staging environment, allowing you to stage content locally on the same server or remotely to another server. And when working on pages, you have the ability to use layouts and nested portlets to design every page to look exactly the way you want it to look. Whether your site is small and static or large and dynamic, Liferay's WCM enables you to easily plan and manage it. With tools such as the WYSIWYG Editor, Structures, and Templates, you can quickly add and edit content. With the Web Content Display and Asset Publisher, you can rapidly select and configure what and how your content is displayed. And by using Liferay's integrated workflow, you can set up custom publishing rules to fit your organization. You will find that managing your site becomes far easier when using Liferay's Web Content Management system.

5.

5. LL

IFERAYIFERAY

C C

OLLABORATIONOLLABORATION

S S

UITEUITE

Liferay Portal ships with a robust suite of collaboration applications which you can use to build communities of users for your site. These applica- tions are best-of-breed applications with all the features you would expect of standalone versions that are outside a portal. The difference with Liferay's collaboration suite, however, is that all of the applications share a common look and feel, security model, and architecture. And they inherit all of the strengths of being a part of the Liferay development platform, so you can use them in combination with Liferay's user management and Content Manage- ment features to build a well-integrated, feature-rich web site.

This chapter will focus on the use of Liferay's collaboration suite. You will learn how to set up and administer:

• Blogs • Calendars • Chat • Mail • Message Boards • Wikis

You will see how all of these features can work together to provide an enhanced experience for your users, as well as giving you the tools to help build a community that keeps coming back.

Scopes

As we learned earlier, roles can be scoped by the portal, by a com- munity, or by an organization. This means that the role only takes effect for the scope in which it resides. For example, a Message Boards Administrator role with complete access to the Message Boards portlet would have different permissions based on the role's scope. If it's a portal role, members have per- mission to administer message boards across the portal. If it's a community role, members have permission to administer message boards only within the community in which they are members of the role. If it's an organization role, members have permission to administer message boards only within the organization in which they are members of the role.

We also use the word scope to refer to the data set of a portlet. When a portlet is added to a page in a community or organization, it is scoped for that community or organization. This means that its data belongs to that com- munity or organization. If the portlet is added to a page in a different com- munity or organization, it will have a completely different data set. This is how the Message Boards portlet can be placed in one community and have one set of categories and threads, and then be placed in a different com- munity and contain a completely different set of categories and threads.

One limitation of this is that by default, you can have only one Message Boards portlet per community or organization. If you have one Message Boards portlet on one page in a community and you add the portlet to anoth- er page in the same community, the second Message Boards portlet will con- tain exactly the same data as the first, and this is because of its scope. It is scoped for that community. Many of Liferay's portlets work this way.

To get around this, some Liferay portlets can have scopes that go beyond just the specific community or organization upon which the portlet has been placed. You can now scope them by page. If you set the scope of a portlet to be the page instead of the whole community or organization, you can add any number of these portlets to different pages, and they will have different sets of data. This allows you to have more than one message board per com- munity or organization if you wish. All portlets, however, default to the “nat- ive” configuration, and have their scopes set to the community or organiza- tion where they are placed.

Unless otherwise noted, all of the portlets in this chapter support scop- ing by either the page or the community / organization to which they be- long. This gives you much more flexibility in how you want to set up your portal. By default, however, the scope remains the same as it always has, and is set to be by the community or organization. If you want to change the scope, it only takes a few simple steps.

2. Select Configuration. 3. Select the Scope tab.

4. Modify the Scope to be the current page. 5. Click Save.

That's all it takes to change the scope for a particular portlet instance. By setting the scope to page, you can add as many of these portlets to a particu- lar community or organization as you want, provided they all are added to different pages.