TweezerMan

I've fixed it - thanks! The "string" being printed is enclosed by backquotes (the character left of the '1' key on your keyboard). The string in backquotes is executed as a command on the server, and the results of that command (its output) is what's printed to the browser. <{POST_SNAPBACK}> Somewhere along the way, the double quotes in the script code were converted to curly quotes, which don't work in a script. I've edited the script above and replaced the curly quotes with 'straight' double quotes. It should work a lot better now.

You are checking the 'Remember Me' box when you log in, right? The first thing I'd look at is the cookie settings in the browser: 1) In Firefox, click 'Tools', then 'Options' on the menu. Click 'Privacy' in the left column, the click 'Cookies' to expand the options if it's not already. Check the 'Keep Cookies' option - is it set to 'until they expire', or is it set to 'until I close Firefox'? 2) In Internet Explorer, click 'Tools', then 'Internet Options...' on the menu. Click on the 'Privacy' tab. There may be a slider bar on the left, allowing you to select different levels of privacy. The default is 'Medium', which includes 'Restricts first-party cookies that use personally identifiable information without implicit consent'. One option is to click the 'Sites' button, enter 'www.totalchoicehosting.com' and click the 'Allow' button to always accept cookies regardless of the privacy policy. What I usually do instead is click the 'Advanced' button and select the following options: 1) Override automatic cookie handling 2) Accept first-party cookies 3) Block third-party cookies 4) Always allow session cookies If your browsers are already configured correctly to save cookies, I'd suspect that a third-party firewall or cookie blocking/managing program is running on the computer and determining on its own whether cookies will be session cookies or not. Hope this helps...

The only thing I can figure is that the command line version of PHP is not built the same as the web server version, or there's some options that aren't the same between the two versions. You could try running the following script: ><?php phpinfo(); ?> ...from both a browser window and a cron job, then compare them and see if there's any significant differences (particularly in the 'GD' section). Other than that, I think you'd need to get the Help Desk to take a look at your server and see if they can tell what's wrong.

You might check the Error Log in CPanel and see if a message indicating what the problem is was recorded there.

Welcome to the forums, Aaron!

The path you'd need to use for a subfolder in your public_html directory would be: >/home/cpanelName/public_html/my_sub_folder ...where 'cpanelName' is your CPanel username, and 'my_sub_folder' is the name of the subfolder you created. I don't know if that totally answers your question, but I hope it helps!

Welcome to the forums, WeBrain! My first guess would be that you need to modify the 'require_once("config.php");' line in the script to reference the actual location where you put config.php. For example: >require_once("/home/cpanelName/config.php");

Welcome to the forums, dssnm!

You should use 'ftp.clearlakevolleyball.com' for 'Server' in your FTP program. Your IP address may have been blocked due to an incorrect password being entered too many times. If this is the case, you'd need to submit a ticket to the Help Desk to get it unblocked.

I extracted the HasGDInstalled() and HasFunctions() functions from postie-functions.php and put them into my own little test script: ><?php function HasGDInstalled($display = true) { $function_list = array("getimagesize", "imagecreatefromjpeg", "imagecreatefromgif", "imagecreatefrompng", "imagecreatetruecolor", "imagecreatetruecolor", "imagecopyresized", "imagejpeg", "imagedestroy"); return(HasFunctions($function_list,$display)); } /** * Handles verifing that a list of functions exists * @return boolean * @param array */ function HasFunctions($function_list,$display = true) { foreach ($function_list as $function) { if (!function_exists($function)) { /* if ($display) { print("<p>Missing $function"); } */ return(false); } } return(true); } echo HasGDInstalled(); ?> On my server, this script displays 1 (true), indicating that all of the functions listed in the HasGDInstalled() function are available. If this script indicates that 'imagecreatefromgif' is missing (not available) when run on your server, the only explanation I can think of is that one or more of the underlying GD libraries required for GIF support is not installed. I wouldn't recommend doing that. My suggestions from here would be to try running the test script I have above. If it indicates that something is missing from GD, I think your options would be 1) open a Help Desk ticket and ask them to investigate, or 2) configure the Postie plugin to use ImageMagick instead of GD to resize your images (set 'Use ImageMagick' to 'Yes').

Welcome to the forums, bombadil!

This isn't really a python problem. In any script that is outputting to a web browser, there has to be a blank line separating any HTTP header lines from the actual page content (that's how the web server knows where the HTTP header ends and the page content starts). Your script works correctly (no 500 error) if you add an extra 'print' command as I have it below: >#!/usr/bin/python # Filename: test.py length = 5 breadth = 2 area = length * breadth print 'Content-Type: text/html' print print 'Area is', area print 'Perimeter is', 2 * (length + breadth)

