Authorize issue

Same problem here ??

hello,
Could you please check your curl/fopen and firewall settings?
Is there any error in console?
If everything is configured appropriately and the issue persist please contact our support desk.

Thank you.

Please enable output buffering .
Thank you.

I got the same problem.

After click Authorize button, there is error warning :

Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /home…

Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home…

Warning: Cannot modify header information – headers already sent by (output started at /home…

Warning: Cannot modify header information – headers already sent by (output started at /home/….

Please enable output buffering .
or you can change //ob_start(); in facebook-auto-publish.php line number 32 to ob_start(); (ie uncomment the line by removing //).
Hope it helps.
Thank you.

Its not help.

Still got the problem.

I already enable output buffering and in facebook-auto-publish.php line 32 already ob_start()

i have same problem to
how to solve this problem?

Please enable output buffering as a temporary fix.
We will update the plugin soon.
Thank you.

It solves, thank you

• This reply was modified 7 years, 2 months ago by valecava29.

No. Its still not solves for me

If everything is configured appropriately and the issue persist please contact our support desk.

Thank you.

Uncommenting ob_start() worked for me – had the same error on authorisation:

Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /var/www/…/wp-includes/script-loader.php:1542) in /var/www/…/wp-content/plugins/facebook-auto-publish/admin/authorization.php on line 9 Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /var/…/wp-includes/script-loader.php:1542) in /var/www/…/wp-content/plugins/facebook-auto-publish/admin/authorization.php on line 9

I guess I have to re-add that when the plugin is upgraded? Would be good if there was a ‘fix’ setting for that in options in future? BTW I definitely have curl and fopen on, and output buffering – checked in settings and phpinfo()

• This reply was modified 7 years, 2 months ago by timbearcub.

Same problem here. ob_start(); worked as a temporary fix.

ob_start () worked here, but only was needed on the app that was using API v2.12 (I guess).