CatTravers
My feedback
1 result found
-
33 votes
Evgeny Zaritovskiy
responded
Workaround from Beardo:
To restore the old authorization page look:
/* SOCIAL LOGIN BUTTONS HIDE */
.WaGadgetAuthorizationRequired .openAuthFormContainer {
border-right: none;
max-width: 0px;
padding-right: 40px;
display: none;
}/* PADDING TO SOCIAL LOGIN BUTTONS HIDE */
.WaGadgetAuthorizationRequired .authFormContainer {
padding-left: 0;
}To remove the login buttons from the member directory personal profiles (at the bottom):
/* MEMBER SOCIAL LOGIN BUTTONS HIDE */
#socialLoginContainer, #idSocialLoginContainer {
display: none;
}Just copy/paste the above and update your “user.css” file.
CatTravers
supported this idea
·
An error occurred while saving the comment
I couldn't agree more. And clients who prefer not to add these buttons should not face demands to justify their reasons!
Ditto for setting the logged in members landing page. It's great that they gave us advance warning that the default would change and need to be manually restored, but it took two emails to tech support and 48 hours to get the link to the instructions on how to do this. Searching on the exact phraseology used in the heads-up email did not bring up the instructions.
I'm baffled as to why they didn't just include the link with the instructions in the advance warning email they sent out. Isn't it completely obvious that you need to tell people how when you warn them they will need to make a manual change? Also, they need to proofread those instructions, as they have referred to the "Members" menu as the "Membership" menu.
All in all, the login-related updates give the impression of something hastily cobbled together without taking a few minutes to think through the implications from the client point of view, and disregarding some really basic best practice precepts.