Thank you!
I've updated the module page as it was still talking about the email address.
Hey nginex,
If it is a new platform with no users that will work.
If you have an existing platform with users in it already and all of a sudden they start using the Social Strava button login instead of their emailaddress this will create a new account instead of logging in their existing account (no match on email address) so I do think this will have an impact.
Good luck!
Hello nginex,
I just checked the existing module and API to have an idea of the changes that will be needed to make the module work again.
When investigating this I noticed the following notification:
"January 15, 2019
Email address is no longer part of the profile:read_all scope and is removed from the athlete model."
I also checked the API documentation and it looks like Strava does not return an e-mailaddress anymore. When you would authorize there is no way of checking/matching the e-mail with existing users. So you wouldn't know if you need to login an existing user or create a new user.
This is something to look into before putting effort in this module as I don't think it's possible anymore.
I look forward to your feedback.
Dear nginex, that would be awesome!
I added you as a maintainer, if I can be of any help (for example testing).
Feel free to contact me.
Thanks a lot in advance!
Thank you for your input.
I deleted the link on the module page, I wasn't aware that the site was hacked and/or redirects to a russian website without a https:// link.
The module still has a lot of use cases as you can create a sticky element without the need of custom css and/or a custom theme. It works out of the box with for example the Olivero theme with the following setup.
Thank you all for your input, I don’t think the initial patch adds any value to the module so I’m closing this issue for now.
Thank you!
I'm sorry, I've added the release notes. This was a very small update that only adds D10 compatibility and doesn't change/add anything else to the module.