Replaced HybridAuth with cAuth?

I’m sorry for the inconvenience it caused you. TO access the backend, delete the plugin folder through FTP. The plugin folder is: /wp-content/plugins/facebook-publish/.

After that you will be able to access dashboard, then you can reinstall the version 1.4.1, the problem wont occur anymore.

The new version not work wen i insert the Application App ID: and Appplication Key:, after i click on Authorize Now, have this message: Facebook Publish: Please enter Application ID and Secret Key

You need to click on save button after inserting APP ID and secret. After that you can click on authorize.

We have to set some permission on facebook with new version of their APIs?

I dont think so. Is it not working with you?

Hello Pramod , thanks for the awesome plugin ,

it works with my old facebook app but with the new version it’s not working .

what i did :
1-log out from authorization
2- enter api v2.3 application ID and Key
3- authorize the app
no page appear after that , also it is not asking to ( manage my page ) or publish on my profile.

when i back to the old app v 1.0 everything works fine

I have already clicked on save button, but not change the results.

No it isn’t working for me, same error.

I’m trying to fix it but I don’t understand what is the problem.

Can you create a “transition” version with optional support for new cAuth and old HybridAuth? So we can migrate “gradually”.

Hi all,

I understand the problem you all are having. I’m sorry for not being able to test the plugin properly. Please be patient, I will do thorough testing and release a working version soon.

Thanks

Thank you, Pramod, for addressing the issue and I hope a solution will come soon. Terrific plugin, otherwise.

Thank you Pramod

Hello darkamex,

I’m not able to regenerate the problem you are facing. Can you please send me the system information of your WordPress installation, using the following plugin:

https://www.ads-software.com/plugins/send-system-info/

My email ID: [email protected]

Thanks

Hello,

I believe your problem is fixed now. Can you guys please update and confirm.

Thanks

Sorry, but not work

any updates regarding this problem?