Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle Portal
11g Release 1 (11.1.1)

Part Number E10235-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4.7 Troubleshooting Page Groups

The Create Page Group link does not display in the Page Groups portlet.

For the Create Page Group link to display in the Page Groups portlet, you must have at least the global privilege Create on the object type All Page Groups.

Global privileges are assigned through the Portal User Profile portlet. In typical installations, you'll find this portlet on the Portal sub-tab of the Administer tab in the Portal Builder. In the Portal User Profile portlet, enter the user's name, click Edit, and click the Privileges tab to bring it forward.

I do not see a page group listed in the Page Groups portlet. I know the page group exists.

To see a page group in the Page Groups portlet, you must have at minimum the View privilege on the page group, or you must have the global privilege View on the object type All Page Groups.

The View page group privilege is assigned on the page group properties Access tab. The View global privilege is assigned through the Portal User Profile portlet. To get these privileges, speak to your page group or portal administrator.

The Browse Users icon does not display on the Access tab.

The portal administrator may have run the script serlacl.sql to enforce role-based security. Role-based security limits privilege grantees to groups. Individual users cannot be granted privileges. The script affects privileges that are granted after it is run. Privileges granted before the script is run remain intact. This means that users who had privileges before the script was run continue to have their individually assigned privileges. After this script is run, the Browse Users icon does not display next to the Grantee field on Access tabs. Additionally, the Privileges tab does not display on the Edit Portal User Profile page.

For more information, see the Oracle Fusion Middleware Administrator's Guide for Oracle Portal.

Many users are able to view my page group, though only a handful have View privileges on it.

