| Project: | Ping.fm |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | FatGuyLaughing |
| Status: | closed (fixed) |
Issue Summary
As far as I can tell, I've set everything up correctly, but I am still unable to post from Drupal. (The ping.fm account itself works fine.) Here are the steps I followed:
- Downloaded and installed pingfm module for Drupal
- Created Ping.fm account
- Applied for API key, and inserted that on /admin/settings/pingfm form
- Set node settings on form to make ping.fm available on News (Story) content types
- Entered Application Desktop/Web Key (from http://ping.fm/key/) for my account at Ping.fm on Admin user account form
- Entered Custom URL at Ping.fm as given on Admin user account page (though I don't really care about posting from Ping.fm back to my Drupal site)
Then, as Admin, I created a news item, checked Pingfm, and saved. I got the error message: "Failed posting to Ping.fm". At Ping.fm, I see no record of the attempt to post.
Again, my Ping.fm account can successfully post to enabled networks from the Ping.fm dashboard.
What steps have I missed? How can I troubleshoot this further? The Drupal log only shows that this News node was created. Turning on "Debug mode" on the pingfm settings page seems to make no difference.
Thanks for any assistance!
Comments
#1
Nobody?
Can anyone recommend a module I can use instead of pingfm?
#2
I'm having trouble with this as well.
I did change the default key on admin/settings/pingfm to the one that I got from Ping.fm. I don't think you're supposed to do that, you're supposed to use the default Drupal API key. Your personal key should be entered on user/[whatever]/edit under the Ping.fm settings near the bottom.
However, I have no idea how to get the default Drupal API key back.
Uninstalling/re-installing the module did not help.
From this issue, it appears that each Drupal site owner must apply for their own Ping.fm Developer Key. This isn't mentioned anywhere in the docs.
I'm going to hold out trying this, as I'm sure Ping.fm has better things to do than give away thousands of API keys.
#3
Okay, here's what I had to do to get the original API key back:
Make absolutely sure you do NOT touch the "users" table, even though the API key is stored there. I did, and messed up my entire site. If you do accidentally delete the user, create a new one that is identical to the old one, and use phpMyAdmin to set the UID back to whatever it was originally.
Once that's back to normal, do this:
So none of you will ever have to go through that, here is the Drupal API key:
4c625cb344fe57ba6167eb16036c7c35#4
Because I am an idiot, I did not think to look in the source code.
The Drupal API key is in pingfm.module on line 193.
Incidentally, since I reverted to that key, the module works just fine.
#5
Haha, would it help if the key was displayed in the user interface somewhere?
#6
Yeah, that would be immensely helpful. I've run across a couple other bug reports that I think have to do with this.
It would be a good idea to make it much clearer that you have to enter your API key on your user page, and the Drupal API key on the Admin Settings page. Plus a note that says "If you can't read, here's the old key," or something to that effect.
#7
I just went through this process as well.
One easy way of handling this - if the settings page application key is ever submitted *empty*, this might be a good indicator to reset.
#8
Thanks for all the info here - I finally managed to get things posted to ping.fm!
It was all about that API...silly me.
#9
Hi Rob,
I have a patch to transform the PHPingFM.php script so it actually returns the error message when you post. Very useful since that way it will tell you whether they have a problem or it looks like your key is invalid! Very neat, if you ask me 8-)
I think that the PHPingFM could be greatly enhanced, especially by skipping the use of the simplexml_load_string() function which returns a weird object that supports the array operator... Hmm... and somehow, the status cannot be set to a boolean, it is always a string. So later I have to make sure it is 1 (true) and not just if ($result->status) { ... }. I still don't understand it because an empty string is generally considered false.
Anyway, this works great and helped me to find out that a key was not compatible with another...
Thank you.
Alexis
#10
gengel,
I agree that the pingfm error should tell you if the error is that the author of the post (whose key is used to broadcast the message!) did not define a key in their account. Then you could just go there (there could be a link in that error!) and fix it.
Thank you.
Alexis
#11
This solution works perfect. All fine now - it posts to ping.fm as expected.
However, the short url points to the Drupal link not the alias i.e. www.site.com/node/50. Would it be possible to change it to the alias URL i.e. www.site.com/some/thing
Thanks for a great module.
FYI this solution worked fine for me: #3
Karlheinz - March 4, 2010 - 22:18
Cheers
naRen
#12
Rengomez,
That part works great for me. Did you open the "URL settings" and enter "some/thing" in there?
Thank you.
Alexis
#13
Hi Yes I did.
I entered the URL that you get from the user page. The text underneath where it says Application key displays the URL. You copy and paste that into the URL settings.
Hope that helps.
Cheers
#14
It also didn't worked for me.
I couldn't bring it to work by updating an existing node.
Than I did it with a new node entry and now it works fine on my site http://www.laserhairremoval-info.com/
#15
I am closing this issue since the original problem at hand has been solved. However, for those that want to keep updated on the path alias issue please go here.