The Proposals Wiki has been deprecated in favor of creating Feature Requests in JIRA. If you wish to propose a new idea for a feature, visit the Community Ideas Dashboard and read the Feature Requests Wiki page for more information about submitting your proposal.
« FrontPage に戻る

Manage Page Improvements

If there is a feature on this list that is important to you, please leave a comment stating so OR vote (thumbs up) for someone else's comment.  The more votes a given feature has, the more likely it is to be included.

If you think something is missing please feel free to add it in accordance with the guildelines on the front page.

Community Posts are referenced here... Please put comments/voting on this page...

For the use as a WCMs the Manage Pages - Portlet needs an overhaul to fit more complex requirements as described in this thread.

New Features:

  • Changing the display order should be limited to specific roles
  • Restrict editing-/ deleting-action of pages for specific roles (e.g. limit a power user to not be able to edit the first 3 pages of his public pages)
  • Restrict Layout/ Add Child Pages/ Look&Feel/ Import-Export for a specific role
  • Create a right (role?) so that a user can only add new portlets but can't remove pre-defined portlets
  • Create a right that a user can't modify a page completely (e.g. can't remove, add, change position, configuration of a portlet)
  • build the FriendlyURLs hierarchical so that the URL represents the site structure (e.g. page "subpage1" under "menu1" would get a FriendlyURL of /menu1/subpage1)
  • FriendlyURLs should be multi-lingual (mapping of a name to the internal layout id)
  • mulit-lingual FriendlyURLs should be easily indexable for search-robots
  • Pick the point at which "Merge Pages" merges in the public pages
  • Extend the "URL" page concept to include links to another community, group or org.

All these proposals should be inherited dynamically so e.g if a power user has only rights to edit/ change pages in the second navigation layer (e.g. only modify pages under menu1 but not the parent page) this rights should be inherited to all newly created child pages as well.

0 添付ファイル
27569 参照数
平均 (0 投票)
コメント 作成者 日時
One major feature as I see it for management of... Sverker Abrahamsson 2009/09/21 12:18
That's actually mentioned in the Portal... Lisa Simpson 2009/09/25 14:06
please, please, please make a way to change... Bernardo Riveira Faraldo 2009/09/30 10:14
Not every organization or suborganization needs... Tibor Kiss 2009/10/12 5:35
Any plans to add in the ability to turn off a... dennis monsewicz 2010/05/20 11:18
Restricting user to delete pages based on... Ram Manusani 2012/01/04 10:02

One major feature as I see it for management of pages would be to have templates for the pages. A page template would set the layout and base portlets which should be on each page of that type. A user with sufficient rights can edit the portlets from the page either overriding the template or changing settings for all pages with the same portlet. Users without that right can only add and manage portlets on the page instance.
投稿日時:09/09/21 12:18
That's actually mentioned in the Portal Improvments pages... emoticon
Sverker Abrahamssonへのコメント。投稿日時:09/09/25 14:06
please, please, please make a way to change user private/public pages in batch! (1000 users, how in hell do you change their public pages to add/remove portlets???)
投稿日時:09/09/30 10:14
Not every organization or suborganization needs public pages. They would like to work as in intranet, but they access their organizational or community pages through public internet.
Therefore it would be helpful to be able to set permission regarding public pages creation at all.
投稿日時:09/10/12 5:35
Any plans to add in the ability to turn off a page so that it becomes unavailable without having to delete it all together?
投稿日時:10/05/20 11:18
Restricting user to delete pages based on roles.. I would be happy to see this feature.
投稿日時:12/01/04 10:02