digg Integrator v.1.2

7 Responses to “digg Integrator v.1.2”

1. September 23rd, 2006 at 2:18 pm

   [...] UPDATE: WildBil posted version 1.2 of the Digg Integrator plugin. Instead of downloading that fixed diggIntegrator.php above, just head over to his site to get the newest version. Version 1.2 includes the fixes I mentioned here and a new feature that includes a sample of the button generated by wjt_diggThisPost. Go get it. Share and Enjoy:These icons link to social bookmarking sites where readers can share and discover new web pages. [...]

   - Digg Integrator Plugin Fix at T. Longren
   
2. September 27th, 2006 at 5:18 pm

   [...] First off, you have the ability to add your own links to the your feeds. If you check out my current FeedBurner feed you’ll see that there is a link advertising my digg Integrator plugin floating around the bottom of one or another entry. In time, hopefully, that will be replaced by text ads purchased by advertisers. [...]

   - Feedvertising: Monetize your RSS » Return of the Whatzit
   
3. September 30th, 2006 at 12:33 am

   I get an “ERROR NOT FOUND” image instead of the digg button after an article has been submitted. Any ideas why? I use the “wjt_diCheck()” php function.

   - amit
   
4. October 1st, 2006 at 1:25 am

   amit, I’ve been getting the same thing recently. I believe this may be due to a change Digg made recently (after this plugin had been updated to 1.2). What exactly that change is, I can’t say. Perhaps Wildbil can take a look, but he probably already has so, yah.

   I attributed the error to the box my sites hosted on at Dreamhost. I swear the box my personal blog is hosted on has the worst uptime at Dreamhost.

   Since you see the same thing, it’s most likely due to a change Digg made. I tested my fix roughly 15 times before writing about it, and I never witnessed this error then.

   - tyler
   
5. October 6th, 2006 at 12:21 am

   it’s something in Bill’s new version. i get the same thing, error not found. but, i used the old version too, on another test post, and after some prodding, i did manage to get the digg java button to display properly. then, i updated plugin versions, and did a new test post and now it’s not working. there must be something small, off, in the way the plugin is referring to the API. Bill?

   - david
   
6. October 6th, 2006 at 8:44 am

   Dave,

   If you take a look at the value for “DiggURL” in the post’s Custom Fields you’ll see that value is “http://www.digg.com/view/all/upcoming.”

   What’s happening is Digg is sending referals from a page other than the story’s – this generates an error message in the code served by digg’s JavaScript.

   If you can locate the real url for the story you can simply cut and paste it over that value to fix the problem. I’ll be adding a filter to the plugin to fix this problem tonight.

   There are actually serveral pages on digg’s side that can cause this, I thought I already had filtered them all out but apparently not. Like I said, I’ll work on getting a fix up tonight or tomorrow night at the latest.

   - WildBil
   
7. October 6th, 2006 at 6:33 pm

   Folks,

   The fix required to handle this is going to be bigger than I originally expected. After a bit more examination I’ve found that there are several more pages on digg that can generate this bug.

   It’s not an impossible fix just one that will take a bit longer than expected. Hopefully by Sunday night, Monday at the latest, I’ll have it figured out and addressed.

   For the time being I recommend manually replacing the “diggURL” value in your custom fields whenever you see the “ERROR FILE NOT FOUND” message. I’ll be sure to update everyone when a fix is in place.

   Sorry for the inconvenience,

   - WildBil