#186 Error with mount points / tool names' case sensitivity in CSS references
Originally created by: sf-overlords
Created by: rcopeland
Created date: 2010-04-06 20:04:10.875000
Assigned to:rcopeland
This includes both the code to downcase mount points and project names on creation and a migration to move existing mount points and project names.
Originally by: sf-overlords
Post by rcopeland:
Originally by: sf-overlords
Post by rcopeland:
So what happens if I comment on this ticket?
Originally by: sf-overlords
Post by rcopeland:
Rick Copeland wrote:
Originally by: sf-overlords
Post by mramm:
test
On Wed, Apr 7, 2010 at 5:38 PM, Rick Copeland
186@tickets.forge.projects.in.sf.net wrote:
Originally by: sf-overlords
Post by rcopeland:
This is me, replying to a ticket status update.
On Wed, Apr 7, 2010 at 3:41 PM, Ticket 186 186@tickets.forge.projects.in.sf.net wrote:
This is still a problem, at least on master. Did this make it into some other development branch?
To reproduce:
Create a wiki tool on a project, then visit the wiki page. The wiki.css will be sought here (for example):
- https://a.fsdn.com/allura/nf/1316537711/ew/tool/wiki/css/wiki.css
but will only be findable here:
- https://a.fsdn.com/allura/nf/1316537711/ew/tool/Wiki/css/wiki.css
One easy fix would be to change all of the entry points for the apps to be lowercase. Actually making the mount point case insensitive would also work, as suggested above.
Diff:
Hi Karsten, for the wiki, Wiki/css/wiki.css does exist but it is empty. The CSS reference is not downcased but it's accurate and works. Are you seeing a problem where the CSS reference is not working?
Dave: I have recreated the problem on my "personal" project:
It has a link to:
The CSS file in question is missing, while replacing the first instance of "wiki" with "Wiki" yields an empty file. Of course, this isn't a very important file to miss! But the 404 is still happening.
In trying to build a tool, I couldn't get my CSS (or anything in my nf folder) to load, following the pattern of the wiki app. After I changed my mount point in my tool's setup.py (and the name of my asset folder in nf) to be lowercase, everything worked.
This condition is not demonstrated on the initial test data, as that gets correctly installed (to "Wiki") whereas subsequent project/tool registrations will show "wiki". So the problem appears to occur when a tool is being installed, but I haven't investigated far enough down the controller to offer any more insight, because the lowercase workaround did the job for me.
Thanks for looking at it?
Thanks for the good example. This might also be an issue with consistency of how we use tool names, default mount points, current mount point, etc. Original commits
git log --grep='\[#186\]'are in master, but they were long ago and we may have regressed.This is fixed on allura js/186. To test, make sure the wiki.css file loads correctly on the default installed home tool. Add another wiki tool. Make sure wiki.css also loads there.
Originally by: algorithms
Originally by: algorithms
tested and reviewed on sb-9014, looks good, merged to dev