For a while now you have been able to insert <more> into your posts to have the system automatically display only the text before the tag on your blog, while automatically adding a 'Read the rest of this post...' link to go to the full post (although this only works if you have comments enabled on your blog since it uses the comment view to display the full post.)
Now, in addition to <more> you can also use <fpmore>. This will do what <more> does for your posts, but only on the front page view of your post, not on your actual blog (i.e., your post will be truncated on the front page, but will show the full post on your blog.)
Not sure how useful, but I didn't want to clog up the front page with my recent long posts. So there you go.
We lost the drive that holds digitalmediatree. I have restored from a backup. Nothing should have been lost from the database, but unfortunately the image directory hadn't been backed up since 11/22. So all images uploaded since then are gone. I'm still trying to recover those, but not sure if I can or not. Will keep you posted. Probably there will be some weirdness since we are now operating out of a different directory (on a different drive) and I might have some paths hard coded in the scripts (not sure.) Just let me know what doesn't work and I'll fix it. Sorry for the outage. Welcome back.
I think I found the problem where we are getting large spam threads on certain pages where the parent post doesn't even exist on that page. Very weird. Must be robots just throwing random information into their POST variables. Mainly I'm posting here so I can comment and make sure I haven't stopped legitimate comments too.
Made some changes on the back end last night. The site was down for 2 or 3 minutes around 9:00pm and then again around 1:30am. You shouldn't notice any difference, but please speak up if you see anything amiss. Thanks.
Site was unreachable just now (well, 2 minutes ago) when I returned from Long Island. I was getting it around 1:30 just before lunch and our departure. Anyone else notice this? For how long?
The server was up, but just completely overloaded. Not sure if it was a traffic burst from somewhere or just something gone haywire. Seems okay now.
Image upload is back. Sorry about that.
subscriptions weren't working. Now they are.
I'll move the server move discussions to here where they really should have been.
[editpage] should now be working again. Any reports to the contrary are appreciated. As well as any reports of other weirdness. I'm pretty sure there are still some bugs out there.
The site was down again. I noticed around 7:30am, but traffic logs are a bit unclear and it might have been down for most of the night. Not sure what the story was, but a reboot and an fsck later and everything seems fine. I'll get this site moved to the new server one of these days.
Sorry about the logs being down for so long. The problem is very time consuming to fix because there are 1,125,435 rows in the table and it's been corrupted at various places, so I can't do a select all on it. I fixed the comment table (which had the same corruption) by going through it by hand and pulling out the corrupt entries, but that table only had tens of thousands of rows. So that was a pain, but at least possible. With over a million rows I just can't do it by hand. I'm trying to write a program, but it's proven difficult because of the corruption.
Anyway, that's my excuse. For the present I have just started the log over again. I should have done this before. I still have the old data, and I'm still trying to fix it, but at least you can see your log again now - it's just that it starts from a few minutes ago, so you'll only see data going forward.