-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update Authorizer plugin management #494
Comments
Commented out second task since we now have a custom maap plugin for WordPress where we can add WP customizations. |
Code has been submitted to the original author of the plugin in the form of a pull request. They have already replied stating they will review it this week. |
The changes I proposed for the Authorizer plugin were accepted and merged into the official Authorizer repo. I've upgraded the plugin in DIT and UAT to version 3.4.1. and set the @oddes When you have a moment, could you please test and verify that you are able to login to the portal using your test accounts? |
Looks good. Able to login to both UAT and OPS. |
@oddes only DIT and UAT have been updated. Was awaiting the results of your tests before I published to OPS. |
@anilnatha Please push this to OPS for testing. |
The Authorizer plugin has been updated in OPS and is ready for your testing @oddes
|
works good. |
Our portal is dependent on a specific version of the Authorizer plugin that we have forked and modified to work with our CAS instance. Because of this, we should not use WordPress's plugin update features; otherwise it will overwrite our modified version of the plugin.
We need to:
Create a child theme of MonochromePro so that changes tofunctions.php
are not overwritten when the theme is updatedThe text was updated successfully, but these errors were encountered: