...more recent posts
Well, I've done a lot of testing and I can't get any of these comment problems to happen again. But I saw some happen yesterday (in the wild, as it were) so I know that something is up. I'll keep looking.
Did somebody say something about having to scroll down on the /settings page before you see any text? That doesn't sound right. Can someone confirm this with browser/OS information?
Does this happen on any other pages?
Thanks.
There are definitely some problems with the [x new comment] counters. This is a result of some new capabilities (yeah, I know) that were just added. I'll get this all straightened out by tomorrow. If anybody notices they make a comment that then doesn't show up, please write to me with the following info:
Did you post from a comment box on the comment page itself, or did you add the comment from a posting page that only contained a posting box (and no comments)?
Did you post directly as a comment, or did you use the new 'preview' feature?
Thanks.
I have not done serious testing, but I believe that preview mode now works for comments. There could well be errors (with the [x comments] comment counters, or the [x new comment] counters on the front page.) Please let me know if you think something is funky.
Also, there is a new page /settings where you can make some adjustments. More options are coming. Right now you can use /settings to manually zero all your new post/comment tracking counters. Plus you can assign a pixel dimension for all your posting boxes. Plus you can set a default behavior for converting line breaks to HTML (you can either have this default to on - checked - as it does now, or you can switch it to always default to off.) Also you can turn off or on the options of preview and pending (future) posts.
I'm sure this is confusing. Any help with the language that might make these options clearer is much appreciated. Also ideas for other settings.
Fixed the problem with "use your own HTML" pages not recording hits for the referer log. Tom brought this to my attention and it turned out to be a little more difficult to track down than I had thought. Turns out that those pages were correctly recording hits, except in the situation where all the content is just put into the template (and nothing is [post]ed.) This turns out to be a reasonable way to build these pages, but it isn't the way I had in mind when I designed it. The original idea is that the format and graphic design elements would be entered on [editpage] into the HTML field, but that you would still post the "real" content through [post].
In any case, it works fine just to make the entire page inside the template. Hits will now record. The only possible draw back is that the search engine won't find text on that page.
Fixed, finally, the 2002 archive bug. This caused problems with the framed view of the archives for sure. Not sure about the regular view. In any case this will be a problem again after 12/31/2012 but if we are still using this code base then this will be the least of our problems.
Well, I was all set to order the new server and put it at he.net when they send me an email announcing that all of their virtual host accounts (that's what we have now - where you share a server with a bunch of other people but it looks to you like you're the only one on it) have been expanded. So as of this month we have twice the storage space and a great deal more bandwidth for the same price.
I still want my own machine, but now that there is less urgency I can't pull the trigger. I'm learning a lot of unix by working in OSX so I'm steeling myself to tackle the server I bought last year but never really used. If I can get linux and everything else running on that box, and can convince myself that it is reasonably stable, then I will just ship that one off. This will be about half the cost of having them manage a machine for me. Of course if something goes wrong it will be my fault instead of theirs.
Not sure what to do. I almost wish they hadn't sweetened the deal. In any case, upload away.
Yeah, the archive broke at midnight. Well, not really broke, but 2002 is not working. I thought that might happen, but I didn't look into it in time. I'll fix it later today when I get my head back.
Our host hurricane electric has a new web based front end for their email systems. I have enabled it if anyone is interested. I'm still working on my own system that will be much more tightly integrated into the tree, but for now this might come in handy - especially if you are traveling, or don't have much control over configuring email software at work.
Anyway, go to /webmail and enter your name and password. Your name is what comes before the @ in your digitalmediatree.com email address. So my name (for my mail account jimb@digitalmediatree.com) is jimb and my password is the password I use to check my mail (not the password I use to /login to digitalmediatree.)
If you don't have a digitalmediatree.com mail address and would like one, let me know. Also I can set the account to bounce all incoming mail to another email address in case you want the dmtree address, but want mail sent to it to show up in your regular (non-dmtree) mail account.
There was a end of the year date bug screwing up the framed archive view. Since December 1 I'm sure, although I just saw it. Fixed now.
I don't think anyone has been playing around with it, but there was a problem with the new comment styles. If you changed the comment style in [editpage] it would retroactively change all existing threads to the new style, but additional posts added after the change to [editpage] would revert to the old style. This has been fixed.