Navigation Menu

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

Also change the current user object properties on a view #32

Closed
4 tasks done
JoryHogeveen opened this issue Dec 11, 2016 · 1 comment
Closed
4 tasks done

Also change the current user object properties on a view #32

JoryHogeveen opened this issue Dec 11, 2016 · 1 comment
Assignees
Milestone

Comments

@JoryHogeveen
Copy link
Owner

JoryHogeveen commented Dec 11, 2016

Currently I only use capability mapping for the role and capability views.

  • update the current user roles property (only on a role view)
  • update the current user caps property
  • update the current user allcaps property
  • compatibility with blog switching (caused the original values to reset)

Only for capability and role views + add a filter for modules to hook into.

@JoryHogeveen JoryHogeveen changed the title Also change the current user object properties on a role view Also change the current user object properties on a view Dec 11, 2016
@JoryHogeveen JoryHogeveen mentioned this issue Dec 14, 2016
8 tasks
@JoryHogeveen JoryHogeveen self-assigned this Dec 14, 2016
@JoryHogeveen JoryHogeveen added this to the Next release milestone Dec 14, 2016
JoryHogeveen added a commit that referenced this issue Dec 24, 2016
Related #32
- new action: `vaa_view_admin_as_do_view`
@JoryHogeveen JoryHogeveen mentioned this issue Jan 16, 2017
7 tasks
@JoryHogeveen
Copy link
Owner Author

Reopened because when a new instance is made for the current user the view modifications are not applied

  • Also apply view modifications for new instances of the current user

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant