Conferences may be co-located with a bigger conference (parent-subconference relation). The default behaviour of the web application is to stick to the view context of the visitor’s landing page. E.g. when entering the SPLASH 2014 website and browsing to the subconference track Onward!’14, the track page of Onward!’14 keeps the styling, domain name and top menu items (attending, calls, program, committees, …) from SPLASH (=view-context).

However, some subconferences are not tightly bound to its parent conference, and therefore one may want to view the subconference’s webpages in their own context. (this is the case for ( Curry On ) which is co-located with ECOOP 2015)

My idea is to have a override view context-setting for each sub-conference. Default is *empty*, forcing default behaviour. When setting this to its own conference edition, all pages will load in the subconference’s view context, no matter what context one entered the web page.

Submitted by Elmer van Chastelet on 19 January 2015 at 13:37

On 19 January 2015 at 13:38 Elmer van Chastelet tagged 0.9.1

On 19 January 2015 at 16:54 Elmer van Chastelet closed this issue.

On 19 January 2015 at 22:12 Craig Anslow commented:

yeah I agree keeping the context for Onward! makes sense.

However, for SLE, GPCE, and DLS this needs to change.

DLS also needs a web site as well, please see other issue :-)

Can you please look into this for us?


Log in to post comments