MoonPoint Support Logo

 


Shop Amazon Warehouse Deals - Deep Discounts on Open-box and Used ProductsAmazon Warehouse Deals



Advanced Search
July
Sun Mon Tue Wed Thu Fri Sat
         
25
           
2005
Months
Jul


Mon, Jul 25, 2005 10:44 pm

Blosxom Calendar Plugin Bug

I use Blosxom for my blog and the Blosxom Calendar Plugin to add a calendar to the blog. I installed version 0.6i of the plugin on August 30, 2004. Today, I noticed that if I click on the path link at the bottom of an entry where the path has a directory as part of the path with a name beginning with a number, clicking on that link generates the internal server error shown below.

Server error!


    The server encountered an internal error and was 
    unable to complete your request.


    Error message:
    Premature end of script headers: blosxom


If you think this is a server error, please contact
the webmaster


Error 500

When I looked in the site's error log, I found the following.

[Mon Jul 25 19:18:21 2005] [error] [client 162.83.13.120] Cannot handle date (0, 0, 0, 1, 11, 2800) at /support/blog/plugins/calendar line 214, referer: http://support.moonpoint.com/blog/blosxom/index.html?find=Dell&plugin=find&path=

When I checked line 214 in the calendar plugin I saw the following.

$monthstart = timelocal(0,0,0,1,$month-1,$year-1900);

The problem appears to be triggered whenever there is a directory with the directory name starting with a number in part of the path. I had a directory with /pc/hardware/dell/4700 as part of the path. I renamed the 4700 directory to d4700 and the problem went away. I changed it to 4700d and the problem reoccurred. I changed it to 3800 and the problem remained. Since I didn't have time to carefully examine the code in the calendar plugin, I finally just changed the directory to dimension_4700 and left it at that.

I thought there might be a later version of the plug-in at the developer's website, but the 0.6i version is the one still posted there.

[/network/web/blogging/blosxom] permanent link

Mon, Jul 25, 2005 8:50 pm

ht://Dig Setup

I installed ht://Dig because I thought I had placed certain information on my website, which I waned to refer to again, but couldn't locate it. I have a search tool for the blog, but that will only search the blog's content. Since I couldn't find the information with that tool, I thought I might have placed the information in a file or files that weren't part of the blog's entries. So I installed htdig and used it to search the entire site. I still couldn't find the information, though I can recall creating a webpage with the information.

Oh well, I'll just have to keep looking or figure out how to do what I need to do again. One of the reasons I created the blog was to serve as a reference when my memory fails me on how I resolved a problem in the past. But, if I didn't post the information here, it's going to take me much longer to locate it or figure out again the steps I took previously.

So I won't have that problem with installing htdig again, I've posted my notes in the blog. Hopefully, it might help someone else as well in resolving problems or answering questions about setting it up so it can be used with multiple websites on the same server.

[ More Info ]

[/network/web/tools/search] permanent link

Mon, Jul 25, 2005 5:00 pm

Russia's Biggest Spammer Murdered

An article titled Russia.s Biggest Spammer Brutally Murdered in Apartment appeared in MosNews today. The article states that the man considered to be Russia's biggest spammer was found brutally murdered in his apartment on Sunday from repeated blows to the head.

Vardan Kushnir, 35, headed the Center for American English, the New York Engish Centre, and the Centre for Spoken English, which sent millions of email messages every day.

According to the article, under Russian law spamming is not illegal, but Russian lawmakers are working on anti-spam measures.

[/network/email/spam] permanent link

Once You Know, You Newegg AliExpress by Alibaba.com

Shop Amazon Local - Subscribe to Deals in Your Neighborhood

Valid HTML 4.01 Transitional

Privacy Policy   Contact

Blosxom logo