Anonymous

Even if mySQL is up to date, that won’t prevent slow connections, particularly at times of heavy traffic. Have you tried posting at times when the server is less busy?

By ‘new posts’, do you mean everything posted since you changed the template, or everything since you upgraded to 1.2.2, or has it just started behaving differently for no apparent reason?

In that case it could be a subcat thing. I’ve never tried that code on a blog with subcategories so it might be them screwing it up for you.

How would that cause a parse error? Parse errors are a PHP thing, nothing to do with XHTML.

Hmm, the board seems to have munged your javascript… Did you try posting it between backticks? They’re like mirror-image apostrophes and this forum chews up code that isn’t enclosed in them.

What version are you using?

would you mind sharing your source for that?

All I can think of is: try putting it in a div, and if $single set display:none in the CSS? It might help if we knew what you were trying to add.

I am confused by this.

If your data is important enough to require backing up, why on earth are you entrusting it to beta software?

Have you tried importing a test file of only a couple of entries? This would help establish whether the problem is with the size of the file (1mb is still pretty big, as text files go!)

I’m sure that someone will develop a plugin to give you that functionality ??

By all means start designing for 1.5, but I’d urge you not to concentrate all your efforts there just yet. Some of us are still using 1.2.2, which AFAIK is still the official release, and patiently waiting for 1.5 to be finished before we switch ??

You could open up wp-layout.css in a good text editor and search for ‘code’… if it’s not there do as Podz suggests and add

code {font-size:1em}

I skipped the monologue so I can’t really comment on that, but dialogue is right. Some people need to chill out and accept there’s more than one valid way of doing things.

Not right now, but maybe one day ??