TweezerMan

Welcome to the forums, Mike!

Welcome to the forums, winfixer!

Try this code out and see if it works for you: >use DateTime; open(FILE, ">>$log_file"); my $dt = DateTime->now(time_zone => 'America/Chicago'); if ($password ne "xxxx") { print FILE $dt->strftime("%m/%d %H:%M") . " $password $ENV{'REMOTE_ADDR'}\n"; close(FILE);

It sounds to me like the .shtml file extension has been associated with Firefox, so when you tell Windows (which includes Internet Explorer) to open a .shtml file, Windows will use Firefox to open the file. Open Windows Explorer, and on the menu, click "Tools", then "Folder Options...". Click the "File Types" tab, and scroll down the list and see if SHTML is in the list. If so, click on it with your mouse and see what program Windows shows for "Opens with" below the list. If Firefox is shown, you should be able to change it by clicking on the "Change" button and selecting Internet Explorer.

You should look at the "Http Code" for these entries. If access is indeed being blocked by your .htaccess file, the "Http Code" should be 403 (which is the HTTP status code for 'Forbidden'). The "Size in Bytes" doesn't necessarily have to be ("-"), as the server can serve a custom 403 error page in response.

Not that I'm aware of. Upload it to your server in your /public_html directory, with a name like time.php, then go to http://your-TCH-domain.com/time.php in your browser.

What other way would you like? I believe the FTP server is displaying file date/times in UTC. The U.S. Central timezone is UTC-6, so files would appear to have date/times 6 hours later than your local time. The 'Keep File Time' check box uses the MDTM FTP command to sychronize the file times, and yes, this only works for files downloaded from the server. The spec for the MDTM command does not allow it set the time on files uploaded to the server.

Adding headers (such as 'Cache-Control') with a Header directive in your .htaccess file requires the mod_headers module to be loaded on the server. From what I can tell. the mod_headers module is not loaded on TCH servers (it is not on mine), so you would not be able to use this method to send a Cache-Control header.

Welcome to the forums, dscotese! I believe this line is your problem: >SetEnvIf Host ".*(www\.litmocracy\.com).*" GoodHost The server variable HOST will contain the domain name that is serving the page. Assuming that www.litmocracy.com is in fact the domain name for your site, HOST will always contain 'www.litmocracy.com', and the environment variable 'GoodHost' will always be set. The 'order deny,allow' line in your .htaccess file tells the web server to process all Deny directives first, then process all Allow directives. A request that does not match any Deny directive, or does match an Allow directive, will be granted access to view your site. With the following Allow directive in your .htaccess file: >allow from env=GoodHost ...and the fact that GoodHost will be set on every page request, every page request will be allowed on your site (i.e. no one will be blocked). I'm not sure what purpose the 'SetEnvIf Host' directive serves in your .htaccess file, so I'd suggest removing it.

I believe the problem stems from your use of the datetime module: >import datetime From what I've found on Google, the datetime module is a new module added in Python version 2.3. The last time I checked, my server (and I presume all other TCH servers) were running Python 2.2.3, so the datetime module would not be an available module for python scripts to use. Hope this helps...

I'm seeing "WordPress database error: [Got error 28 from table handler]" at the top of the page. See this WordPress troubleshooting FAQ on "MySQL Error 28". Bottom line: You should submit a ticket to the Help Desk and have them check the free space for /tmp on the server.

Step 3 of the instructions you linked to discusses adding a hidden "Template" form field to the search form on your weblog. You've done this on the search form that appears in your weblog's sidebar: ><input type="hidden" name="Template" value="aftertastebliss" /> Searches submitted from the search form on your weblog page will have the results displayed with your alternate template. However, the alternate template also has its own separate search form code. (As you've noted, it's what displays 'the new search bar that appears at the top of the page'.) If you want 2nd and subsequent searches to also use your alternate template to display search results, you need to add the above hidden field to the search form that's in the alternate search template. All searches are executed and displayed by mt-search.cgi, and CGI scripts don't process PHP code. There's no way for an alternate template to have any kind of PHP code that would get executed when a search is performed.

Welcome to the forums, d.a.n!

Welcome to the forums, AwwYouDead!

Welcome to the forums, nayner!

I'm not sure where server 87 is located, but you can try running the following PHP script and see if it gives you the info you're looking for: ><?php echo 'The current server time is ' . date('D d M Y h:i:s A T'); ?> On my server, the script outputs the following:

Welcome to the forums, Oudie! You need to submit a ticket to the Help Desk and ask them to recompile PHP with all of the options normally used on TCH servers. Looking at phpinfo() on your server, the 'Configure Command' section only shows the following: The server hosting my account shows the following: The '--with-gd' option missing from your server's PHP configure command is why GD functions do not work on your server. The Help Desk should be able to quickly take care of this once you bring it to their attention.

This part of your query does not look like it's constructed correctly: >$db->time(time(, '$card')) The time() function doesn't take any parameters. If $db->time accepts two parameters (I don't know if it does or not), then it would appear that the closing parenthesis for the time() function was misplaced at the end of the $db->time function: >$db->time(time(), '$card')

Welcome to the forums, lbriseid!

Welcome to the forums, timmy!

Welcome to the forums, Bigg-Birdd-VA! The documentation that you're looking at appears to be from an older version of Mailman. It looks to me like the option you're looking for is 'generic_nonmember_action', on the "Privacy Options" / "Sender filters" page: Actions available are Accept, Hold, Reject (bounce), and Discard. If you choose Discard, you may want to set the following option "forward_auto_discards" to "No". Hope this helps...

In your CPanel, under 'Cron Jobs', the "Advanced (Unix Style)" button provides a view that is pretty close to what crontab would display.

As far as I know, the Help Desk would have that for you. While it is possible that the cron daemon may not be running, I don't believe it is likely. If you submit a ticket to the Help Desk, you should tell them that your cron job does not appear to be running and ask them if they can determine why (don't just ask them if the cron daemon is running).

You'd need to submit a ticket to the Help Desk and have them investigate it. There is a cron daemon that runs cron jobs on the server. If it's not running, cron jobs don't get run. Could be either one, unless you know that your script does produce output which should have resulted in an e-mail from cron.

Welcome to the forums, xlagoon! Are there any error messages recorded in the CPanel Error Log?