WordPress 3.0.1
By Dwip August 22, 2010, 4:39 pm Comments (49) RSS Feed for this post

In keeping with the technological breakthroughs of the age, this blog is now running WordPress 3.0.1. This is a fairly significant change under the hood, and things are bound to break somewhere. If they break for you, leave a note here and I’ll look at it.


Blog Comments (49) Trackback URL for this post RSS Feed for this post
Comments on WordPress 3.0.1
avatar Comment by Conner #1
August 22, 2010 at 3:53 pm

Ok, I’m here then.. and getting ready to subscribe to your RSS feed.. is there a distinct benefit/difference between the Atom 1.0 feed and the RSS 2.0 feed? Or should I just use the post specific comment feed?

And why is everything I’m typing in this box appearing to have a right side wrap boarder well beyond the right side of this column? (it appears that about 20 characters or so are under the right hand column.)

avatar Comment by Dwip #2
August 22, 2010 at 4:02 pm

I don’t actually use the feeds myself, but they appear functionally the same to me from within IE. The regular feeds will get you posts on the site, while the post-specific is, well, post-specific, just for comments on this post. YMMV.

The box is well beyond the right border, or the actual comment display is well beyond the right border? Firefox, yes? Might be an issue with display in FF I’m just not aware of. I may or may not be able to handily fix it from within the theme.

avatar Comment by Conner #3
August 22, 2010 at 4:13 pm

Yeah, I tried subscribing to all three to see what the difference was and it appears the Atom 1.0 & RSS 2.0 feeds are the same (and correspond to Samson’s Blog feed while the post specific feed corresponds to Samson’s Comments feed). Since I’m interested in the blog entries generally, I went with the RSS feed, but since I also specifically wanted to “watch” this thread I also went with the post specific one, but I don’t think I like that it’s set up that way. If I was genuinely trying to follow your whole site like I do with Samson’s blog (not that I’m not interested, but I’m not looking to catch back up with your whole site’s history either) it’d mean subscribing to a separate RSS feed for the comments on each and every post you’ve got individually. :(

No, the box and what’s being typed in it. Once it’s posted it all wraps properly. Actually, I’m using Opera 10.61 on Vista at 1280×800 (on my laptop). The edit box has it’s right margin lined up with the “(” in the “Tutorials (14)” above it on the right column.

avatar Comment by Dwip #4
August 22, 2010 at 4:35 pm

I’d need to check with Firefox to be sure (which I don’t have installed right now), but this is the first I’ve heard of the comment form being whacked. May be Opera. May not.

It turns out you can get to whole site comments when you’re logged in by going up under Navigatory where it says “Comments RSS.” If that doesn’t work, the feed is here. I’m trying to figure out the best way to make that more available as we speak.

[edit] Comments RSS should now be available globally. As soon as I figure out how to increase the number of items in said feed, that will also be done.

avatar Comment by Conner #5
August 22, 2010 at 5:00 pm

Sorry, it’s the first time I’ve used the comment form.. or at least the first time I’ve used it to post something long enough to notice the problem. ;)

Interestingly, in my news reader (Akregator under linux as opposed to Opera on my laptop), the box still extends beyond the right column by just as much but is on top of the right column instead of under it.

Also, in said news reader, the RSS feed gives the first so many characters of the post while the atom feed provides the post in full, yet the site-wide comments feed provides the full comment rather than the RSS version of each comment. (Yes, I’d found the Comments RSS link shortly before I found this new thread. :D)

avatar Comment by Conner #6
August 22, 2010 at 5:03 pm

Increasing the number of comments available in the global feed would definitely be a nice touch. Since I leave Akregator running pretty much 24/7 it shouldn’t make much of a difference to me at this point, but it’d still be a nice touch for folks who don’t leave a news reader running when they’re not on their computers. ;)

avatar Comment by Dwip #7
August 22, 2010 at 5:52 pm

And now everything should show 20 entries. While I was at it, the Things They Said comment list on the side now shows 10.

avatar Comment by Conner #8
August 22, 2010 at 6:21 pm

Yup, rss is serving 20 instead of 10 now, and increasing the recent list to 10 from 5 helps. But I do have an oddity for you, and perhaps it’s because I’m logged into the site from my reader so it could grab things as me rather than anonymously, but all my own comment posts are being served time stamped December 31, 1969 instead of August 20-22, 2010 like the rest of the comment posts. Not a huge deal, but given that I keep my incoming posts date sorted, all my own postings are at the bottom of the list each time this way.

