Not Working All The Time [#1943540]

Not sure what's up, but this only seems to be shortening urls intermittently.

I'm using this with the Twitter module and Short URL module, so not sure if it's this or one of those.

Basically what happens, when a node is saved and the Tweet goes out, there is no short url.

The Short URL module seems to work as short url is present ie. bit.ly, but there is no link after i.e. bit.ly/ls.

If I re-save the node it seems to "trigger" the module, but then two tweets are going out.

Comments

Comment #1

IceCreamYou CreditAttribution: IceCreamYou commented 15 March 2013 at 03:58

Status:

Active

» Postponed (maintainer needs more info)

Does it work if you use a different service? Does it work if you try directly from the /shorten page?

Comment #2

mattwmc CreditAttribution: mattwmc commented 15 March 2013 at 05:59

I'm actually using my own custom short url.

I just used bit.ly as an example.

For whatever reason it doesn't seem like the short part of the url is getting triggered, or the Twitter module isn't sending it?

I wonder, is there any way to get the short url listed on the node edit page, showing up after saving?

Seems to be working about half the time or maybe less.

*edit: I'll try a different service and see how it works and report back

Comment #3

mattwmc CreditAttribution: mattwmc commented 15 March 2013 at 14:53

Something is definitely nor working right.

Switched to bit.ly and now at times it will not even post the short url, but just "node/123" which isn't even a link (no http:// or www).

Further note, switching to biy.ly when it did work, didn't work right with subdomains as it didn't recognize them, but my custom short url does. Update: It hasn't been working with subdomains at all.

I wonder if it could be a php issue? That's how the short urls are created?

Update: Switching to PHP to see if it works (previously used Curl)

Comment #4

IceCreamYou CreditAttribution: IceCreamYou commented 18 March 2013 at 04:00

Does it work if you use a different service? Does it work if you try directly from the /shorten page?

EDIT: I am trying to find out something very specific. What I want you to do is to switch the service to something like bit.ly (i.e. not Short URL) and try shortening a URL from the shorten page. This will tell me whether there is a problem with this module or whether the problem is with the way another module uses Shorten URLs.

Comment #5

mattwmc CreditAttribution: mattwmc commented 21 March 2013 at 05:00

Bit.ly didn't work, either.

Actually when the tweet was sent out the url was like node/123

Wasn't even a working link.

Comment #6

IceCreamYou CreditAttribution: IceCreamYou commented 22 March 2013 at 11:54

Please try shortening a URL from the shorten page.

Comment #7

mattwmc CreditAttribution: mattwmc commented 23 March 2013 at 04:49

Checking the reports for shorten does show the correct urls.

I'm not sure where to go to shorten a url from the shorten page?

I have:
/admin/settings/shorten
/admin/settings/shorten/custom
/admin/settings/shorten/keys

Comment #8

IceCreamYou CreditAttribution: IceCreamYou commented 24 March 2013 at 09:42

The URL of the shorten page is /shorten. There is also a "Short URLs" block that shows a shortened URL on every page which will accomplish the same goal of demonstrating that this module works when used independently. However the fact that the reports show the correct URLs has the same effect, which is to show that the problem is most likely with the Twitter module and not Shorten URLs.

However it's still not really clear to me why this would be happening. The Twitter module's integration with Shorten URLs is pretty straightforward, I know other people are using it successfully, and I can't reproduce the problem. What is your format string at admin/settings/twitter/post? Try disabling the Shorten aliased URLs where possible setting as well.