ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Routing issue (Bug #1248)

Added by kwadronaut . at 2013-03-13 10:28 am. Updated at 2013-03-15 03:18 pm.

Status:Closed Start date:2013-03-13
Priority:Normal Due date:
Assignee:Holger Just % Done:


Category:User interface
Target version:3.8.0
Remote issue URL: Affected version:3.7.0



Yesterday I had a funny issue where the name of a colleague appeared at the top right name when I mistyped an addresss. Our chili instances lives at https://fqdn/code/ and I wanted to read an issue so typed https://fqdn/code/1111 instead of https://fqdn/code/issues/1111 When I clicked his name I did arrive to the correct user (me), so I presume that link (https://fqdn/code/users/number) was correct. I couldn't reproduce this on our own tracker.

I tried this on and it looked similar: when visiting https://fqnd/1237 I got a 404 that looks localized in some language I don't speak, but maybe the top right says 'sign in?' On refresh I do get the localized version I prefer, but apparently it thinks I'm not logged in. When changing the url, it notices again that I was logged in. See also the screenshots.

Assigning to Holger Just as discussed on irc.

19.png - Go directly to without having logged out (68.7 kB) kwadronaut ., 2013-03-13 10:28 am

05.png - Refresh that page (65 kB) kwadronaut ., 2013-03-13 10:28 am

34.png - Correct the url in your addressbar and see your name again and that you *are* logged in (86 kB) kwadronaut ., 2013-03-13 10:28 am

Associated revisions

Revision 68e6d171
Added by Holger Just at 2013-03-15 03:15 pm

Manually apply basic before_filters in case of routing error #1248


Updated by Holger Just at 2013-03-15 03:18 pm

The basic before filters where not applied properly when catching an ActionController::RoutingError (which then renders a 404) as Rails obviously doesn't call a controller action in this case but fluke out before. We now manually call these before filters and ensure we have the correct user and localization at hand.

  • Category set to User interface
  • Affected version set to 3.7.0
  • Target version set to 3.8.0
  • Status changed from Open to Closed

Also available in: Atom PDF