avatar Comment by Dwip #9
August 22, 2010 at 6:35 pm

From my end, all the comment RSS, both sitewide and post, is dated 1969. As best I can figure out, this is some sort of WordPress issue rather than anything I can deal with myself.

avatar Comment by Conner #10
August 22, 2010 at 7:05 pm

Strange issue, but I’ll willingly accept that it’s just a Wordpess thing and live with it then.

avatar Comment by Samson #11
August 22, 2010 at 7:07 pm

FWIW, edit box works perfectly fine in Firefox or I’d have complained by now :P

It’s lined up properly with the line running down the page.

avatar Comment by Dwip #12
August 22, 2010 at 7:08 pm

Apparently it has something or other to do with it not adding the date correctly. 1969 happens to be the default date that gets added somewhere.

Chrome, I am told, similarly works ok.

avatar Comment by Samson #13
August 22, 2010 at 7:10 pm

Opera on the other hand is mishandling the edit box. It’s extending past the line down the page about halfway into the next column.

That could either be a bug on their part, or one of those subtle things in the HTML/CSS that Opera is objecting to.

avatar Comment by Conner #14
August 22, 2010 at 7:26 pm

Yup, even in Linux, the edit box lines up fine in Chrome. I think Samson’s right, it’s got to be one of those odd HTML/CSS bits because it was “wrong” in opposite ways in Opera and my news reader which uses the Mozilla engine (to the best of my knowledge) but isn’t actually Firefox. Perhaps later, if you’d like, when I’m back on my laptop I can check how it appears in some other browsers for you. (I’ve got Safari & Netscape on my laptop too.)

Yeah, I’m sure the 1969 thing is one of those Unix time conversion type things and no big deal, it’s just odd that comments not by me show up properly.

avatar Comment by Conner #15
August 23, 2010 at 1:11 am

So, are the buttons above the editing box the only tags supported for members in comments, or are there other tags available too. For example, something along the lines of a quote=name tag, an underline, hard line, colors, font sizes/styles, or…? I know you already love emoticons enough that I could see you removing them even if WordPress did offer them default, but… just wondering, especially since I seem to recall from my own brief foray into WordPress that such things varied by editor with some variety of editors available to choose from and some such things were entirely configurable even independently of the editor chosen.

avatar Comment by Conner #16
August 23, 2010 at 1:16 am

Okay, quick test to see about the performance of the editor box in Netscape Navigator 9.0.0.5 and it appears to work as one would expect rather than as it did in Opera. Go figure. Safari’s up next.

avatar Comment by Conner #17
August 23, 2010 at 1:26 am

Ok, last test of the new comments editing box, and it appears that in Safari 5.0.1 it works right too. So, I have to conclude that it’s strictly a bug in Opera or the way that Opera handles the HTML/CSS in question. (Well, and whatever browser engine Konqueror, which is what Akregator uses, is based upon.)

avatar Comment by Dwip #18
August 23, 2010 at 1:27 am

WordPress comments are pretty limited compared to what Sandbox has available. Most basic HTML is supported, but you have to know what you’re doing. For instance, there’s a way to add a name field to the blockquote tag, but I have no idea what it is.

I’ve tried a couple of times to find a good BBCode parser for comments, to no avail. That may have changed in the intervening months. Hasn’t been much of an issue until now.

I hadn’t ever given emoticons any thought, to be honest with you.

avatar Comment by Conner #19
August 23, 2010 at 2:04 am

WordPress comments are pretty limited compared to what Sandbox has available. Most basic HTML is supported, but you have to know what you’re doing. For instance, there’s a way to add a name field to the blockquote tag, but I have no idea what it is.

I’ve tried a couple of times to find a good BBCode parser for comments, to no avail. That may have changed in the intervening months. Hasn’t been much of an issue until now.

Well, that’s really a shame, but fair enough. I don’t know that I plan to go trawling any html sites to hunt down how to add a name field to the blockquote tag, so I’ll live with what we’ve got. If you do find a nice one, I’ll be delighted to see it though.. on the other hand, that may very well be the major thing that turned me off of WordPress when I’d looked into it to begin with.. well, that coupled with what a pain in the ass it was to configure the plugins that I thought sounded cool of the multitude of plugins available. (I seem to recall spending several full days just scrounging through plugins to try out and mostly reject and then another day or two trying to figure out the conflicts between the ones I had liked.) :D

I hadn’t ever given emoticons any thought, to be honest with you.

