This is a critical issue for merging it in with our codebase, because of how we establish which application is responsible based on the canvas_path.
If the media-pop app grants access to / and giveaways cover /giveaways we are going to run into an issue where if the giveaway user wants to access /privacy-policy they'll be logged out. Worse yet if a user is logged into /dashboard to manage their promotion and they go to look at their giveaway thus hitting/giveaway/something/ the system (as it is) would log the /dashboard user out, causing some confusion as to why the user needs to constantly log in when they go back.
After #19 it would be more like:
request.user.facebookuser_set
We should probably also enable something like:
request.facebook_user
So we don't have to run do a filter each time we want to current facebook user.
This is a critical issue for merging it in with our codebase, because of how we establish which application is responsible based on the canvas_path.
If the media-pop app grants access to
/and giveaways cover/giveawayswe are going to run into an issue where if the giveaway user wants to access/privacy-policythey'll be logged out. Worse yet if a user is logged into/dashboardto manage their promotion and they go to look at their giveaway thus hitting/giveaway/something/the system (as it is) would log the/dashboarduser out, causing some confusion as to why the user needs to constantly log in when they go back.After #19 it would be more like:
We should probably also enable something like:
So we don't have to run do a filter each time we want to current facebook user.