XF 2.0 E-Mail from Facebook - Login with Facebook Problem
- Thread starter sbj
- Start date
While it is possible that Facebook is generally taking exception to the way we have implemented the Facebook log in button in the software, there are actually some key differences on your site that they may be picking up on.
The default look of the connected accounts section on XenForo looks like this:
On your site it looks like this:
While there isn't much discernible difference here, if I had to guess, they may be referring to the different "f" icon.
In other words, you should be using this icon:
Instead of this:
This may not be something you have changed yourself, so it might be worth it if we ping @Mike Creuzer on this as if I'm correct, this may affect multiple styles/customers.
The default look of the connected accounts section on XenForo looks like this:
On your site it looks like this:
While there isn't much discernible difference here, if I had to guess, they may be referring to the different "f" icon.
In other words, you should be using this icon:
Instead of this:
This may not be something you have changed yourself, so it might be worth it if we ping @Mike Creuzer on this as if I'm correct, this may affect multiple styles/customers.
sbj
Well-known member
I am using the default XF style (only color changes and minor css changes like adding border).
How do I change those icons?
sbj
Well-known member
@Chris D
Can I get the correct css code to fix it? What should be the hover color?
Not sure if correct. Testing is a pain cause I have to login and logout to test it.
Can I get the correct css code to fix it? What should be the hover color?
Code:
.button.button--provider--facebook > .button-text::before, a.button.button--provider--facebook > .button-text::before {
content: "\fa-facebook";
}
.button.button--provider--facebook > .button-text::before, a.button.button--provider--facebook > .button-text::before:hover {
color: white;
}Not sure if correct. Testing is a pain cause I have to login and logout to test it.
XF 2.0 did use the f icon, but really the extent of our recommendations at this point are to simply upgrade to XF 2.1 which would solve the problem with the icon automatically.
Not sure if upgrading would solve the hover colour or not, but worth a try.
Not sure if upgrading would solve the hover colour or not, but worth a try.
sbj
Well-known member
So you want me to upgrade to 2.1 (which I had to delay because of absence of addon devs), which will cause me a lot of problems, so just I can get the right Facebook icon?
I mean, I am using the default XF style, so all 2.0 XF installations will have that issue. Not sure how feasible the solution is.
Anyway, if you can tell me what the right hover color is, I might get it done by using css?
sbj
Well-known member
I thought the end of life was for the 1.5 release, not for 2.0. Did I miss any announcements?
And by the way, according to the inspector tool, 2.0 does use the correct fa icon :
which is
But alright, sooner or later I had to switch, it just is so funny that the reason for that is a Facebook icon. I'm laughing my soft parts off
.
And by the way, according to the inspector tool, 2.0 does use the correct fa icon :
which is
But alright, sooner or later I had to switch, it just is so funny that the reason for that is a Facebook icon. I'm laughing my soft parts off
.
That's where it gets kind of interesting, and I wonder if Font Awesome had some foresight here.
In 2.0 you probably want to use
So if you go down that route, you may not need to upgrade to 2.1 but it is still the latest, stable and supported release so will still be my advice.
However, in every other release we've ever done, the previous second point release release becomes unsupported when the new second point release is released.
So XF 2.0.x became unsupported the moment XF 2.1.0 was released.
A similar thing happened with PHP coincidentally. PHP 5.6 was supported officially by PHP for longer than PHP 7.0 was.
f09a is the f icon in FA4 but in FA5 it is the correct "official" f icon (as you pictured above).In 2.0 you probably want to use
f230.So if you go down that route, you may not need to upgrade to 2.1 but it is still the latest, stable and supported release so will still be my advice.
1.5 is a special case - bigger and much more considered changes required before upgrading so it has had a much longer support term.
However, in every other release we've ever done, the previous second point release release becomes unsupported when the new second point release is released.
So XF 2.0.x became unsupported the moment XF 2.1.0 was released.
A similar thing happened with PHP coincidentally. PHP 5.6 was supported officially by PHP for longer than PHP 7.0 was.
Triops
Well-known member
Oh man that is indeed hilarious if thats the case @Chris Dlogged it as an issue all the same, will get a patch out tomorrow.
@Mike Creuzer @ThemeHouse
Did you provide a solution for Xenith 1.5.22? If not what would be the line for EXTRA.css, please?
Similar threads
