Skip to content

[READ ONLY] Subtree split of the SocialiteProviders/WordPress Provider (see SocialiteProviders/Providers)

Notifications You must be signed in to change notification settings

SocialiteProviders/WordPress

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 
 
 

Repository files navigation

WordPress

composer require socialiteproviders/wordpress

Installation & Basic Usage

Please see the Base Installation Guide, then follow the provider specific instructions below.

Add configuration to config/services.php

'wordpress' => [    
  'client_id' => env('WORDPRESS_CLIENT_ID'),  
  'client_secret' => env('WORDPRESS_CLIENT_SECRET'),  
  'redirect' => env('WORDPRESS_REDIRECT_URI') 
],

Add provider event listener

Laravel 11+

In Laravel 11, the default EventServiceProvider provider was removed. Instead, add the listener using the listen method on the Event facade, in your AppServiceProvider boot method.

  • Note: You do not need to add anything for the built-in socialite providers unless you override them with your own providers.
Event::listen(function (\SocialiteProviders\Manager\SocialiteWasCalled $event) {
    $event->extendSocialite('wordpress', \SocialiteProviders\WordPress\Provider::class);
});
Laravel 10 or below Configure the package's listener to listen for `SocialiteWasCalled` events.

Add the event to your listen[] array in app/Providers/EventServiceProvider. See the Base Installation Guide for detailed instructions.

protected $listen = [
    \SocialiteProviders\Manager\SocialiteWasCalled::class => [
        // ... other providers
        \SocialiteProviders\WordPress\WordPressExtendSocialite::class.'@handle',
    ],
];

Usage

You should now be able to use the provider like you would regularly use Socialite (assuming you have the facade installed):

return Socialite::driver('wordpress')->redirect();

Returned User fields

  • id
  • nickname
  • name
  • email
  • avatar