quixote7

I don’t know whether to be happy or not that it’s not just me. ??

Hmm. Not sure what it’s doing. I looked at page source, and the comment about “optimized by Yoast” is there, plus the first sentence as an excerpt. So that’s good.

But why doesn’t it show that sentence as being the snippet on the editing page?

And I still don’t see a sitemap. Any way to check whether it’s actually being generated somewhere?

I’ve had that problem, and it’s very frustrating. It’s due to the width of the main block + the side block being too wide for the screen. Even one pixel too wide will cause that. Borders and margins are *included* in that total width.

One sort-of easy way to tackle it is to reduce the width on either main or side by some huge amount, and see if they’re side by side again. If yes, then that’s the problem. Go through and especially check margins carefully. Since they’re hard to visualize, they’re usually the source of the problem.

If not, then you may have somehow deleted a closing </div>. It can be a real bear to find the culprit div in that case.

Hope this helps.

(Bizarre. This morning –hours too late!– all my comments are showing up. I hope this one is more timely.)

Just wanted to mention that I think I’m sort of getting a handle on it. The weirdest part is that everything revolves around knowing the category ID number, but good old WordPress doesn’t actually show that where I’d expect it, on the Category admin page, nor do they let you know how to find it on the Category_Templates instruction page. (Hint, hint, documentation writers!)

I found the answer here. (The ID may show up in the status bar instead of mouseover, depending on browser.)

My theme doesn’t have a category.php page I could use as a model, so I used archive.php, as per the hierarchy tree. I copied that to category-33.php (the one I want to have as a separate page), and I think I’m on the glide path.

Thanks again for the link!

(Same thing happened with the last comment. They just disappear, and I’m the only one who can see them, and only when I’m logged in. What’s going on here?!)

(I don’t know what to make of this. I posted a reply saying Thanks! for your answer, but I can only see it when I’m logged in, and the system says the last comment is yours.

<O_O>

I don’t know if this one will go live or not. Hope you see at least one of them!)

Thanks for your answer! (I’m not sure why that page didn’t show up in all the searching I did. It’s obviously relevant. Maybe Google is *not* my friend?)

I’m still rather confused, though. Is it saying the categories are already separate pages? If so, why aren’t they listed as such? If not, I’m not sure I understand what you do to make a specific category an official blog “page.” I’ve only glanced through that documentation, though. I’ll study it properly, and maybe all things will become clear to me.

Meantime, if there are more pointers anyone wants to share, I can use all the help I can get!

(This post didn’t show up for me for several hours, so I wound up double-posting.

I posted a way around the problem at the other entry. Basically: go ahead and do a totally new wp install, then restore into that.)

One thing I tried was just hitting the “Install” button for the hell of it. Since it wasn’t working no matter what I did, what did I have to lose?

Turns out that you install a “new” blog to restore an old blog. I mean, obviously. Who wouldn’t know that? :rollseyes:

Once you have a new wp install, then copy over your wp-config.php and contents/ folder. (Change wp-config as needed if your new setup requires it.) That gets you your blog back except for the posts, comments, etc. Then you go to Tools and Import, and import the .xml file that you exported from your site. (Or use phpmyadmin to tell mysql to import a .sql backup, but that’s more complicated.)

And then you have your blog back.

A suggestion to WordPress developers and codex writers: either make a note about restoring an integral part of the “install” page, or make it very clear in the instructions that this is how it works. This whole thing was many hours of totally unnecessary aggro.

vkaryl, your reply helps with something else: when I checked validation, the funky flickr script generates a river of errors. I’ll look into the CDATA tagset to fix that. Had no idea what to do before!

Thanks.

(I had a problem with the form used to post these questions, and the duplicate post went into limbo. In the meantime, this one has dropped off the table, but without any answer to keep it company.

Help, help, help. <i>Please.</i>

if you want ordinary bullets rather than nothing, use:

content: "2022 020";

[it will not let me enter that correctly, with or without backticks. what it should say is “double-quote backslash 2022 space backslash zero zero two zero double-quote”]
the “backslash 2022 is the escaped hex value for the ordinary round bullet symbol, and backslash 0020 is the escaped hex value of a space.

A List Apart has, as usual, excellent tutorials on this. Mark Newhouse at that link says that this method works only in Firefox and Mozilla-type browsers. Possibly, now that IE7 is more compliant, it works in that too. I’m not sure what you see in non-Mozilla browsers. Haven’t checked that out yet.

Embarrassing resolution:

Turned out javascript was turned off. But not at WordPress. On my browser. Jeeeee-sus.

The good news is: the documentation works.

Followup #2: moshu, thanks for your response. I didn’t see it earlier. Unfortunately, no, that doesn’t help. I’m obviously doing something wrong, but I can’t figure out what.

Followup: The script works when I just write a web page and put it in. It works on Ethan’s site (https://www.ethanzuckerman.com/blog/) which, it turns out, is a WordPress blog. On my site, I can’t even get a simple “hello, world” javascript to run, no matter where I put it: header.php, page.php, sidebar.php. The only thing that shows up is straight text, and in header.php sometimes not even that.

What could my js problem be? As far as I can tell, I’m entering the script correctly according to the wordpress codex javascript docs. I have rich text editor turned off (although it’s already off when editing templates, in any case). As far as I can tell, I have the path to the script correctly set, and the file is read and execute enabled. Is javascript globally turned off somewhere, and do I need to turn it on?

Help, please! This is driving me crazy!