I’ve been experiencing some issues with sending trackbacks in WordPress 18.104.22.168-beta as of this afternoon. I did an “svn update” to update my local wordpress folder and I was updated to revision 2612 from subversion. There’s a bug report here that relates to what I’m experiencing. It seems the latest revision, 2612 has fixed the problem for some users. Unforunately, the problem started with rev. 2612 for me, which doesn’t make much sense.
If I don’t see something new in subversion by tomorrow afternoon to fix it I’ll probably just revert back to a stable 1.5.1 install.
Well, now what?
Work with Me
I'm available for hire and always taking new clients, big and small. Got a project or an idea you'd like to discuss? Startup plan but no developer to make it happen? Just get in touch, I'd love to see if I can help you out!
Leave some Feedback
Got a question or some updated information releavant to this post? Please, leave a comment! The comments are a great way to get help, I read them all and reply to nearly every comment. Let's talk. 😀
4 thoughts on “Trackbacks In Unstable WordPress”
I don’t even know what trackbacks are so, I am not having any problems… plus I have not upgraded, because I don’t know how, and fear it’ll screw things… 🙂
I can probably do it, providing some reading and backing up, but I don’t see the point if only a beta version is out, and I am pleased with WordPress 1.5 as it is currently. 😉
Pascal, a stable 1.5.1 release is out. It came out about 10 days ago or so.
OK, well I reverted back to 1.5.1 stable and STILL no trackbacks. I dunno what’s up. Supposedly Trackbacks didn’t work in 1.5.1 stable even. So, I dunno what to do. I suppose I’ll attempt to find a working revision in subversion tonight. Although I’ve tried 2611 and 2612 with no success.
This is getting frustrating.
I’m a fuckin idiot. I just went back to revision 2612 from stable 1.5.1. I removed deactivated the BlogTimes plugin and that seems to have fixed the problem. I looked at my apache logs and noticed some funky errors being caused by the BlogTimes plugin. So beware of Matt’s BlogTimes plugin.
BlogTimes plugin located here: http://dev.wp-plugins.org/wiki/BlogTimes