WP to Twitter update: Cli.gs to be shut down

October 9, 2009

Topics: News, WordPress.

Continuing updates: Cli.gs gets a temporary stay of execution. Keep watching for further news — I may end up making these changes after all, but for now I’ll wait and see.

The Cli.gs URL shortening service is due to be closed down on Sunday, October 25th. At this time, the service will stop accepting new short URLs and generating statistics, but will continue to forward visitors at least through the end of November.

What does this mean for WP to Twitter?

Shortly before October 25th, I will release a very important update to WP to Twitter which will encompass the following changes:

  1. I will remove support for new Cli.gs shortened URLs.
  2. To continue offering choice, I will add support for at least one additional shortener.
  3. Users with Cli.gs as their selected shortener will be given a choice what shortener they’d like to switch to.
  4. If no choice is made, users will be switched to un-shortened URLs

Additionally, I aim to add support for custom shortened URLs – URLs shortened on your own domain. However, this may not happen by October 25th.

8 Comments to “WP to Twitter update: Cli.gs to be shut down”

  1. Cli.gs was not shut down; the old cli.gs URLs continue to point where they always have.

  2. I’d like to change url, but can you now answer what happened with old cli.gs URL’s already created?

  3. I have the same problems as jeff/ I also can’t add short link to the bit.ly account. This are problems with server?
    P.S. sorry for my bad english.

  4. I went ahead and attempted to tweet a new WP post using bit.ly, it gave me a short URL, but it added a parenthesis to my original URL resulting in a 404 error. It also did not register the short link to my bit.ly account, so I can’t edit it. My server is running PHP 5. I don’t know if the problem is in the plug-in or on my server. Any thoughts?
    Thanks.

  5. Hi, Reid – please post requests for support on the WP to Twitter support page.

  6. When I pressed the “check support” button, I received the following messages:

    * Successfully contacted the Cli.gs API via Snoopy and created a shortened link.
    * Failed to contact the Bit.ly API via Snoopy.
    * Successfully contacted the Twitter API via Snoopy.
    * Your server should run WP to Twitter successfully.

    I went ahead and attempted to tweet a new WP post using bit.ly, it gave me a short URL, but it added a parenthesis to my original URL resulting in a 404 error. It also did not register the short link to my bit.ly account, so I can’t edit it. My server is running PHP 5. I don’t know if the problem is in the plug-in or on my server. Any thoughts?

    Thanks.

  7. That’s still an unknown; but it’s a definite risk that they’ll no longer be valid.

  8. Ahh that’s a bummer! What’ll happen to the old cli.gs URL’s already created?