#3178 closed defect (invalid)
'Browse source' link randomly broken
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | general | Version: | devel |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Sometimes (pretty random, actually), the Browse source link is broken because de < and > characters of the A HREF are the HTML entities < and >. No idea why they got changed like this. See attached screenshot.
After the screenshot was taken, a reload of the page solved the problem. A few jumps later, the problem reappeared …
Attachments (1)
Change History (7)
by , 19 years ago
Attachment: | tracbug2.jpg added |
---|
comment:1 by , 19 years ago
The only logical explanation for this behavior is that the requests are handled by server processes running different versions of Trac, which a restart should solve. I can't imagine you haven't restarted the server a couple of times since this problem appeared, but I really can't think of any other possible cause for this.
comment:2 by , 18 years ago
Yep, the webserver was restarted many times. Actually, I fully restart Apache2 after each Trac upgrade. What bother me is the random caracteristic.
comment:3 by , 18 years ago
I see this too on occasion. Usually a reload fixes the problem but not always. And I do restart the server after upgrades, too.
I find it curious that it only affects the Browse Source button.
comment:4 by , 18 years ago
The bugs comes from old unremoved files in the installation directory. Use the following to upgrade trac :
cd ~/trac rm -rf build rm -rf /usr/lib/python2.3/site-packages/trac svn up python ./setup.py install /etc/init.d/apache2 restart
comment:5 by , 18 years ago
Milestone: | 0.9.6 |
---|---|
Resolution: | → invalid |
Status: | new → closed |
We all breath better now ;)
comment:6 by , 18 years ago
uh, i get this problem when using webadmin plugin… the admin link shows the same way like the 'browse source' link in the image added here somewhere. i'm running debian, with trac 0.9.6 … but could i have the same problem? if so, how should i fix this?
thanks in advance…
A screenshot of the bug.