Welcome to the forums, goldberry31!

I don't really know for sure, but it doesn't sound to me like something that should be there, and I'd probably remove it.

You can set up a secure URL for mt.cgi by adding the AdminCGIPath setting to your mt.cfg file. Example: >CGIPath http://www.my-TCH-domain.com/mt/ AdminCGIPath https://www.my-TCH-domain.com/mt/

I set up a WP install from scratch, created an e-mail account for the Postie plugin to use, and installed the Postie plugin per the instructions. I set up the cron job a little differently than what the instructions recommend though: 1) I set the permissions on wp-content/plugins/postie/get_mail.php to 0755 so it could be executed directly, as get_mail.php has a proper shebang line at the beginning of the script: >#!/usr/bin/php -q 2) I used the following as the 'Command to run' in the cron job: >/home/cpanelName/public_html/wp-content/plugins/postie/get_mail.php >/dev/null 2>&1 a) No 'php -q', since that's in the get_mail.php script already. b) No '~' shortcut for the '/home/cpanelName' directory. c) Replace 'cpanelName' with your CPanel username. I ran get_mail.php in a cron job a few times with test e-mails I sent to the appropriate e-mail account, and it successfully created thumbnails from the pictures I attached as expected. I did not have to modify the get_mail.php script at all. If the script can't find GD on the server, I would suspect that GD is not installed on the server. I don't think this is likely, but it's not hard to check. (You can run a script with the phpinfo() function in it, or you can browse to http://serverXX.totalchoicehosting.com/phpInfo.php, where 'XX' is your server number.) I would suggest going over the Postie plugin settings again and make sure you have its settings configured properly (such as 'Resize Large Images' set to 'Yes'). Also, check the size of the images you're attaching to your e-mails - the width of the image must be greater than the 'Maximum Image Width' setting (default: 400px) in order for a thumbnail to be created.

Yes, having two domains with different content does require two separate virtual hosting accounts, or that you upgrade to a reseller account. MT does not really offer any practical way to extract one weblog's data, templates, settings, etc., from an installation with multiple weblogs. There's going to be two parts to migrating your second weblog to a new account: 1) Migrating data from your MT database, and 2) Migrating uploaded files on the server. What I would probably do is export the MT database using phpMyAdmin in CPanel. This will produce an export file containing both of your weblogs. I would then import the database into the second domain's account, again using phpMyAdmin in CPanel. After installing and configuring MT on the second domain, and importing the MT database into the second domain, I'd log into MT on the second domain and delete the first domain's weblog, leaving you just the second weblog you want to use on the new second domain. This process will migrate your entries, comments, trackbacks, templates, and weblog settings without any loss. Once you're sure everything is migrated and set up correctly, you can then delete the second weblog from the first domain's MT installation, leaving one MT weblog on each domain. If you have any files you've uploaded to the server for the second weblog, such as image files, you'd need to copy those from the first domain over to the second domain (download them via FTP from the first domain, then upload them via FTP to the second domain). You don't need to migrate the actual MT weblog pages from the first domain - they can be recreated on the second domain by doing a full rebuild once you have the second weblog up and running on the second domain. The Help Desk should be able to copy your MT database from your first domain to your second domain if you want them to. You'd still need to install and configure MT on the new domain, and delete the first weblog from the new domain's installation of MT once you have everything set up. The Help Desk could probably also copy any files you need from the first domain to your new domain, if you can clearly explain which files need to be copied. Hope this helps...

Welcome to the forums, haebby! My first guess would be that there may be a problem with the script not being run from the same directory the script is located in. I would suggest adding the following code to the very beginning of get_mail.php, just after the '<?php' line: >chdir(dirname($_SERVER['argv'][0])); If that doesn't solve your problem, you're going to need some sort of error message to give a hint as to what the problem is. There is a lot of code and it's not immediately apparent where a problem like this could be coming from. I'd suggest sending a test e-mail to your account, then modify your cron job command to not send its output to /dev/null: >php -q ~/public_html/wp-content/plugins/postie/get_mail.php 2>&1 When the cron job runs, you *will* get an e-mail containing output from the script. Hopefully there would be one or more error messages within the output that would tell you what the problem is. Hope this helps...

Welcome to the forums, taranicole1988!

Welcome to the forums, rappeto!

Welcome to the forums, Sandra!

Welcome to the forums, Princess Paw Paw!

Welcome to the forums, Michael!

Welcome to the forums, teacka!

Welcome to the forums, jkmccabe! I hope you enjoy your new reseller account!