Viewing 11 replies - 1 through 11 (of 11 total)
  • I still Get

    The API call returned a 503 response code.

    Plugin Author Andrew Norcross

    (@norcross)

    can either of you check (1) what your current version of YOURLS is and (2) if the install is a public or private one?

    Thread Starter Spike05de

    (@spike05de)

    Is the newest version 1.7 (Tom Araya). The install is private, the problem exist with public also

    Plugin Author Andrew Norcross

    (@norcross)

    @spike – the plugin won’t work with a public install, due to the YOURLS API limitation on using API keys (they only work with private). There are bugs with the 1.7, make sure you’re running 1.7.1.

    also, a fix will be out shortly to account for installs that are on a subfolder.

    Mine has always been set to private.

    Yes I have the latest version of Yourls

    Thread Starter Spike05de

    (@spike05de)

    I don´t find the newest version of YOURLS. https://github.com/YOURLS/YOURLS/releases

    My install is private

    Thread Starter Spike05de

    (@spike05de)

    The plugin works great when I publish a new post. Then the shortlink are generated. But I need the shortlink before the post published.

    Plugin Author Andrew Norcross

    (@norcross)

    @spike that’s not possible at the moment, because the final URL has not been generated in WordPress before publish. may I ask why you need the link beforehand?

    Thread Starter Spike05de

    (@spike05de)

    I can generate the URL always before. If the item is scheduled. This makes sense because during the automatic posting on the Twitter Short Link will equal published. But at the moment I can not generate short URL if an item is scheduled. I get the error message: This is not a valid post status. Before the update, everything worked fine.

    Plugin Author Andrew Norcross

    (@norcross)

    @spike05de I’m about to push an update that adds back in scheduled posts. this was an oversight on my part, my testing with scheduling didn’t create a URL due to an unrelated reason.

    Thread Starter Spike05de

    (@spike05de)

    No it works.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Same problem after update to 2.0.4’ is closed to new replies.