|Oracle® Fusion Middleware User's Guide for Oracle Portal
11g Release 1 (11.1.1)
Part Number E10235-02
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 does not affect privileges granted to users before it was run, only after. Once 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 Oracle Fusion Middleware Administrator's Guide for Oracle Portal.
It's likely that a default template has been selected at the page group level. You can find this control on the Configure tab of page group properties, under Page Defaults. If Use Default Properties When Creating Page is selected, and a default template is selected under Default Template, that template is automatically applied to every new page, unless it is explicitly de-selected when you create or edit the page.
One way around this is to take every step of the page creation wizard, rather than clicking Finish once you've entered the essentials. When you get to the template selection step, de-select the default template by choosing Do not use a template.
Another way around this, once the page is created, is to edit page properties, and select Do not use a template on the Template tab of page properties.
You may not have sufficient privileges to add content. You must have at least the page (or tab) privilege Manage Content or Manage Items with Approval on the page or on the tab that contains the region.
If the page is based on a Portal Template, and the template region is locked, no one can add content to the region, unless they do so through a WebDAV client. If the default item region in a template is set not to allow users to add content, this setting is ignored by WebDAV when adding content to pages that are based on the template.
To unlock a region:
Open the page or Portal Template in Edit mode, and edit the region.
Select Enable Users To Included Content In This Region.
Click OK to save your changes and return to the page or Portal Template.
For a template to be available for use, the option Make available for use in this page group must be selected. You will find this option on the Main tab of template properties.
For a template to display in either of these locations, you must, at minimum, have the View privilege on the template. Ask the template owner or the page group or portal administrator for access privileges on the template.
If the page is based on a template, it could be that the template designer or did not select Enable Pages To Use Different Style. When this option is not selected for the template, the Style tab does not display when users personalize the page.
It could also be that the page group property, Allow Privileged Users To Personalize Page Style is not selected. For more information, see Section 4.3.2, "Controlling Who Can Apply a Different Style to a Page".
If the page is based on a template, the template designer my have prevented users from setting their own page access by clearing the option Enable Pages to Have Different Access. Clearing this option prevents users from choosing different access control settings when they create or edit pages that are based on a template. Such pages always use the template access control settings.
This option is available on the Access tab of template properties.
It could be that the template is being used on a translated page and that objects on that template have not been translated. When a template that was created in the portal's default language is applied to a translated page, only the template objects that have also been translated display on the template.
Add translations for all template content. For more information, see Chapter 19, "Translating Portal Content".
If the template is a Portal Template for items, it could be that the item placeholder is in a non-active state, such as Draft, Pending, Rejected, Hidden, Expired, and so on. The item placeholder must be active for it, or the content that replaces it, can be displayed on the rendered page.
If you're sure you have the right page group selected in the Page Groups portlet, click the Browse link next to the HTML Templates heading under Layout & Appearances. This takes you to the Portal Navigator, specifically to the HTML Templates node under the page group selected in the Page Groups portlet Work In drop-down list. Scroll through the listed templates.
If you still cannot find your template, enter the template name in the Portal Navigator Find field and click Go. The HTML template you are looking for should be listed in the search results.
When a page or template is cached at the system level, and Approvals and Notifications are enabled for the page group, unpublished items, such as Draft, Pending, Rejected, and Deleted Rejected items, do not display as expected. For this reason, do not cache approval-enabled pages or templates at the system level. For more information, see Chapter 21, "Improving Page Performance".
For information on which items are accessible in what states, see Section 17.9.3, "Item URL Security".
This involves the source page and a Portal Template. When you edit or personalize the Page portlet to display selected regions, and a change is made to the portlet's source page regarding the template—either a template is added or detached or a template region equivalent to a region selected for display on the portlet is deleted—the portlet cannot resolve such changes with its Display Selected Regions setting. The result is that the portlet displays without content—or blank. To resolve this situation, re-edit or personalize the portlet's region display settings.
To personalize a portlet, in page View mode click the Personalize link in the portlet header. For more information on restricting the display of regions in a page portlet, see Section 8.5.3, "Selecting Page Portlet Regions for Display".
An exception to this is when the page skin uses a class generated by an Oracle Portal style. For example, you can place an Oracle Portal style element class in the <body> HTML tag:
<BODY style="margin:0px" class="Bodyid2siteid0">. Should you change the style declaratively, through the Oracle Portal user interface, the change is reflected as well in the template that references the style class.
This enables you to change the Background Color of all pages that use the page skin through the declarative style. (For more information on Oracle Portal style element classes, see Chapter 11, "Using Portal Style Element Classes in HTML Templates and CSSs".)
You can delete tabs and regions from Portal Templates only if you have sufficient privileges to delete tab content on the pages that are based on the template.