as doc says, I have "cp" template/en/default/* into a new template/en/custom directory, then modified banner.html.tmpl... and I can't see my changes :( I also tried a minor change to index.html.tmpl: not better... obviously, changing default/index.html.tmpl works. so, what's wrong?
Did you run checksetup.pl after adding your new templates?
that's it! I changed summary from "can't make template customisation work" to "template customisation documentation does not tell to run checksetup.pl" ;))
Summary: can't make template customisation work → template customisation documentation does not tell to run checksetup.pl
I'll go for that.
Assignee: justdave → matthew
Status: UNCONFIRMED → NEW
Component: Bugzilla-General → Documentation
Ever confirmed: true
IT shouldn't have just failed silently, though. The only case where I could see this maybe happeningis if the wbbserver has read access to the default/ template, but not the custom/ one - could that have been happening?
it is possible: install user is not apache user on our system, and we got some 403 errors (not related to this problem): may be I forgot to chown "custom" directory before testing... if I chown back "custom" dir to install user, bugzilla displays default templates: where is it suppose to log some error?
Matthew is still going to be around to help out, but Jake is taking over the day-to-day front-line triage type stuff for Documentation
Assignee: matthew → jake
Status: ASSIGNED → NEW
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.18
Debian install (using prepackaged .deb files from Testing build) has the same problem, yet running checksetup.pl does NOT make bugzilla read from the /custom/ directory. May be debian-specific problem, not sure.
Added a note to both 2.16 and the tip documentation.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.