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

Update some WordPress API calls and some PHP 7 support #21

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

skoranda
Copy link

@skoranda skoranda commented Jun 3, 2016

Added multi-site support for switch to blog functionality
and updated calls to use the newer WordPress user object.

Replace deprecated get_usermetadata call with get_user_meta.

Check for index 'redirect_to' for $_REQUEST before calling
shibboleth_session_initiator_url to avoid PHP notice.

Updated deprecated call update_usermeta to update_user_metada.

Replaced a call to the split() function with explode() since
split is deprecated in PHP 5.3 and is no longer available
in PHP 7.

Added multi-site support for switch to blog functionality
and updated calls to use the newer WordPress user object.

Replace deprecated get_usermetadata call with get_user_meta.

Check for index 'redirect_to' for $_REQUEST before calling
shibboleth_session_initiator_url to avoid PHP notice.

Updated deprecated call update_usermeta to update_user_metada.

Replaced a call to the split() function with explode() since
split is deprecated in PHP 5.3 and is no longer available
in PHP 7.
@jrchamp
Copy link
Contributor

jrchamp commented Jun 3, 2016

Looks good. I have a slight preference for !empty($var) over isset($var) && $var, but the effect is the same.

Note: This pull request would close #9 and close #15

@michaelryanmcneill
Copy link

Hello, thank you for submitting this patch. I released version 1.8 today to resolve this and other issues and included a shoutout for your patch. I did not include the changes for "multi-site support for switch to blog functionality", as I was hoping you could provide further clarification on the purpose and use case that this is supporting. I am the new maintainer of the plugin and all further work on the plugin will be done in a new GitHub repository. If you believe that switch_to_blog change should still be included, can you please open up an issue/PR in the new repository with details on the use case? Thanks!

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

Successfully merging this pull request may close these issues.

3 participants