We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 6619 - Allow Static Pages to be optionally assigned to a scheduled conference
Allow Static Pages to be optionally assigned to a scheduled conference
Status: NEW
Product: OCS
Classification: Unclassified
Component: User Interface
All All
: P3 enhancement
Assigned To: PKP Support
Depends on:
  Show dependency treegraph
Reported: 2011-04-26 14:12 PDT by James MacGregor
Modified: 2012-09-24 09:19 PDT (History)
1 user (show)

See Also:
Version Reported In:
Also Affects:


Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2011-04-26 14:12:18 PDT
Currently, any static page created in OCS "belongs" to a conference website, and is displayed within the conference website context. This is fine, except when the static page is specific to a scheduled conference (eg., a custom Keynote Speakers page): since the static page is being displayed within the conference website rather than the scheduled conference context, the Navigation block doesn't display any Conference Information content (such as the link to Call for Papers; presentations; etc.). This is visually noticeable/disruptive when looking at a static page, and also removes valuable information from what may be an important scheduled conference page. 

One solution would be to extend the static pages plugin so that Conference Managers can optionally select a scheduled conference to attach the static page to; in which case, the static page URL would include the scheduled conference's path.