You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Miled, we noticed the hybdridauth for Wordpress Social Login 3.0.3 has an Apple.php file in the SRC/PROVIDER folder but none in the CALLBACKS folder so we created a clone file, called it apple.php and gave it the generic callback reference like all the files in the CALLBACK folder, we also added missing icons in the ASSETS folders 32x32 and 16x16 BUT APPLE was not activated in the ADD MORE PROVIDERS panel (at wordpress plugin) so we can enter the client id and client secret key.
Do you have a complete Apple provider set that works for Wordpress Social Login 3.0.3? We also would so much appreciate a Flickr Provider and a Napster Provider pack (Napster is formerly Rhapsody which Hybridauth used to support). Thank you kindly and I am more than grateful for all of your efforts.
The text was updated successfully, but these errors were encountered:
website-doctor-usa
changed the title
Apple and Flickr Providers for Wordpress Social Login plugin
Apple, Flickr and Napster Providers for Wordpress Social Login plugin
Jun 2, 2021
Miled, we noticed the hybdridauth for Wordpress Social Login 3.0.3 has an Apple.php file in the SRC/PROVIDER folder but none in the CALLBACKS folder so we created a clone file, called it apple.php and gave it the generic callback reference like all the files in the CALLBACK folder, we also added missing icons in the ASSETS folders 32x32 and 16x16 BUT APPLE was not activated in the ADD MORE PROVIDERS panel (at wordpress plugin) so we can enter the client id and client secret key.
Do you have a complete Apple provider set that works for Wordpress Social Login 3.0.3? We also would so much appreciate a Flickr Provider and a Napster Provider pack (Napster is formerly Rhapsody which Hybridauth used to support). Thank you kindly and I am more than grateful for all of your efforts.
The text was updated successfully, but these errors were encountered: