Trackbacks: Do they work, and if so, how?

Topics: ASP.NET 2.0
Jan 6, 2008 at 9:23 PM
I haven't seen them work once when linking an article from another site, but I'm also fairly new to them.

If I link an article in a post, isn't the code supposed to trackback to the linked post?

I haven't seen this work yet.

I'm on the newest 1.3 version, Standard theme, although I heavily modified its style.
Jan 7, 2008 at 9:35 AM
Trackbacks tend to show up on outgoing and incoming referrals pretty inconsistent. Probably caused by how different blogging platforms try to filter spam.

WordPress blogs present a designated trackback URI, but using this URI as link on a BE.Net instance, doesn't work at my side.
TypePad blogs display trackback URLs too, but these even result in an error 500.

So yeah, 'even' as a pretty early adapter of BlogEngine.net, it confuses me too. First I thought it's a cross-platform issue, but even from BE.Net to BE.Net sites, track/pingbacks sometimes appear and sometimes they don't.

Who else is experiencing the same behavior? Any thoughts why?

Jan 24, 2008 at 11:06 AM
Anyone pingback issues on v1.3? Maybe (another new) Medium Trust issue?
Feb 19, 2008 at 11:39 AM
I can only agree with jlrolin: If I write a blog-post including a link to a blog-post from a different blog, it does change anything to other blogs trackback list.

If I got it right, there should be trackback refferering to my blog-post...
Feb 19, 2008 at 11:39 AM
Edited Feb 19, 2008 at 11:40 AM
sorry, mouse too quick. saved it twice
Feb 19, 2008 at 12:09 PM
Yeah, hope the BE.NET team will fix this soon. From what I've heard from Al, it's been addressed and scheduled for 1.4.

On a side note, sometimes it takes a few days (!) that any of my trackbacks show up on other BE.NET blogs.
Links to WordPress/TypePad blogs never worked here though :-(
Feb 20, 2008 at 10:43 AM

wotaewer wrote:
sorry, mouse too quick. saved it twice


I don't think you did! I've had this issue since I started using Firefox. Whenever I post a reply on CodePlex, I get a duplicate, as I will no doubt get now! I've reported this, but had no response.