search

transparencyint / CGIP

Climate Governance Integrity Program
6 stars 1 forks source link

F nodejitsu hosting #267

Closed janmonschke closed 11 years ago

janmonschke commented 11 years ago

Contains all changes needed for hosting the app on nodejitsu. And another fix to make initial locked models work again (which was kind of a Heisenbug ;) ).

Just check if the server still works on your machine and if locked models in one browser window show up as locked in another browser(-window) directly after a reload.

futchas commented 11 years ago

I just test it and the server still works, but the behaviour of the locking is still a bit weird. For instance, if I refresh the same window where i locked an element, it will show it as locked. You need to refresh again to get it unlocked again. Also multiple refresh in the other windows will show an actor as unlocked, even it still is locked in the other window.

janmonschke commented 11 years ago

This is not a weird behaviour, it's wanted and it has to do with that you're using the same username in both windows. So say in window A you've locked something and then you open up window B where it shows as locked. Then when you reload window B it'll trigger a disconnect event of your user and therefore unlock all you locked models. So that when B is finished reloading, it will not show up as locked.

On Sat, Mar 2, 2013 at 12:27 PM, Iyad A. notifications@github.com wrote:

I just test it and the server still works, but the behaviour of the locking is still a bit weird. For instance, if I refresh the same window where i locked an element, it will show it as locked. You need to refresh again to get it unlocked again. Also multiple refresh in the other windows will show an actor as unlocked, even it still is locked in the other window.

— Reply to this email directly or view it on GitHubhttps://github.com/transparencyint/CGIP/pull/267#issuecomment-14326808 .