Hi all,
Daniela, you'll have to do a full-text search across your OCS installation and replace all occurrences of {include file="common/header.tpl"} in any template file with something like
- Code: Select all
{if $currentConference->getConferenceId() == 1}
{include file="path/to/alternate/header.tpl"}
{else} {include file="common/header.tpl"}
{/if}
However, the $currentConference variable isn't available in all those templates, so you would have to find an appropriate alternative (and some of the templates don't have to be modified)
hda.lib@cbs.dk, I understand your desire for greater modularity of templates (like how WordPress works), but that does make upgrading much more difficult. At this point, you would need to use some variant of logical switching. One method that comes to mind is to create separate template directories for each conference with the id of the conference as the directory name, and whenever a template file is included by another template file, attach the current conference id to the path, like
- Code: Select all
{include file="$conferenceId/common/header.tpl"}
.
At this point, whatever changes are made to the templates are going to cause collisions with the next upgrade. I think it would be great to allow for more customization of templates in the future, and it is indeed listed as a suggestion on the OJS roadmap (see
http://lib-pkp.lib.sfu.ca/wiki/index.php/OJS), but it may be some time before we have this functionality.
Happy hacking,
Matt