unoamigo

Lets just wait a bit and see where it goes. It’s awfully preemptive to get excited/angry/upset about something in development.
If the release candidate comes out and things are really borked, then I’m sure Matt & Ryan will be quite happy to take 1.3 back into development and work on getting 1.3 right the first time – instead of with 1.4.

Run 1.2 and one or more of the comment moderation/spam monitoring plugins.
If your looking to do a serious blog with serious content and readers, then your not going to want to spend a lot of time mucking around with in development code.

It amazes me that people are demanding answers and how to descriptions on in development software. It wouldn’t be fair to even begin to describe 1.3 as beta ready.
Let the devs keep working on it rather than spending lots of time trying to answer everyones questions on *how* to use it. If your wanting to play with it now, I think it’s safe to say that you should be prepared to spend a good amount of time digging around and learning. And then, all that work might be for naught because the devs could decide on a better way to do something or can features and modifications alltogether.
On the other hand, it would be nice if the CVS notes had a little more detail to them. Many of them are pretty well useless. If Matt and Ryan would be so kind to spend a couple minutes typing up notes to their commits, I sure would be grateful. Might also help to curb some of this anger floating around…
This is turning into chaos, everyone is wanting to run 1.3 now and know how to use it. It’s crazy because it has been this way since 1.2 was a release candidate. Long before a single line of code was even written for 1.3.
Can’t we all just relax a just little bit?

Whew sorry. The whole living out of a tent thing takes a toll on my ability to respond – quickly.
Podz, I haven’t played too much with 1.3 (yet). I’m just starting to. It looks as though 1.3 is going to add some nifty new page set up functionality. This I’m sure is going to inevitably effect how one will ideally want to run the statistics package.
It looks to me like you will be able to create a new page called “stats” and insert the call to the stats package. This will invariably make /stats/ available. If I’m understanding correctly. The version from a week or so ago that I downloaded – this wasn’t entirely functional yet. I think this will be the way that the stats package should be run on 1.3. When I get a chance, I’ll ad some more info.
sdollen – the install directions included explain how to get it up and running. Were actually just wrapping an if statement around the wordpress loop

Doesn’t seem like it should… But you can give it a swing and see what happens.

Installing WordPress is pretty easy and the cms as a whole is very lightweight. Multiple installs are not a problem and fairly quick to do.
Don’t expect multiple blogs with one install in the next release…

No, not really. You can edit the timestamp on each post though.
With some work you could probably add some php into your index file specific to each user – to note the different time zone. I doubt that it would be worth the effort.

Rev6k, can you link your page. It helps a lot.

Looks good to me. Welcome to WordPress! ??

Cool, now you just need a script to do it automatically based on CVS.
That way we can have the latest and greatest. ??

Yeah, I’ve been a bit distracted with a job hunt at the moment. That is a known bug that I intend to squelch with a couple other little updates – which basically consist of a few options I wrote in to use on my own site.
Until then, please be patient.

Right now I don’t have a lot of time.
I haven’t experienced the problems your talking about… I’ll do some testing.
What other plugins are you using? It is potentially possible that something is conflicting with it.
Can you elaborate on #2 a little bit more.

I’m going to make a random guess here. See what happens when you run:
wp-admin/upgrade.php
If I’m remembering right, it will go through and make sure everything is set right.
Sorry I don’t have time to look up the details and write up a bit of SQL for you. Maybe someone else will…

Very enjoyable!

The title length is unlimited. You could have 1,000 words in your title and it wouldn’t matter.
I about have a plugin written that checks it and pops up an alert if the title length is too long. Well, it checks the length, but the alert box isn’t popping up at the moment.
You would have to go back and edit the title to make it shorter… with what I’m doing. But hey, it’s something. As soon as I figure out how to get the alert to pop up (it’s weird), I’ll post the plugin. Unless your happy getting an e-mail that says the post title is too long? That is easy. ??