Hi r.a.b. - it ought to be pretty painless migrating from Frog 0.9.5 to Wolf 0.5.5 (you would need to start there, not with 0.6.0, of course). I recently moved the last of my Frog sites -- I was holding off, because it was still on 0.9.3! But in the end, it was seamless, and now it's running happily on a fresh Wolf install. I couldn't face recreating things, even though much smaller than what you're dealing with, but the db steps were flawless, and everything (and everyone!) is very happy indeed.
It looks like you've been reading the wiki already, so just a few additional remarks here:
radioactiveblue wrote:. . . I'd like to move to a professional host -- can anyone recommend a Wolf-friendly host, or know who to avoid?
A lot depends on budget, location, etc. At the inexpensive end is Byethost (astonishingly good feature set, astonishingly good support, all for ... free!), and also at the less expensive end is A Small Orange. To avoid? 1and1 has been a problem, so too MediaTemple -- I believe these are still serving up PHP4 which is death to Wolf! A rule of thumb, then, would be to avoid hosts who are maintaining deprecated versions of PHP!
Other suggestions will be made, I'm sure. (Perhaps if you're considering a certain host, you can ask for experiences of them here?)
Would the best approach be to install a new version of Wolf on the new host and port the data across from my MySQL database, or would it be better to set up the Frog and follow the upgrade instructions?
Since you're running Frog 0.9.5 at the moment, it's a 1-for-1 swap to Wolf 0.5.5. So I would go ahead and install Wolf on the new host, and bring in your mySQL database. There are some threads around on moving sites, although I'm not sure there's anything in the wiki at the moment on that. Hard-coded links would have to be updated, of course, and it might be easier to do a search-and-replace on the mySQL dump before importing it to the new site.
Also, does Wolf have an extension for the admin interface to tile the child nodes in an archive so it only displays N pages at a time (if not, how difficult it would be to write one)? I have almost a thousand pages under one of my archives, so it's not great when it's expanded.
Ah, the old "paging-in-the-admin" question! At the moment, the extension you describe doesn't exist. Limiting page display could be done different ways. One is to paginate it all, which is what you seem to be describing. Another might be to have the option of selectively applying a filter (e.g., all "descendent" pages created in the last four weeks only).
Well, those are a few quick thoughts. I'm sure this is a sensible move, not just because I'm partisan (!), but because Wolf has developed significantly since the fork (including numerous security measures), and will continue to do so.
