#4143 closed defect (worksforme)
JavaScript error on wiki pages
Reported by: | Owned by: | Matthew Good | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | wiki system | Version: | 0.10 |
Severity: | trivial | Keywords: | |
Cc: | alarionov3@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
There is a JavaScript error in the addLinks function, title has no properties
. This is because in the wiki template, addHeadingLinks is only called with one argument.
Attachments (0)
Change History (8)
comment:1 by , 18 years ago
Milestone: | 0.11 → 0.10.2 |
---|---|
Owner: | changed from | to
comment:2 by , 18 years ago
Cc: | added |
---|
Is this bug a so hard fixing. Maybe it can be fast fixed and ported in 0.10 branch or maybe you can provide temporary patch.
My users are tired of IE error message.
comment:3 by , 18 years ago
Milestone: | 0.10.3 |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
This is because in the wiki template, addHeadingLinks is only called with one argument.
Really? That was changed a long time ago: [3564/trunk/templates/wiki.cs]. You're probably using customized templates, check what your TracIni setting is:
[trac] templates_dir = /path/to/your/templates
and compare those templates with the "official" ones.
Anyway, if someone has the error in his modified template, the changeset linked above should be enough for showing how to fix this problem.
comment:4 by , 18 years ago
Sounds strange, but my template is up to date. I chek trac.ini. Path to templates is correct. But in page source (in browser) there is
addHeadingLinks(document.getElementById("searchable"));
instead of addHeadingLinks(document.getElementById("searchable"), "Link to this section");
comment:5 by , 18 years ago
Well, try to modify the template you think is getting used (add some random <h1>HELLO!</h1>) and see if that shows up…
comment:6 by , 18 years ago
There is no results on page. I'm using FastCGI frontend. Mybe ClearSilver is caching templates?
comment:7 by , 18 years ago
I've never used FastCGI myself, but I guess that you need a server restart.
#3729 has been marked as a duplicate.