Facebook authorization

  • Resolved rafinhoas

    (@rafinhoas)


    10 years, 5 months ago

    I’m getting this when I try to authorize my facebook account. What I’m doing wrong? I did every step in this instructions 

    -= This is normal technical authorization info that will dissapear (Unless you get some errors) =-

-=

Array
(
    [atpKey] =>
    [doFB] => 1
    [nName] => paraventas.com
    [fbAppID] => 728187430578397
    [fbAppSec] => ac288cdc1a95fd94fb36a77f3c507f5c
    [catSel] => 0
    [catSelEd] =>
    [postType] => A
    [fbAttch] => 2
    [fbAttchAsVid] => 0
    [imgUpl] => 1
    [fbMsgFormat] => New post (%TITLE%) has been published on %SITENAME%
    [fbMsgAFrmt] =>
    [useFBGURLInfo] => 1
    [riComments] => 0
    [riCommentsAA] => 0
    [rpstDays] => 0
    [rpstHrs] => 0
    [rpstMins] => 0
    [rpstOn] => 0
    [rpstStop] => O
    [rpstOnlyPUP] => 0
    [fltrsOn] => 0
    [rpstBtwDays] => Array
        (
        )

    [fbURL] => https://www.facebook.com/Para.Ventas.USA
    [fbPgID] => Para.Ventas.USA
    [rpstRndMins] => 0
    [rpstPostIncl] => 0
    [rpstType] => 2
    [rpstTimeType] => A
    [rpstFromTime] =>
    [rpstToTime] =>
    [rpstOLDays] => 30
    [rpstNWDays] => 365
    [nxsCPTSeld] => a:1:{i:0;s:4:"post";}
    [tagsSel] =>
    [tagsSelX] =>
)

https://graph.facebook.com/oauth/access_token?client_id=728187430578397&state=nxs-fb-0&redirect_uri=http%3A%2F%2Fparaventas.com%2Fwp-admin%2Foptions-general.php%3Fpage%3DNextScripts_SNAP.php%26update%3D0&client_secret=ac288cdc1a95fd94fb36a77f3c507f5c&code=AQC6vAwl4Iq2zLnmGxtw1MiMsbKYQTmiTy6vaAZlikp7BjNBjWjdZ5wNa47m0W2026AJSQNxFaDoSBkYw0rayJ88W8yCEXNyXosNIwgw7Y06GbhHDo_fByQ6urg09pJWcsb2cs-u9LvoU96Jt4N6Ueh7UZowV00qMDZLh0vDg-c_uAELcy8ysyz24G9OW4BecNgh-evW3YXNnhC5JluVQcZCgI7VJI_akN5h5RbGXrrfSNIvGzuPklcc4oQnlkehV3fkclh34YYlvhOyi8-h97XdDvY1vFBqJFO25CPoIueQ6sLx32deKouGZHLtUIdN7D8

Array
(
    [headers] => Array
        (
            [www-authenticate] => OAuth "Facebook Platform" "invalid_code" "Error validating verification code. Please make sure your redirect_uri is identical to the one you used in the OAuth dialog request"
            [content-type] => application/json; charset=UTF-8
            [pragma] => no-cache
            [access-control-allow-origin] => *
            [x-fb-rev] => 1306262
            [cache-control] => no-store
            [expires] => Sat, 01 Jan 2000 00:00:00 GMT
            [x-fb-debug] => GBqm6EfGXbHBxpe5LIUPr26C+kA7Xxl0HlgOZpAnskevkklNxvsv2D7bAzSK0EIinruXW8JEKH0nRFGtCMfxqg==
            [date] => Thu, 26 Jun 2014 15:29:46 GMT
            [connection] => close
            [content-length] => 190
        )

    [body] => {"error":{"message":"Error validating verification code. Please make sure your redirect_uri is identical to the one you used in the OAuth dialog request","type":"OAuthException","code":100}}
    [response] => Array
        (
            [code] => 400
            [message] => Bad Request
        )

    [cookies] => Array
        (
        )

    [filename] =>
)

    https://www.ads-software.com/plugins/social-networks-auto-poster-facebook-twitter-g/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author NextScripts

    (@nextscripts)

    This is a known error that happens when one of your other plugins or theme is silently altering PHP $_GET variable. We will put a workaround fix in the next release.

    Before that you can try to deactivate other plugins. Once you deactivate plugin altering $_GET variable, you will be able to authorize it.

    If it’s help you anyhow, this is what is being added:

    update=0

    When is this going to be fixed?

    Plugin Author NextScripts

    (@nextscripts)

    We will put a workaround fix in the next release. In a meantime just deactivate plugin that alters $_GET, authorize Facebook then activate it back.

    We don’t know which plugin is modifying GET.

    We recently upgraded your plugin and all of our linked accounts are gone.

    We readded them and now everything is working except FB, which is the most important link. We can’t be digging through all of our plugins to find out what is causing this. It was working before our last upgrade of your script.

    BTW we are Pro users.

    Plugin Author NextScripts

    (@nextscripts)

    To be exact it was not caused by our plugin. The reason for this is Facebook API 2.0. It was released on Apr 30 and everybody were forced to switch to it.

    This problem is a result if that switch.

    As I said next release will contain a workarond fix for it.

    OK, but it actually stopped working when we upgraded, not on Apr 30th.

    Any idea when we can expect the new version?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Facebook authorization’ is closed to new replies.