Page not found: /fbautopost/authorization/retry%3Fcode%3D

Created on 24 August 2014, over 10 years ago
Updated 22 March 2023, almost 2 years ago

We have a scenario as follows:

1. Fresh site install / instance using a Facebook app ID and secret that has been used on a prior install of the same site.
2. The logged-in user has already authorized the Facebook app to post on his or her behalf.
3. This instance has never posted for any users.

In this scenario, the first post we try to make does succeed but at the end we get redirected to a "Page not found" error. It looks like the URL is not being unescaped.

Here's a sample of the full URL:
fbautopost/authorization/retry?code=AQDrQmVOSjDsOYflDW--ho-XFZ-zpp5wdG9D6puQXDX5VLt2u2yYmu0cbjBKEj7l39krhQonXfWrxffLejEDnG0CXq38ALMxWtBPltxUaaScxRNALABF-78BwhYBxtLDVxxHinXBRyMqm4qjYs66WqVdzgFbR8ZF2B80o5F0AL4_MxgkgDrkUF5ZQFYyiCK8T_NFA9-KPaWd9dQxTAbV_RGshQiEvzaudunE69tTGSis4noWi-md8TgG0wW56LHLleGiLuGAfzWgM_jgLR0syancYol8PMDt5abh_uwrzycvCziNg12Aj4G3WoUipO_rSmY&state=1e601243605f35af6746266da2774923

One possible workaround would be to convert the code parameter to a menu path argument so that no escaping is possible. For example, the menu path could be changed from "fbautopost/authorization/retry?code=xxx&state=yyy" to "fbautopost/authorization/retry/code/xxx/state/yyy".

That should not require any unescaping, except for anything that Facebook might throw in that could be escaped.

🐛 Bug report
Status

Closed: outdated

Version

1.0

Component

Code

Created by

🇺🇸United States GuyPaddock

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024