Plugin configuration problem

  • Resolved xaviermi

    (@xaviermi)


    1 year, 10 months ago

    Hi Jan, I activated your plugin and went through the setup process and saved everything. Unfortunately nothing is published on Mastodon and, checking the authorized applications on my Mastodon profile, your plugin is not there… Where am I wrong or how can I fix it?

    • This topic was modified 1 year, 10 months ago by xaviermi.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Jan Boddez

    (@janboddez)

    It should show on your instance’s /oauth/authorized_applications.

    Does the plugin’s setting’s page say, “You’ve authorized WordPress to read and write to your Mastodon timeline”?

    If you enable debugging (add define('WP_DEBUG', true); to wp-config.php), do the various plugin options show at the very bottom of the settings page? Do you see values for “client ID” and “secret,” and “access token,” and so on?

    • This reply was modified 1 year, 10 months ago by Jan Boddez.
    Thread Starter xaviermi

    (@xaviermi)

    WordPress is not present among the authorized applications on the Mastodon account.

    “Do you see values for “client ID” and “secret,” and “access token,” and so on?define('WP_DEBUG', true);wp-config.php” > NO.

    • This reply was modified 1 year, 9 months ago by xaviermi.
    Plugin Author Jan Boddez

    (@janboddez)

    Which errors _are_ you seeing?

    Do you get a “You’ve authorized WordPress to read and write to your Mastodon account” or does it still say “Authorize WordPress to read and write to your Mastodon timeline in order to enable crossposting”?

    What happens when you click the Authorize button? Is there an Authorize button?

    Does it say “Something went wrong contacting your Mastodon instance. Please reload this page to try again”? Or still “Please fill out and save your Mastodon instance’s URL first”?

    What did you fill in for the instance URL? It should be just the URL of the instance, like https://mastodon.online.

    • This reply was modified 1 year, 9 months ago by Jan Boddez.
    Thread Starter xaviermi

    (@xaviermi)

    “Authorize WordPress to read and write to your Mastodon timeline in order to enable crossposting”? > It does not ask for any requests

    Does it say “Something went wrong contacting your Mastodon instance. Please reload this page to try again”? Or still “Please fill out and save your Mastodon instance’s URL first”? > NO

    The instance URL is: https://mastodon.uno/@profilename

    Screenshot: https://imgur.com/a/EkijPWD

    • This reply was modified 1 year, 9 months ago by xaviermi.
    Plugin Author Jan Boddez

    (@janboddez)

    So the error you’re getting is “Something went wrong contacting your Mastodon instance. Please reload this page to try again.”

    The reason is that your instance URL should be https://mastodon.uno.

    Thread Starter xaviermi

    (@xaviermi)

    <font _mstmutation=”1″></font>I’m getting no errors. Basically once I click on “save changes” nothing happens. It saves the settings I entered, but doesn’t ask me for anything else. There is no permission request to WordPress…

    p.s. so this plugin doesn’t work with mastodon.uno instance?

    Plugin Author Jan Boddez

    (@janboddez)

    I just tested it. It works fine.

    You have to put in https://mastodon.uno (I’ll make this more clear in a next version), and then Save Changes.

    Then an Authorize button will appear. After you’ve authorized WordPress to post on your behalf, it will work.

    In your screenshot, it literally says, “Something went wrong contacting your Mastodon instance.” That’s the error I was asking about. It shows because the instance URL should not contain a username or anything.

    I’ll eventually make this more clear in the docs/description.

    Thread Starter xaviermi

    (@xaviermi)

    Okay. That was the problem. Only the URL of the instance should be entered, without entering the username/profile. Now it has asked for permission. I’ll check that you publish everything automatically, but it’s already a step forward. Thanks for the support.

    • This reply was modified 1 year, 9 months ago by xaviermi.
Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Plugin configuration problem’ is closed to new replies.

Tags