Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_ #51

Open
ghost opened this issue May 22, 2014 · 5 comments

Comments

Projects
None yet
2 participants
@ghost
Copy link

commented May 22, 2014

_

@phillipadsmith

This comment has been minimized.

Copy link
Member

commented May 22, 2014

@stehlo Can you upload a screenshot or two, or a screencast of the behaviour?

@phillipadsmith

This comment has been minimized.

Copy link
Member

commented May 26, 2014

Took me a fair bit of clicking around to reproduce this issue (seen here: https://www.youtube.com/watch?v=d9DgMm1H8LI for those without a running install).

@stehlo Do you have a proposed fix? Have you investigated?

Phillip.

@theory

This comment has been minimized.

Copy link
Member

commented May 27, 2014

@phillipadsmith Do you have a list of steps to reproduce?

@phillipadsmith

This comment has been minimized.

Copy link
Member

commented May 27, 2014

@stehlo Okay. Many thanks. I wasn't privy to the conversation! :) Happy to try to help also.

@theory

This comment has been minimized.

Copy link
Member

commented Jun 3, 2014

The display of the site context menu is handled by comp/widgets/site_context/site_context.mc. The list of all sites is stored in and read from the Bric::App::Cache object ($c). The list of sites to which the user has permission to see is stored in the session, and read via get_state_data() and stored via set_state_data() (defined in Bric::App::Session). The currently-selected site, or "site context", is also stored in the Bric::App::Cache object, accessible via calls to get_user_cx() and set_user_cx(). The cache is stored in shared memory, so should only get flushed when the server restarts. Otherwise, the only reason I can think of that the site context is forgotten is if set_user_cx() is called for some reason.

Anyway, You'll want to put some debugging into comp/widgets/site_context/site_context.mc. If you use print STDERR statements, you can tail the bricolage error log to see the output. That’s how I've typically done my Bricolage debugging.

@phillipadsmith phillipadsmith self-assigned this Jul 15, 2014

@ghost ghost changed the title Site context not kept, when moving between desks _ Jan 3, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.