Users who do not have the page group privilege View on a page group they can nonetheless see probably have a global privilege that gives them access. The most restricted of the global privileges—the View global privilege on the object type All Page Groups—enables users to see your page group (and everyone else's).

The way to limit the list of users who can view your page group is to limit the users who are granted this global privilege (as well as the list of users who have the View privilege explicitly on your page group).

I've removed some users' access privileges to a page group, but they're still able to access it.

They are probably viewing a cached version of pages in the page group. To ensure that users who no longer have access privileges on a page group do not continue to access some version of it, once you change their access privileges, go to the page group's Access tab, and click the Clear Cache link. This will clear the cache of any lingering versions of the page and allow you to more easily see the results of your changes to access settings.

I've given users the Manage Style privilege on one or more pages in my page group, but they're unable to choose a different page style.

Check the Main tab of the page group's properties. One or both of the following options should be selected:

The person who created the page group has left our department. This person is listed as the contact at the bottom of every page in our department's page group. How do I change this?

You may be in luck! If your former contact used a Portal Smart Link to add contact information to each page, all you must do is change the page group contact information. You'll find this on the Main tab of page group properties. Change the entry for the Contact E-mail field.

If your previous contact added the contact information using, for example, a text item, you must edit each affected text item. If this is the case, we suggest that you use this opportunity to add a Portal Smart Link instead. For more information, see Section 4.3.3.1, "Specifying the Page Group Contact E-mail Address".

When I create a new sub-page, its property settings are nothing like those of its parent page. How do I get sub-pages to have similar settings to their parent pages?

You can set up inheritance rules to inherit property settings from a page's parent page or its page group. A page's parent page is the page immediately preceding it in the page hierarchy. A page's page group is the page group under which the page was created.

You can specify inheritance rules that govern a page group on the Configure tab of page group properties.

On the Configure tab, click the Edit link under the Page Defaults section. Under the Page Defaults heading on the resulting page, choose from:

For more information, see Section 4.5.2, "Specifying Inheritance Rules for Newly Created Pages".

Differentiating between page group and page properties can require a little thought when a sub-page is created directly off the page group's root page. The settings for the page group's root page properties are not the same thing as the settings for the page group's properties.

Page group properties are those that display when you click the Configure link next to a page group selected in the Page Groups portlet's Work In drop-down list. They're also displayed when you click the Properties link next to Page Group in the toolbar at the top of a page that is in Edit mode.

Page properties are those that display when you click the Properties link next to Page in the toolbar at the top of a page that is in Edit mode.

Some properties are common to both sets; however, those properties that are set at the page group level are potentially more widely applied than those set at the page level.

I selected a default style for my page group, but new pages are not using that style.

Check your inheritance rules. It could be that they are set up to inherit defaults from the parent page rather than the page group.

To set up inheritance rules so that newly created pages inherit defaults from the page group, go to the Configure tab of page group properties, click the Edit link under Page Defaults, and select the radio button for Use Default Properties When Creating Page. The next time you create a page in this page group, its style default will be the same as the one set at the page group level.

I have selected a default template/page skin for my page group, but it is not the default selection for newly created pages in my page group.

Check your inheritance rules. It could be that they are set up to inherit defaults from the parent page rather than the page group.

To set up inheritance rules so that newly created pages inherit defaults from the page group, go to the Configure tab of page group properties, click the Edit link under Page Defaults, and select the radio button for Use Default Properties When Creating Page. The next time you create a page in this page group, it will use the default template/page skin you have chosen for the page group.

I cannot remove the page skin that is applied to my page.

A page's template options are located on the Template tab of the page's properties. On this tab, make sure that the option Do not use a template is selected.

If your page is based on a Portal Template, it could be that the template incorporates a page skin. When a page is based on a Portal Template, it inherits the template's HTML page skin (if one is applied). On the pages that use the Portal Template, the template's HTML page skin cannot be removed or overridden by another HTML page skin. This means when you are editing a page based on a Portal Template, you do not have the option to choose an HTML page skin. If you want to make your own page skin selection, you must first detach the page from the Portal Template.

Alternatively, if you have privileges on the template, and you're sure all other users of this template can live with the change, you can edit the template and remove its HTML page skin.

New pages are not inheriting their access privileges from the page group as I have specified.

It is likely the pages in question are based on a Portal Template. Look at the Access tab for the template's properties. If the option Enable Pages To Have Different Access is not selected, the access rules specified for the template are being enforced on all pages using the template. In such cases, the Access tab does not display for pages that use the template.

For the template, select the Enable Pages … option if you want pages that are based on the template to be able to have access rules that differ from those defined through the template.

The Access link in the page toolbar on pages that use the template may not display immediately. In this case, go to pages that use the template, and enter Edit mode. Click the Page: Properties link in the toolbar at the top of the page. Click the Access tab to bring it forward. Make your changes to access settings. Be sure to click the Clear Cache link after you have made your changes. This will remove any legacy privileges from the cache, enabling newly-added users and groups to have access, and preventing newly-removed users and groups from gaining access.

You may also detach the page from the template to regain control of access settings at the page level. Doing this means any additional changes made to the template will not cascade to the page from which it was detached.

I do not see the Move to Shared link next to my template, page, or navigation page in the Portal Navigator.

Of all the page group objects, only these three cannot be moved to the Shared Objects page group. You must create them anew within the Shared Objects page group in order to share them across page groups.

For more information, see Section 4.6, "Sharing Objects Across Page Groups".

You can share pages across page groups by publishing them as portlets. Pages published as portlets are available to all page groups through the Portlet Repository. For more information, see Section 8.5, "Placing One Page Onto Another".

I have exposed my portal in both Spanish and English. I have added a file item to the Spanish version. It is also displaying in the English version.

Assuming that your portal's default language is English, any content you provide to translated versions of your portal also displays in the default language version (in this case, the English version). Add an English translation of the file to the English version, and that will be displayed in lieu of the Spanish version you uploaded first.

Once an English translation of the document is added to the portal (in the same location), users of the English version of the portal, will see only the English version of the document.

For more information, see Section 19.3.1, "Adding a Translated Item".