cjsmith: (b&w fancy rob)
cjsmith ([personal profile] cjsmith) wrote2002-02-14 06:06 pm

NOW what?

ALL right folks, who stole my "Comment on this" link from the previous post?

I swear, LJ hates me. No one else has the stupid reply links. Now I can't get comments at all. Grrr.

[Edit: Well, at least THIS one has it. No, I did not disable comments on the previous entry! Not intentionally.]

[Much Later Edit: HAHAHAHAHA, Joe told me how to access that entry for editing. Comments are enabled again! The missing link is back! I have TRIUMPHED! With a little help from my friends. :-)]

[identity profile] joedecker.livejournal.com 2002-02-14 06:38 pm (UTC)(link)
[Edit: Well, at least THIS one has it. No, I did not disable comments on the previous entry! Not intentionally.]


If you go back and edit that one, can you see if that got accidentally checked?


LJ isn't outputting "comment on this", so it doesn't appear to be the sort of weirdness that sometimes crops up from malformed HTML.

[identity profile] cjsmith.livejournal.com 2002-02-15 10:37 am (UTC)(link)
If you go back and edit that one, can you see if that got accidentally checked?

That was my first thought, but I don't know how to edit it without the "comment on this" link. I can't find the item ID for it. Between this post and two posts ago, where the uncommentable one lies, is a range spanning several hundred potential ID numbers.

Maybe it got checked accidentally. Best I can figure.

[identity profile] joedecker.livejournal.com 2002-02-15 12:53 pm (UTC)(link)
I had missed that, but I do have something you may not have tried. From your user info (or any page with the blue left column in it), pick "Edit Entries", then choose "last N entries" for some value of N...?

[identity profile] cjsmith.livejournal.com 2002-02-15 03:54 pm (UTC)(link)
HAHAHAHAHAHAHA that did it! "Disallow comments" had, indeed, been checked. And for my future information, that post was itemid 58276 :-)

[identity profile] joedecker.livejournal.com 2002-02-15 04:25 pm (UTC)(link)
Awesome! I'm just glad we found a workaround, don't matter none to me how it got that way. :)