- How do I install mmanos/laravel-social.
- Install it with Composer using the package name mmanos/laravel-social in a Laravel 4 application. You then register the package service provider and facade alias in your Laravel config and publish or create the package configuration file. Installation will not work on Laravel 5 or later because the Composer constraints target Illuminate ~4.0 and legacy PHP versions.
- Does mmanos/laravel-social support Laravel 5, 6, 7, 8, 9, 10, or 11.
- No. mmanos/laravel-social is a Laravel 4-era package and depends on Laravel 4 components and PHP versions that are end of life. It is not compatible with modern Laravel releases and cannot be adopted as a dependency in Laravel 5 and above. Use Laravel Socialite for current Laravel applications.
- Which social login providers does mmanos/laravel-social support.
- The package provides OAuth social login drivers for providers such as Facebook, Twitter, Google, and GitHub. Provider configuration and authentication flows are handled through the package's configurable driver API. However, many provider endpoints and API versions have changed since 2014, so those flows are likely broken or unreliable today.
- Is mmanos/laravel-social still maintained.
- No. The last release was on 2014-11-28, the repository has no active maintainer, and there is no CVE response or provider API update process. It should be treated as abandoned legacy code rather than a supported dependency. Any production use carries significant security and maintenance risk.
- What is the best alternative to mmanos/laravel-social for modern Laravel.
- Laravel Socialite is the first-party replacement for OAuth social login in Laravel 5 and later. It supports major providers with a stable, documented contract and is actively maintained alongside Laravel. For additional providers, use the socialiteproviders/* community packages rather than a Laravel 4-era facade.
- How do I configure Facebook, Twitter, Google, or GitHub login with mmanos/laravel-social.
- Configuration is handled through the package config file, where you define provider credentials, redirect URLs, and related options. You then call the Social facade with a driver name, such as Social::driver('facebook'), to start the authentication flow. Because the package targets Laravel 4, the config layout and service-provider assumptions do not match Laravel 5 and later.
- Can I safely use mmanos/laravel-social in production.
- Using it in production is high risk. The package is pinned to end-of-life Laravel and PHP versions, its OAuth dependency chain is unmaintained, and provider endpoints from around 2014 have largely changed or been retired. If a legacy Laravel 4 application must keep it temporarily, isolate it behind an internal interface and plan a Socialite or custom OAuth client migration.
- How do I migrate from mmanos/laravel-social to Laravel Socialite.
- Start by inventorying every provider, callback route, and user-record column used for identity mapping, such as provider, provider_user_id, and tokens. Introduce an internal social authentication service abstraction and replace Social::driver calls with Socialite driver calls behind that interface. Then update callback handling and test each provider flow before removing the old package. This is effectively a rewrite of the social login layer, not a drop-in replacement.
- Why does mmanos/laravel-social fail when logging in with Facebook or Google.
- The package was built around provider APIs and OAuth endpoints from around 2014, and those versions have since been retired or changed. You may also hit transport or signature failures because the package depends on legacy PHP and OAuth libraries that do not meet modern TLS or cipher requirements. Updating credentials alone will not usually fix these incompatibilities.
- How do I test social login with mmanos/laravel-social.
- Testing is difficult because the package assumes Laravel 4, legacy PHPUnit conventions, and a facade-based driver layer. You can mock the Social facade or individual drivers to avoid real provider calls, but the underlying dependencies are outdated and may not run in modern test environments. A better long-term approach is to test your own social authentication abstraction so the provider implementation can be replaced.