Back up your databases!: See the new MySQL, SQLite, and BerkeleyDB instructions...

A curious omission there makes me wonder if the reason why I never got any replies to my semi-annual question about recentlycommentedon and postgres is because you're dropping support for postgres.

Are you?

Not in the least! The honest truth is that I was the one who wrote up all of the backup instructions while everyone else was going a million miles an hour doing their jobs, and I don't know the first thing about Postgres. There's an entry in draft that says nothing more than:

???????????

I am going to have one of the engineers write it up on Monday. No conspiracy theories there. That's just how it goes with Beta docs. :-)

Installed fresh and running sweet. I can't seem to break it. :)

Running smoot. You guys must have done a lot of optimisation on the code, cos it's smokin :)

Is backing up using the export feature not enough anymore?

is the "offset" feature for MTEntries working for anyone else?

Is backing up using the export feature not enough anymore?

The export feature is as it has always been. It backs up entries, comments and TrackBacks from a single blog. It doesn't preserve your configuration or templates.

Backing up your database preserves the whole installation so that you can roll back to exactly what you had when you backed up.

I'm surprised it was considered a bug that notification was sent for junk email. I guess I don't get a lot of spam, but I liked knowing that I'd received junk so that I could check and make sure it really was junk. Now I'm afraid real comments will languish in my junk bin for days.

Great work on all this. I've been really pleasantly surprised at how few bugs even the nightly builds had.

Thanks Matt. You wouldn't be so happy to receive notifications of junk if you got a lot. I get over 500 per day and was absolutely floored to log in and get all those emails. It reminded me of the early days before MT-Blacklist.

That's what I figured. Maybe 3.3 can have a toggle button for junk notifications?

I make no guarantee, but for Postgres:

pg_dump -U USERNAME DBNAME > FILENAME

That's the command I use to backup my database. I haven't had to restore from it yet, so I'm not positive it's correct, but a quick scan of the file looks fine to me.

Anyway I was just being cranky. It's one of those weekends.

FYI, if you run your postgres backups directly from the postgresql user on the system, I'm fairly certain you can use something like this:

/usr/local/pgsql/bin/pg_dump communique > /usr/local/pgsql/backups/communique.bak

(Same as above, but without the username argument. That's how I run my twice-daly DB backups anyway. And I did have to make use of them once when my Mom hosed her entire blog via the "search and replace" within the CMS.)

Sigh. One of those weekends. That should have used placeholders for databsename and filename, but of course it didn't.

Not that it's too important, but the default stylesheet comments say HOSE where I believe they out to say HOUSE.

This release fixed the problem I was having with not being able to manage comments in beta 2, so hoorah!

Ack. You guys gotta check how the stylesheet and other templates are linked in the header and sidebar. Right now they're linked by filename instead of template name. Got a few extra grey hairs on that account ;P

I get follow message when 1st entry

Building entry 'blog4�エントリ' failed: Build error in template 'Individual Entry Archive': Error in tag: Can't find template 'styles-site.css'

AS Is this a new blog from beta 4 with the dafault templates?

If the case, look through the templates and see if the stylesheet is linked correctly.

Hey Jay,

This beta fixed that thumbnail creation I was having with the archives folder! Weeeew!

I love the improvements you've made to Spam Lookup, especially the addition of credits for URLs or email addresses that have been published in previous comments, and giving specific demerits to specific keywords. You have enough user configurability here that the system might moderate most spam without any significant help from me. I appreciate that!

I'm still using Beta 3, and have a quick question regarding dynamic templates. I never used this feature prior to installing Beta 3, and noticed that this feature seems to only work when updating the template within MT, and not when updating a linked template.

Is this a bug, or just a current limitation of the feature?

Thanks.

This may be more of a support issue... I can "trust" certain commenters by selecting their comment and doing "More actions, trust commenter". Commenters can also be "authenticated" through Typekey. I can view a list of "authenticated" commenters, but I don't see a way to view a list of "trusted" commenters, and marking them as trusted does not make them show up on the authenticated list (MT seems to maintain a distinction between the two classes). How do I see who I've marked as trusted?

Charlie: on the commenters listing, there is a "Filter:" line at the top. Click the hyperlink on the right of that to display the filter controls. You can change that to show only trusted commenters. You can also click on the "trusted" status icon of an existing trusted commenter to do the same filter.

Ok, I see that. The trouble is that no matter how I filter, no commenters are shown on the commenter list. It's empty whether showing all or some filtered set. I assume the commenters list pulls its data from the list of comments... I can go to commenter A, select, choose to "trust" him, but his name doesn't appear on the list. I doubt this is a bug. Is there a setting that can prevent commenters from showing up?

Hey Charlie, this sounds like a user support problem. You may want to post over here with links to screenshots of what you're talking about. I have a feeling that you're trying to trust unauthenticated commenters which, of course, doesn't work.

Thanks. I'll do it. Why is trusting unauthenticated commenters an "of course it doesn't work" issue? Does that mean I can't choose to trust someone if they haven't been authenticated by Typekey?

Why is trusting unauthenticated commenters an "of course it doesn't work" issue? Does that mean I can't choose to trust someone if they haven't been authenticated by Typekey?

Because it's based on authenticated identity. Authenticated ID is mapped to a person. A name and email address is mapped to letters on a screen that anyone can type in. There are (and will be) plugins available for whitelisting and blacklisting commenters by such random and mutable properties like their Name or Email Address, but that's not a solid foundation for "Trust".

That helps. As Reagan famously said, "Trust, but verify."

Hi Jay, I'm encountering the same issue as Charlie. I think this is a UI problem. It isn't clear that "Trusted" is a subset of "Authenticated. In fact, on my MT 3.2 blog I have "Immediately publish comments from" set up for "trusted commenters only". I have not set up any authentication, because I didn't think I needed any.

The result is that one someone goes to comment, they get the following message: "I have enabled a feature that allows your comments to be held for approval the first time you post a comment." The problem is that their comments always have to be approved, because I haven't enabled authentication.

I suggest graying out the "Trusted" box on the feedback settings until the authenticaiton is selected and token placed.