Flyover 2.4

Flyover 2.0 is out

Flyover 2.0 is out. This version features a code rewrite from the ground up and has been tested thoroughly for more than 1 month before being officially released.

Library update

HybridAuth has been updated to version 3.0 RC9, the latest available, with performance and error management improvements. This is a giant leap as it marks complete independence from every providers' own SDK. Some providers have been added and some have been discontinued. Continue reading to know more.

Custom scopes

Every provider can now be tweaked individually with custom scopes. You can add or remove scopes intelligently depending on what your application needs to retrieve.

New ACP panel

The ACP panel overview has been revamped with new and more intuitive graphics. It now sports an users usage statistic and a faster access to tokens as well.

New redirect URI

The infamous redirect URI has changed towards a simpler, standardized structure. You will need to change the redirect URI of every provider's application you are currently using right after updating Flyover in the control panel.

Refer to Flyover documentation in order to build and use the new redirect URI.

Other notable changes

The following list of new features have been added:
- new providers: GitLab, Mailru, Odnoklassniki, Spotify, WeChat, Yandex;
- new data point for synchronization: language;
- Suggestion: Disabling mybb login/registration in 1.6.

Critical changes

The following list of critical changes have been applied:
- minimum requirement is now PHP 7.1;
- dropped support for accounts without an email: from 2.0, users are required to specify an email. The emailless and passwordless option has been renamed Passwordless mode;
- some providers have been discontinued: AOL, BeatsMusic, Deezer, Dropbox, LastFM, PayPal, Pinterest, SoundCloud, Vimeo, 500px;
- Microsoft has been renamed WindowsLive;
- popup mode has been discontinued due to chronic instability.

It is highly recommended to try version 2.0 on a test board before deploying it live, which is encouraged anyway. Export your tokens and perform a database dump before upgrading Flyover.

Upgrading to version 2.0

The upgrade process is straightforward:
delete /inc/plugins/Flyover
upload the new version maintaining the same folder structure as in the release package
run the upgrade script when asked in the ACP
rebuild Flyover's cache from Configuration > Flyover > Rebuild cache.

Templates and stylesheets have been changed accordingly to reflect code changes. Being a major release, lots of edits have to be made. For your convenience, a diff comparison is attached to this post in standardized git format.