Paul Ryan

We do have a longstanding meta thread to bring this functionality into the UI for easier control: https://github.com/uhm-coe/authorizer/issues/75 These screenshots help to provide an example UI for the eventual feature,...

This sounds specific to the Google Account integration; we haven't noticed any issues in our testing but we don't use Google logins as extensively as CAS. Do you have any...

Thanks for the pull request, we'll work on reviewing it and let you know if we have any comments/questions. Since caching OAuth tokens has security implications, we'll want to do...

Thanks for keeping this updated; we'll work on getting it merged in the next release cycle. These are the open chores as I see them: 1. Add an option to...

Hm, you seem to be missing the admin javascript, the sources should look like this on the admin dashboard: We confirmed it's present in the wordpress.org plugin repo and the...

One other possibility if you do see `authorizer.js` file present in the plugin source: `jquery-effects-shake` is a javascript dependency, so if that script is missing or unregistered, it won't load:...

We had a workaround for this where we temporarily removed the `terms_clauses` hook that WPML creates: https://github.com/uhm-coe/authorizer/blob/master/src/authorizer/options/class-public-access.php#L196-L204 Since we don't have access to the latest WPML source, can you check...

Can you try commenting out both the `remove_filter()` and `add_filter()` lines? It's possible that WPML rewrote how they hooked into `terms_clauses`, and our code no longer matches their codebase. (We...

We can't remove the entire code block because Authorizer needs to fetch the categories with `get_categories()`. Can you try just commenting lines 199 (the `remove_filter()`) and 201 (the `add_filter()`) to...

OK great! You can leave them commented out on your setup; we'll remove that extra check in the next release of Authorizer so it should continue working after you upgrade.