Given your comments about them in the past at Samson’s, that is hardly a surprise. ;)

avatar Comment by Samson #20
August 23, 2010 at 2:08 am

How odd that the RSS thing would screw up the dates for the person logged in. In the Firefox reader, my comments here don’t have a date listed at all, which is probably how it handles a big fat 0.

December 31, 1969 – That’s the unix start date. Usually what you see if the timestamp value is a 0. Probably some kind of bug in WordPress.

I beam with pride that Sandbox does comments better :)

Now if only I knew how to make it do plugins so I could proceed with world domination.

avatar Comment by Conner #21
August 23, 2010 at 2:16 am

Well, oddly enough, in Opera’s built-in reader it does show a timestamp but it reflects correctly but it displays in my local time rather then the feed’s own time so it may be going off seconds ago or some such rather than a Unix style timestamp whereas, I suspect, Akregator is going off the feed’s timestamp and perhaps WordPress is setting that field to 0 when it’s the person’s own posts or some such. Maybe tomorrow I’ll throw the feed into thunderbird to see how it displays the feed’s times, though that still may not tell me anything. :shrug:

Well, we’ve already established that Sandbox and QSFP handle several things better than WordPress, the plugins have always been it’s biggest selling point, but they also happen to be it’s biggest security issue potential too.

avatar Comment by Dwip #22
August 24, 2010 at 11:36 pm

Comments are now numbered. There’s also a couple of pagination links, but they don’t work right now. Working on that.

Will eventually need to rewrite the comments stuff to be in line with WordPress 2.7+ per here, here, and here. However, argh.

avatar Comment by Conner #23
August 25, 2010 at 1:27 am

I like the comment numbering.
I have faith that you’ll figure out the pagination.

Okay, after reviewing your three links, I’d have to say that it looks like ultimately you need to invoke “paginate_comments_links($args)”. Not so sure what about the second link is relevant to this issue, but, maybe that’s something else your theme needs that’s just not related to pagination… It looks to me as though the third link you gave is really more syntax examples of how to implement the “paginate_comments_links ($args)” function.

Is this something your rabbit classic theme doesn’t support at all presently or just something it’s not using properly?

avatar Comment by Dwip #24
August 25, 2010 at 1:40 am

If I understand what I’ve read correctly, I need the stuff in the first and second links to make pagination work correctly, among other things. Rabbit Classic is using a seriously old version of the comment code, which is hindering things.

avatar Comment by Conner #25
August 25, 2010 at 1:37 pm

See, this was a big part of why I didn’t go with WordPress, I do enough struggling to know what I’m doing coding my mud and didn’t want to have to struggle to know what I was doing coding my blog that I already struggle to remember to post to too. ;)

avatar Comment by Dwip #26
August 25, 2010 at 3:15 pm

OTOH, it does give me the excuse to do some work with code, which I don’t otherwise get.

Which is also to say that I’m doing this RIGHT NOW, so expect comments to look deeply whacked for a while.

avatar Comment by Conner #27
August 25, 2010 at 4:24 pm

Hmm, I think I liked the comments numbered the other way better, but this way works too. Beyond that, I’m not seeing a lot of the comments looking whacked at this point. :shrug:

Lately I’ve been staying busy enough that I’ve been putting off my own code work for way longer than I should be, but I’m really not at all looking for such an excuse either. :D

avatar Comment by Hanaisse #28
August 25, 2010 at 5:01 pm

Sorry, I didn’t realize it was a WP issue or that you were working on it.

Just to add to my comment of being f’d up, the font appears much bigger than it did previously. Sometimes bigger isn’t better.

(I have pics if you want to see what it’s doing to FF. )

avatar Comment by Dwip #29
August 25, 2010 at 5:05 pm

I’ll eventually be asking for just that thing, but for the moment I’m making changes by the minute, so it wouldn’t do a ton of good.

avatar Comment by Dwip #30
August 25, 2010 at 6:08 pm

And for the moment, we have paginated comments that should look ok and not suck.

I still need to fix comment numbering, as the method I was using doesn’t work with pagination. I also need to fix whatever the deal is with avatarless people showing up with a Gravatar icon. And re-add the topmost “reply to this post” link. And redo the container that held the reply stuff.

But closer.

avatar Comment by Hanaisse #31
August 25, 2010 at 8:00 pm

Page refresh brings you up to the top of the page instead of the comment you just posted. Also the links of latest comments on the right do the same – goes to top of the topic, not the comment.

You may or may not be aware of it.

