... Just read your #8. I am having trouble duplicating the problem. Obviously, there is some difference in content between refreshed and unrefreshed first posts.

This line is of interest: $messages = tidy_get_error_buffer();

$messages contains more information than we are letting through to the user. If you can add $content .= $messages; above the if ( strpos($..., we might be able to see what is going on.

ION: 'temporarily view this post' is not doing what it is supposed to in prod.

eta: "temp view" works when it is the only entry. If you pick a post in the middle of a long page to "temp view", there is no joy.

eta: "temp view" works when it is the only entry. If you pick a post in the middle of a long page to "temp view", there is no joy.

Has anyone else had this problem? I just tested it by blocking you and temporarily viewing each of your posts, and it worked just fine.

Firefox 1.O, multipiped, Win2K. Definitely reproducible.

edit: Backing off. It only makes the single post visible. My bad.

Never mind.

...although, it is confusing, that it goes back to the top of the page and you have to scroll down past a lot of entries from the same blockee, looking for the one post you thought might be of interest. Maybe a header:location that passes the postid on the $_GET would be good.

t if it gets in geekier up in here, there may be an implosion

It's part of one of the extant requests, to make the block and mark code work like the edit and return you to the scene of the crime.

OK. Have I mentioned recently how much I dislike the block feature?

It really seems anti-community, to me.

why?

I would like there to be no need for a block feature, but it seems that it's keeping more people in the same building, by not forcing them to be in the same room.