After successful installation and rules set up (via your screencast) logged out of site (which is in maintenance mode) and went back on to add another rule to post newly published nodes.
Was met by having to log in to FB again and when clicked on that button/link. Hit the error. See atached screen-grab.

CommentFileSizeAuthor
FB-Autopost_sign_in_error.png91.37 KBopegasus
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

e0ipso’s picture

Title: Deprecated function: Call-time pass-by-reference has been deprecated in _registry_check_code() (line 3080 of /home/X/X.com/inclu » Deprecated function: Call-time pass-by-reference has been deprecated in _registry_check_code()
Status: Active » Postponed (maintainer needs more info)

This probably happened because of any othe part of the system. You only need to log in in the admin interface to be able to select the pages you want to post to (if any).

opegasus’s picture

Yes, well the 'Log in to Facebook' keeps cycling back to 'Log in to Facebook' and never presents the FB login. The screen-grab shows what is rendered after clicking on 'Log in to Facebook'. Plus I just get the errors.

Since posting this issue I updated to the DEV version...now the the errors disappears but it keeps cycling back to the admin page. No actually FB login appears.

4kant’s picture

...exactly the same here as #2.

I deactivated IPv6 on the server but still the message is thrown by base_facebook.php of of the facebook-sdk (3.2.2).

Don´t know where to look for the source of this error.
The Facebook-App is only of type "Website with Facebook Login" - is that supposed to be correct?

4kant’s picture

...solved my own issue (#3):
api.facebook.com had to be enabled in the firewall.

e0ipso’s picture

Status: Postponed (maintainer needs more info) » Fixed
4kant’s picture

Sorry to reopen this.
After some weeks of pause with my Facebook project the issue came back.
I checked the entry of api.facebook.com in the firewall - it´s still there. Nothing has changed - as far as I can tell.
Has anything been changed concerning fb_autopost login by facebook since 31st of July?

e0ipso’s picture

@4kant please update to the latest version and report back.

4kant’s picture

Yes of course - first I realized that, with the "old" version, login no longer worked (instead the same as #2 again).
Then I updated to the latest version 1.1 with no effect.
The apache error log again says : "Invalid IPv6 configuration on server, Please disable or get native IPv6 on your server."
But on the server I hadn´t changed anything.

That´s why I ask if Facebook did any changes...

By the way - as I´m not a Facebook pro - I wonder whether this article is of interest (or "causes" this issue) :
URL: https://developers.facebook.com/roadmap/

For October 2 2013 it says:

Removing the ability to post to friends' timelines via API
We have found that posting content via API (stream.publish) on a friend's wall lead to a high incidence of user dissatisfaction (hiding content, blocking the app). After the migration period, posting content to friends' timelines via stream.publish will no longer be allowed. Please use the Feed Dialog for posting.

4kant’s picture

...again I found a solution by myself ;-)
This time I enabled graph.facebook.com in the firewall...

...more to come soon ;-)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

B N Pandey’s picture

Issue summary: View changes

Currently I am working on fb_autopost. I am creating rules and facebook aap id for auto post, and adding two event :- 1 -- After saving new content.. 2 -- After updating existing content. But when new content is saved, it is posted randomly wrong image form files folder and given page not found title. But when updating the same content, it posted correct image with page not found title and produce this error.

Deprecated function: Call-time pass-by-reference has been deprecated in _registry_check_code() (line 3139 of /includes/bootstrap.inc).

Thanks
B N Pandey

e0ipso’s picture

@B N Pandey Are you using the last version of the module?

e0ipso’s picture