CommentFileSizeAuthor
#9 crude-fix_-_remove-publish-stream.patch1.21 KBgbrands
fb-error.png24.54 KBgbrands
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
CreditAttribution: e0ipso commented

Is it not working? That message suggests that it is working.

mmauroy’s picture

mmauroy CreditAttribution: mmauroy commented

Same here ! I got this working few days ago.
I just install it on another platform this morning (with the latest version) and ran into this error.

stavthan’s picture

stavthan CreditAttribution: stavthan commented
Issue summary: View changes

Same here, it was working when i installed this module (for a couple of days) but now this!
any solution?
Thanks a lot
Thanassis

person101x’s picture

person101x CreditAttribution: person101x commented

Confirmed error as well. This would likely have to do with Facebook's recent forced upgrade to the 2.0 SDK.

person101x’s picture

person101x CreditAttribution: person101x commented

This is likely the problem: http://stackoverflow.com/questions/30074899/error-invalid-scopes-offline...

ighazali’s picture

ighazali CreditAttribution: ighazali commented

So this module is unusable because of the update

stavthan’s picture

stavthan CreditAttribution: stavthan commented

same problem here .
it seems that publish_stream is deprecated and can not be used anymore!
any ideas how to stop asking for publish_stream permissions?

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
CreditAttribution: e0ipso as a volunteer commented

@ighazali patches are welcome.

gbrands’s picture

gbrands CreditAttribution: gbrands commented
FileSize
crude-fix_-_remove-publish-stream.patch1.21 KB

This is a very crude fix, but it got me up and running again. It simply removes 'publish_stream' from the permissions array that is returned.

I tried to remove the permission by editing the permissions for all roles with v2.0 api selected, and the 'publish_stream' continued to be returned. This was just a quick way to be up and running again. If no one else posts an update over the weekend, I might have time to work out a "real" patch.

gbrands’s picture

gbrands CreditAttribution: gbrands as a volunteer commented
pingevt’s picture

pingevt CreditAttribution: pingevt commented

I can confirm that it is the 'publish_stream' permission. I have yet to publish anything yet... but I was able to sign in. (Will work on a patch soon)

Quick fix so far:
1. under the permissions per role for version 2.0, just save the form for all roles. This will remove, the default publish_stream for all roles.
2. fb_autopost.admin.inc, line 89: remove 'publish_stream' from the array.

I'll edit this as I move forward, but wanted to post this to get others going as well.

@gbrands, that will also get it going. When calls are made to fb_permissions_get_facebook_permissions() most are adding in 'publish_stream'. This is why simply saving them doesn't fix it. I think an actual patch will have to update all those calls. Quick search, it only looks like there are 2 calls, and the one i mentioned above is the only one with 'publish_stream' as a default.

stavthan’s picture

stavthan CreditAttribution: stavthan as a volunteer commented

yes !!! it works, thanks man!

marcoka’s picture

marcoka CreditAttribution: marcoka commented
Status: Active » Needs work

  • e0ipso committed 20745fc on 7.x-1.x 
    Issue #2483635 by e0ipso: Invalid Scopes: publish_stream
e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
CreditAttribution: e0ipso as a volunteer commented

This is now fixed in the new release.

Thanks for contributing.

marcoka’s picture

marcoka CreditAttribution: marcoka commented

thank you e0ipso

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
CreditAttribution: e0ipso as a volunteer commented
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

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