The Open Group : Making Standards Work
About The Open Group The Open Group Forums Certification Consortia Services
HOME   |   SITE MAP   |   SEARCH  

  Become a Member of The Open Group The Open Group Member Area  
Government Programs Events Bookstore & Downloads Newsroom Contact The Open Group
You are here:  Home > Collaboration Services > Plato FAQs > CHANGING SITE PARAMETERS
Services to Consortia
  Plato Web Infrastructure FAQ -- "CHANGING SITE PARAMETERS"    
 

What can I change on a Plato web site,once its been set up ?

This is an example of the administrator's maintenance page for a typical Plato site. The Notes column does not appear on the actual maintenance page but is here to give further explanation.

Item description Notes Items with a blue background cannot be amended by the maintainer
Project ID: A unique identifier, generated by the system. 232
Name: Appears in the header block and the page title (browser title) on every page.
Short form of Name:(max 40 characters) This is used in the Cookie path. Leave blank to use the full name above, truncated if necessary)
Byline: Appears after the Name, in smaller font. anging_params.tpl
Parent site - URL: This is the URL of a parent site, if any. Leave blank if there is no parent site.
Parent site - tag: This is a short name, for use as a link to the parent site. Leave blank if there is no parent site. If this is supplied, the breadcrumbs (You are here...) start with this tag. Otherwise the first entry is the site's home page.
Frontpage text:
This text appears on the home page at ALL levels. Text to appear at a certain level only can be defined in subsequent sections.
Frontpage footer title:
A subheading for the footer on every page.
Frontpage footer:
If omitted, this and the sub-heading above are both omitted - there is no footer.
Website and Domain for mailing These are usually defaulted. www.opengroup.org
opengroup.org
     
Document Root This must match the web server definition of the web site above. /web/top/
One or two levels This will indicate where there are public and protected levels

There are distinct public and protected URLs

Path for top level (public) area This defaults to the corresponding URL above, and is usually the same, unless URL alaises are used. /web/top/member/chapters/australia
Path for all protected area This defaults to the corresponding URL above, and is usually the same, unless URL alaises are used. /web/top/member/chapters/australia/protected
URL for top level This is appended to the Website to form the start URL of the Plato site. http://www.opengroup.org/australia-chapter
URL for all protected areas (gpj_url) If there are more than one level, all protected levels exist here. This is always defined as the "protected" sub-directory of the "public" level. http://www.opengroup.org/australia-chapter/protected
Navbar gif/jpg filename: If supplied, appears at the top of the navigation bar. Must be an appropriate size. /gifs/
Are documents split by category ? The default is No. If YES, the document pane is split into multiple panes by category . No Yes
Can new category/status values be added by anyone ? Default is YES. Setting to NO allows greater control and is useful if the document pane is split into multiple panes by category . Yes No
Are submissions moderated by an editor ? Default is NO. Yes No
Is there a predefined default visibility level for new items? Default is the current level.
Are News and Events hidden from the combined public view? Default is NO. Select YES if you want news and events in the Playdough Event and Newsdesk No Yes

Visibility level 10 - "Project"
Level 10 tag: This is the mandatory level, which can always create/update items.
Frontpage text:
(Project ONLY)
This text appears on the home page, at this level only, after the common text.
This level can create/update items: Defaults to No at levels other than 10. Yes No
Access control lists for Project level This is a set of web-enabled mailing lists. togstaff rp_australia
Project mailing list This is the list displayed on the home page at this level (if the "Count of emails" below is non-zero. rp_australia
Front page layout
The count fields show how many of that item is displayed on the home page. A blank or zero supresses the entry entirely.
Count of news: Count of events: Delete events after: days Hide events after: days in the past
Count of emails: Count of documents: Count of polls:
Count of actions: Count of review documents:

Visibility level 20 - "Forum"
Level 20 tag: This is the first optional level.
Frontpage text:
(Forum level ONLY)
This level can create/update items: Yes No
Access control lists for Forum level togstaff rc_australia
Forum mailing list rc_australia
Front page layout
(Blank to suppress)
Count of news: Count of events:
Count of emails: Count of documents: Count of polls:
Count of actions: Count of review documents:

Visibility level 30 - "Members"

This level is suppressed.

  If initially suppressed, a level can be un-suppressed by the setup team, if you supply the appropriate data to define access control etc.  

Visibility level 40 - "Public"
Level 40 tag:
Frontpage text:
(Public ONLY)
Public mailing list Note that this is suppressed. It can be un-suppressed by the setup team, if you supply the appropriate information. None .
Front page layout
(Blank to suppress)
Count of news: Count of events:
Count of emails: Count of documents: Count of polls:
Count of actions: Count of review documents:

Admin level
Mailing list for Admin facilities togstaff

   
Text for front page headings  
Actions These entries allow the headings on the home page to be modified
Documents
Events
E-Mail
News
Polls
Review documents

Text for individual items
Actions These entries allow the names of items such as 'Document' to be redefined, globally Plural
Singlular
Documents Plural
Singlular
Events Plural
Singlular
Glossary Plural
Singlular
News Plural
Singlular
Polls Plural
Singlular
Review Documents Plural
Singlular

Headings for Glossary Items
Key These entries allow the two or three elements of a Glossary item to be renamed
Text
Details
(Set blank to omit this attribute)

Further information on Plato including troubleshooting tips is available here

August 2006

 

 
 

 

 

 
 

 

 

 
   |   Legal Notices & Terms of Use   |   Privacy Statement   |   Top of Page   Return to Top of Page