Also, is there any way to remove the leading http:// that’s in the box when you click to add a link? It’s pretty useless, no one types in a url any more when one can copy/paste a full url.

avatar Comment by Dwip #32
August 25, 2010 at 8:22 pm

I may or may not have just fixed the refresh thing. If I haven’t, I’m not sure if it’s anything I can deal with.

And no, I can’t do anything about the leading http thing. Sorry.

Good news is, I have pretty much everything but the comment numbering working. That’s our next step.

Test comment edit.

avatar Comment by Hanaisse #33
August 25, 2010 at 8:42 pm

Yes, page refresh thing appears fixed. Thank you, sir!

avatar Comment by Samson #34
August 25, 2010 at 8:46 pm

The AJAX comment editing thingy is busted. I tried to edit my last post in the Castles thread only to have it load with no text in it.

avatar Comment by Dwip #35
August 25, 2010 at 8:53 pm

Is it still busted? Because I’m using it just fine. I did change the comment IDs a couple minutes ago, though.

avatar Comment by Conner #36
August 25, 2010 at 9:10 pm

the font appears much bigger than it did previously. Sometimes bigger isn’t better.

I agree, it does indeed seem larger and it may have been better smaller.

(I have pics if you want to see what it’s doing to FF. )

Of course she does, she’s the screen shot queen (as well as the queen of bug finding.) ;)

I still need to fix comment numbering, as the method I was using doesn’t work with pagination.

Odd, it seemed to be working before. You had comments numbered through 50 on the first page and then numbered from 1 through 30-something on the second page of the Castle thread. Or are you shooting for comment numbering that’s continuous?

avatar Comment by Samson #37
August 25, 2010 at 9:43 pm

http://img690.imageshack.us/img690/2455/bustedid.jpg

Still looks pretty busted to me even after a forced refresh.

avatar Comment by Hanaisse #38
August 25, 2010 at 9:52 pm

Yeah, comments look busted, but the font size is back to normal.

avatar Comment by Dwip #39
August 25, 2010 at 9:59 pm

You’re both using Firefox, right? Does it work in IE or any other browser? Because it’s definitely working for me.

And comment display should be final. Comment numbers now work, and they are clickable (instead of the timestamp) to give a link to the comment.

avatar Comment by Hanaisse #40
August 25, 2010 at 11:12 pm

Yes, FF. I’ll go check IE.

–> From IE: The text shows up as editable.

avatar Comment by Dwip #41
August 25, 2010 at 11:22 pm

That’s not good, because it means I haven’t got the slightest damn clue about how to fix it.

On another note, this fixed some errors in the RSS feeds, although having to resort to that solution is…problematic.

avatar Comment by Dwip #42
August 26, 2010 at 12:08 am

And I think we’re done now. Comments, suggestions, &c.

Oh, meant to say. I know y’all with Firefox can’t use the Ajax plugin. I stuck a link back in for WordPress’ default editor. Not as slick, but it’s what I’ve got for the moment.

avatar Comment by Samson #43
August 26, 2010 at 12:20 am

So where is this mysterious link back to the other editor? I’m still having it try and use the AJAX one.

avatar Comment by Dwip #44
August 26, 2010 at 12:24 am

“Comment #43 by Samson | Edit This”

Should be what you see. If not, obviously we have deeper problems.

Also if you could hop on IM to help me test something.

avatar Comment by Conner #45
August 26, 2010 at 12:25 am

I like the comment numbers this way, and the comments themselves look good to me. Just tried the editor from my previous post and the ajax is coming up without anything to edit just like in Samson’s screenshot for me in Opera too. Where’s this link for WP’s default editor? Do I need to do a forced refresh to find it?

Um, what was wrong with the feed that that linked article is meant to fix?

avatar Comment by Conner #46
August 26, 2010 at 12:26 am

I’m not seeing that for my posts either, Dwip. :(

avatar Comment by Conner #47
August 26, 2010 at 12:32 am

Comment #X by Conner

:snicker: We’ve all written Comment #X now…

avatar Comment by Dwip #48
August 26, 2010 at 2:51 am

Hours later, thanks to Samson’s help, we emerge victorious from battle with the evil forces of PHP. That really sucked.

avatar Comment by Conner #49
August 26, 2010 at 1:03 pm

Looks much nicer from what I can see so far, but I also don’t see any edit post options yet… Either way, congrats on your hard fought victory. ;)

[Edit] And it appears the ajax editor is back to working right again too. :)

Leave a Comment