cjbrowne / cde Goto Github PK

The middleware that sets this variable up is defined at app.js:58, the display code is in layout.jade (which is small enough that you should be able to spot it immediately) and the session handler middleware is set up at app.js:55 and app.js:57. My middleware is literally the last thing to happen before the router, so I really can't see it being an issue with the ordering.

You need to do something that gets layout.jade re-sent to the client in order to work around the bug, but fortunately that's quite a common thing at the moment (I prefer full page reloads to AJAX calls in most places, although more could be done to minimise the bandwidth used by sending 'layout.jade' ahead of time to be cached and using jQuery to populate it on the client-side). Functionality first, optimisation later.