Unable to Authorise Access about share-on-mastodon HOT 6 CLOSED

Thanks for letting me know! What version of the plugin are you using? Which Mastodon instance?

1. Would it be possible to enable WP debugging by adding the following to wp-config.php?

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

You should then see a textarea field on the settings page for this plugin that displays your Share on Mastodon settings. (Don't share them here! But you should then at least be able to see if a mastodon_client_id and secret were assigned, which should happen in the background when you first input and save your instance.)

Actually, there must be, otherwise the Authorize button would not be shown. They do get sanitized, though, before the plugin saves them to the db, so maybe they got corrupted there.

2. Do you have access to your SQL db? Mind running something like DELETE FROM wp_options WHERE option_name = 'share_on_mastodon_settings'; (Best make a backup before. May need to adjust your database prefix.)

If not, that's okay, too. I plan to release next version very soon, and will at least add a way to recreate a client id and secret, and remove the superfluous sanitization.

from share-on-mastodon.

from share-on-mastodon.

Yeah, somehow the client ID or secret WordPress has stored for you isn't what your instance is expecting, which is stopping you from authorizing WP to access your Mastodon account by means of an access token.

If you deleted the plugin's settings (which does not happen on uninstall, for multiple reasons), you'd get assigned a new ID and secret, and chances are those would work.

The new version should be available soon. Today, perhaps, or tomorrow. And will include a couple changes that make switching accounts and wiping settings much easier, and storing tokens and such more robust.

from share-on-mastodon.

from share-on-mastodon.

All right. Not promising anything, but: you should now (or soon) be able to install v0.4.1, which comes with a back-end button to destroy all settings. You could probably just do that and then try again. The way the client ID and secret are saved also changed slightly, and I haven't had any issues testing things over here, so ... Fingers crossed.

One other thing's changed: if after you've installed the update, you deactivate and reactivate the plugin (or install from scratch), it should also check the validity of your access token in the background, once a day.

Should you find that posting to Mastodon suddenly stops working (like when you revoke the token from Mastodon's back end but not WordPress), you'll then notice the need to re-authorize on the settings page, and the blank token, in case debugging is enabled, in the settings "dump." (I'll add context and what not in a later version.)

It's probably safest to disable debugging after troubleshooting, and delete the debug.log file in wp-content (or elsewhere, if you've set it up that way) in case there is one.

from share-on-mastodon.

from share-on-mastodon.