“Default WordPress blog for crossposts” is blank

  • Resolved alexiumz

    (@alexiumz)


    7 years ago

    Hi, I’m trying to write posts on one site (Site A) and have them automatically post on another (Site B). From what I understand, this plugin is exactly what I’m looking for, however I’m having a little trouble with it actually connecting/posting to Site B.

    Both sites are self hosted and both are connected with WordPress.com via Jetpack, each with their own WordPress.com account.

    I have installed the plugin on Site A. However in any configuration of connecting sites and WordPress.com accounts, it fails to crosspost. The debug simply reads

    array(0) {
}

    And after a little digging, I believe it’s because in the plugin settings, the “Default WordPress blog for crossposts” is blank. There are no blogs to choose from in the dropdown menu.

    I imagine I’ve simply got things the wrong way around with the ClientID side of things, so I wondered whether you might be able to guide me through the process a little and help me figure out where I’m going wrong?

    Clicking the link to create a ClientID, I am taken to a WordPress.com developer page.

    • Should I be logged in on this with Site A or Site B’s WordPress.com account?
    • What should the redirect URL be? It appears that connecting in the plugin settings will only work if the redirect URL is that of Site A’s, regardless of which WordPress.com account I use to create the application.
    • Do I need to add any Javascript Origin URLs of either site?

    Once I have made the application, I can input the WordPress Client ID and OAuth consumer secret in the plugin settings and connect. I’m then prompted with an authorisation page.

    • Should I be logged in with Site A or Site B’s WordPress.com account to grant authorisation on this page?
    • I am then prompted to log in to either Site A or Site B, depending on which WordPress.com account I am logged in to in the step above.

    I am then redirected back to the plugin settings which says successfully connected – albeit without any blog listed in the dropdown list.

    Thanks in advance for your help.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Meitar

    (@meitar)

    This plugin’s Screenshots section shows a walkthrough of this process. The short answer is that it’s identical to every other OAuth sign in process.

    It’s also possible that the WordPress.com REST API service has changed in the last two years, as this plugin has been unmaintained since 2015. If that’s true, then it simply needs someone to find and fix the issue. I no longer have a need for this plugin and so I no longer actively maintain it. ˉ\_(ツ)_/ˉ

    Thread Starter alexiumz

    (@alexiumz)

    I followed the walkthrough with the screenshots; I get to the settings page and there are no blogs listed in the drop down menu whereas there is in your screenshots. It was this that alerted me that somewhere, something wasn’t right.

    I’ll try investigating OAuth sign in elsewhere.

    Plugin Author Meitar

    (@meitar)

    Okay. Again, it may be a bug in this plugin caused by a change on the WordPress.com side sometime between 2015 and now. I’m not sure and unfortunately don’t have the time or resources to investigate it for you. Good luck!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘“Default WordPress blog for crossposts” is blank’ is closed to new replies.