{"action":"opened","issue":{"url":"https://api.github.com/repos/mitcho/shibboleth/issues/28","repository_url":"https://api.github.com/repos/mitcho/shibboleth","labels_url":"https://api.github.com/repos/mitcho/shibboleth/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/mitcho/shibboleth/issues/28/comments","events_url":"https://api.github.com/repos/mitcho/shibboleth/issues/28/events","html_url":"https://github.com/mitcho/shibboleth/issues/28","id":174141494,"number":28,"title":"Problem with $force_update in shibboleth_update_user_data","user":{"login":"devanonyme","id":21067311,"avatar_url":"https://avatars.githubusercontent.com/u/21067311?v=3","gravatar_id":"","url":"https://api.github.com/users/devanonyme","html_url":"https://github.com/devanonyme","followers_url":"https://api.github.com/users/devanonyme/followers","following_url":"https://api.github.com/users/devanonyme/following{/other_user}","gists_url":"https://api.github.com/users/devanonyme/gists{/gist_id}","starred_url":"https://api.github.com/users/devanonyme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/devanonyme/subscriptions","organizations_url":"https://api.github.com/users/devanonyme/orgs","repos_url":"https://api.github.com/users/devanonyme/repos","events_url":"https://api.github.com/users/devanonyme/events{/privacy}","received_events_url":"https://api.github.com/users/devanonyme/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-30T22:27:24Z","updated_at":"2016-08-30T22:27:24Z","closed_at":null,"body":"I was asked to generate a semi-random (need to be unique) nickname on initial account creation and the implementation of Shibboleth seems to conflict with user_register hook.\r\n\r\nI was able to work around this by using shibboleth_user_nickname but I was actually surprised to discover the $force_update flag in the fonction shibboleth_update_user_data.\r\n\r\n2 observations :\r\n\r\n1) You absolutely need to set a filed mapping value (in admin option) even if \"managed\" is check to false (otherwise it generate index error visible in debug).\r\n\r\n2) wp_update_user($user_data) write over the value that is set by my user_register hook (not surprisingly as it's called after). Considering the value is not checked \"managed\" I would have assumed that it would have been handled as such even in account creation.\r\n\r\nI would consider this as a bug but I dont see the use case of $force_update? Maybe it's just a missing check to skip over undefined mapping?"}}
{"actor":{"display_login":"devanonyme"}}