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

Upgrade Install Suggestion #13

Open
CodeBlastr opened this issue Sep 28, 2012 · 2 comments
Open

Upgrade Install Suggestion #13

CodeBlastr opened this issue Sep 28, 2012 · 2 comments

Comments

@CodeBlastr
Copy link
Owner

Summary : After a user logs in the first time, they should automatically have the privileges sections update run.

Currently : After you login, after the first install, you are shown your user account, and this leaves the acos table empty.

Desired : After you login, after install. Either privileges should automatically be updated, or you should at least be redirected to /privileges/sections with a message to run the update.

@akhileshs-clarion
Copy link

We understood that after first installation, admin user should be redirected to /privileges/sections and here we need to show a message which would ask to run the update for privileges for users.

We would like to understand after clicking on "Run Update" button, what would be the process being executed. It would be good if you can explain the process in details with example.

@CodeBlastr
Copy link
Owner Author

In order to update privileges you go here : http://example.com/privileges/sections/clear_session and click "run update". You will see the function being triggered by clicking "run update" that it runs this controller function : http://example.com/privileges/sections/aco_sync . I think that will show you the process being executed. This code is where it starts...

https://github.com/zuha/Zuha/blob/master/app/Plugin/Privileges/Controller/PrivilegesAppController.php#L99

The important thing to note is that the aco_sync() method runs as a series of page refreshes. This was because running it as a single process caused the server to time out, as it takes too long.

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

2 participants