notthatugly

Your archives are stored separately in the database you set up when you first installed b2, so uploading new files can’t overwrite them. I was also hesitant about switching, but I found the upgrade process very smooth.

Check that you have this line at the top of index php:
require_once($abspath.’wp-links/links.php’);
and that it hasn’t been commented out.

It goes in the parameters for php the_content:
< ?php the_content(‘(leer mas…)’) ? >

How many kinds of template do you want? For me, one of the main advantages of WP is that I <i>don’t</i> have an infinite number of templates to configure.

oh, it mangled the last two parameters, which denote what you want before and after each link; e.g.

• and

<? php get_archives ('postbypost','x','html','

• ','

'); ?>
where x is the number of titles.

The main differences seem to me to be the integrated blogroll, ability to password individual entries, and saving posts as drafts. Archiving is also slightly more flexible. Hope that helps.

I’m not sure that a default template (and that’s what these are supposed to be, aren’t they?) ought to be hiding the links section, since the integral blogroll is one of WordPress’s main ‘selling’ points. But it would certainly have been useful to have one div for the blogroll, another for the calendar, another for categories etc. Or, at the very least, split the menu into two separate divs (as I’ve done on my personal blog) so that three-column layouts are a viable option.
But I’ve done what I could with what we’ve got and posted a zip file of seven stylesheets
here . They’re predominantly imageless because while it’s perfectly possible to make image-centred layouts using only CSS, they don’t seem to me to allow as much scope for user customisation.

I agree — even though the structure of index.php is very limiting, there’s no reason why every design should be two vertical columns extending the full length of the page. Although it wouldn’t be my first choice to use an inline scroll for a blog, I’m all for giving the end user the option.
I think this is because I started journalling on diaryland before I moved to my own domain; because they have shorter entry pages, are more likely to be female and less likely to be techies, diarists tend to place more importance on how their site looks. A user coming from that context is accustomed to seeing relatively small entry boxes, and won’t have a problem. Somebody who only reads blogs using conservatively designed default templates might have issues with it. I’d trust the end user to know their own audience and cater for them accordingly.

any limit as to the numbers of entries per person?

ALA also has a simple php switcher which I’m using on my blog; it sets cookies, is Mozilla-friendly and uses no javascript.

If you want to display both titles and dates you’ll need to use one of the archive hacks available on this forum. I’m using codergurl’s hack, and all you’d have to do is edit the lines at the bottom:
<?php archive_date(‘m-d-Y h:iA’) ?>:
ID&c =1″; ?>”>
<?php the_title() ?>
to
ID&c =1″; ?>”>
<?php the_title() ?> :
<?php archive_date(‘F j Y’) ?>

But is there any way of controlling the number of posts displayed within the template? I vaguely remember this being possible with b2 — something like ‘posts=5’ in the header?
(Also, if you use get_archives to get links to the last few entries you have to choose between dates and titles, whereas if you’re using the post engine you can display both.)

That’s great — thanks!

R.e. identifying newly updated blogs; does .72 have this functionality?