TweezerMan

If you'd just like to make the error messages go away, you should be able to do so by lowering PHP's error reporting level so 'notice' warnings are not logged. In your php.ini file, you can use the following: >error_reporting E_ALL & ~E_NOTICE Or, in your httpd.conf file or an .htaccess file, you could use this instead: >php_value error_reporting 2039 This is actually the normal 'default' setting for error reporting, so this should give you the same behavior as what you would see on a production server.

What program and what mode (ASCII/BINARY) are you using to upload the files? I'm wondering if you're experiencing the same issue you had the last time you were getting these errors. .tar.gz and .zip files need to be uploaded to the server in BINARY mode. For MT 3.2, files in the /mt-static/images directory and all subdirectories need to be uploaded to the server in BINARY mode. All other MT 3.2 files need to be uploaded to the server in ASCII mode. If you've been relying on any sort of auto-detect in your FTP program to choose what mode the files are uploaded in, I'd suggest that it's not working and you should manually select the upload mode as I've indicated above. There is no program to 'check' the scripts.

I don't know much about python or what it is installed with on TCH servers, so the only suggestion I have at this point is to submit a ticket to the Help Desk and ask them about it.

Welcome to the forums, Lawrence!

Welcome to the forums, Benny!

If you want PHP to be able to create files in the cache directory, it will need to have 0777 permissions. The 'Undefined index:' errors are not Apache errors - they're errors in the PHP code. (That's why the error messages begin with 'PHP Notice:'.) 'Undefined index' in this context means 'undefined array index'. The fix for the first error appears to be here (Skyzyx Support Forums). Another user appears to have posted fixes addressing many of the other errors you're receiving here.

MT no longer appears to be installed where the error message says it is.

Welcome to the forums, codawson! "Unlimited subdomains" in this case means your (reseller) domain is allowed unlimited subdomains. Your customers will be able to have their own unique domain names that are not subdomains of your reseller domain. Your customers may also be allowed to have unlimited subdomains of their own (using their own domain name), if you allow it in your hosting packages. The only ways I'm aware for transferring a web site to TCH is either via FTP or a CPanel site-to-site copy. For FTP, you would have to download your site from the other host, then upload it to the TCH server. TCH does not transfer sites via FTP for you, so there is no fee, although any bandwidth used to upload your site will count against your monthly bandwidth usage. If the other host uses CPanel on their servers, the TCH Help Desk may be able to use CPanel to copy your site from the server at your old host directly to the TCH server. There is no fee for this service - you'd just need to submit a ticket to the Help Desk and ask for it. The cost to transfer a domain to TCH depends on the top level domain (.com, .net, etc.). Prices start at $10.95 and include a one year extension of the domain registration. I don't believe that you have to transfer the domain name to TCH to use it for routing e-mail, but the DNS record would need to be updated so it correctly pointed at the TCH servers. CPanel is very easy to use. (That's one reason for it's popularity.) There is no online demo available to try out - sorry! Each customer that you create an account for will have their own CPanel, separate from yours and any other customers. Hope this helps...

You can check the URL of the referring page by examining the variable $_SERVER['HTTP_REFERER'] in your script.

Any forum members who wish to discuss or inquire about mythusmage's offer should do so privately by PM or e-mail. The BigPAPI plugin can be found on the developer's web site: http://www.staggernation.com/mtplugins/BigPAPI/

Glad to hear you finally got it worked out!

Check the Error Log in your CPanel and see if there is a more specific error message recorded there.

I believe this is OmniStar Mailer, a commercial mailing script. roloff - The bottom line here is that in order to use OmniStar Mailer's responder.php script in a cron job, any code in responder.php, or in scripts included by responder.php, has to be modified to run properly in a non-web server environment. I've looked at the code a couple of times and recommended fixes where I thought there was a problem. OmniStar Mailer has a lot of code though, and as an outsider who is not a licensed user of this commercial software, I'm not sure there is much more than I can do to help you.

I would think that pulling the data through a MySQL query would put more load on the server and take longer to execute that just reading a plain file directly from the disk. MySQL table data is also stored in files on the disk. But to get that data and send it to a browser, the web server must open a connection to the MySQL server, submit a request (MySQL query) for the data, wait for the database server to process the query and retrieve the data, receive the query result from the MySQL server, and finally read the data from the returned query result. You have none of this overhead if you just read the text directly from a file on disk. There may be other reasons why you'd want this data stored in your database instead of in a disk file, but speed/resources wouldn't be one of them.

I agree with TCH-Thomas on submitting a ticket to the Help Desk. If I'm reading that first error message correctly, your script does not have permission to create files in the server's /tmp directory, and this is something the Help Desk would need to fix. The other two errors are caused by the first error, so fixing the first error should fix all three.

Duplicate topics merged. Please do not cross-post the same question to multiple forums. I am not aware of any coupons being offered by TCH for any purchase.

You may have multiple AllowOverride directives in your httpd.conf, each of which applies to a different directory. I'd probably recommend placing AllowOverride directives within each of the VirtualHost blocks you set up for your sites: >NameVirtualHost *:80 <VirtualHost *:80> ServerName localhost DocumentRoot /Users/jeff/Sites <Directory /Users/jeff/Sites> AllowOverride All </Directory> </VirtualHost> <VirtualHost *:80> ServerName lazytiger.local DocumentRoot /Users/jeff/Sites/lazytiger <Directory /Users/jeff/Sites/lazytiger> AllowOverride All </Directory> </VirtualHost> <VirtualHost *:80> ServerName bluestars.local DocumentRoot /Users/jeff/Sites/bluestars <Directory /Users/jeff/Sites/bluestars> AllowOverride All </Directory> </VirtualHost> This should allow you to use the .htaccess directives that you're wanting to use.

That helps, but I'm still not sure how you want the calculation to occur. For example, given specific values for $number1, $number2, $number3, and $number4, what result should your formula produce? Just a guess here, but your formula may not be handling the multiplication of $number4 the way you want. There is a process known as 'order of operations', which determine which math operations will be performed before other ones. In your formula, there are two aspects of 'order of operations' that would determine how the formula is calculated: 1) Anything within parenthesis is evaluated first 2) Within a group of parenthesis, or within the whole formula after all parenthesis have been evaluated, multiplication and division is performed first, then addition and subtraction is performed, both from left to right. If you use the following number as an example: >$number1=1 $number2=2 $number3=3 $number4=1.2 ...and substitute them into your formula: >echo 10 + (2.4 * 1) + (5.7 * 2) - (10 * 3) * 1.2; The first thing PHP will do is evaluate the multiplications in parenthesis: >echo 10 + 2.4 + 11.4 - 30 * 1.2; Next, it will look for multiplication and division operations to perform, from left to right and evaluate them. It will find '30 * 1.2' and evaluate it: >echo 10 + 2.4 + 11.4 - 36; Finally, it will evaluate the addition and subtraction operations from left to right: >echo -12.2; If you want to multiply the entire sum of 10 + (2.4 * $number1) + (5.7 * $number2) - (10 * $number3) times $number4, then that entire expression would need to be enclosed in parenthesis, forcing PHP to evaluate that entire sum first before multiplying it by $number4: >echo (10 + (2.4 * $number1) + (5.7 * $number2) - (10 * $number3)) * $number4; With the extra set of parenthesis to alter the order of operations, the above formula would evaluate to '-7.44' instead of '-12.2'. Hope this helps...

The last half of your formula is not valid code: >( * $number3) * $number4;} - You're indicating PHP should multiply something times $number3, but that something is missing from the formula. - The closing brace character at the end ("}") doesn't appear to have a corresponding open brace, unless this statement is the end of an 'if' block (for example). If that's not enough help, if you can describe what you want the formula to do, I can tell you how it should be coded to do that.

Welcome to the forums, srm_creator!

Welcome to the forums, fissionprime!

Welcome to the forums, Akogo!

That program is *really* old. The listed system requirements for RAM is '32MB'. I wouldn't be surprised if that software doesn't know how to properly calculate available RAM when there's 1GB of RAM in the system, because 1GB is a larger number than the software ever expected to see. If this is the case, I don't know that there is any way to work around the error.

Most of the steps appear to be necessary, but when installing to a TCH server, you have to work around not having shell access as noted below: Requirements: MIME-Tools - Instead of checking to see if this is installed from command line (shell), you'll need to log into your CPanel and click on the "Click to View" link next to "Installed Perl Modules" in the left column. This page will show the rather large list of all modules installed on your server. I'd suggest using your browser's "Find" feature and search for "Mime::Tools" in the page. If MIME::Tools is installed, you should find it in the page, and see most (if not all) of these other modules listed near it (which are also a part of the MIME-Tools package): >MIME::Body MIME::Decoder MIME::Decoder::Base64 MIME::Decoder::BinHex MIME::Decoder::Binary MIME::Decoder::Gzip64 MIME::Decoder::NBit MIME::Decoder::QuotedPrint MIME::Decoder::UU MIME::Entity MIME::Field::ConTraEnc MIME::Field::ContDisp MIME::Field::ContType MIME::Field::ParamVal MIME::Head MIME::Parser MIME::Parser::Filer MIME::Parser::Reader MIME::Parser::Results MIME::Tools MIME::WordDecoder MIME::Words I believe MIME-Tools should already be installed on your server, but if MIME-Tools does not appear to be installed, I'd recommend opening a Help Desk ticket and asking them to install it for you. Installation Change the lib path - You won't be able to run the command shown to list the perl library directories on the server. You can run this script instead from your browser (script name should end in '.cgi', and be sure to set its permissions to 0755 before running it): >#!/usr/bin/perl use CGI::Carp qw(fatalsToBrowser); print "Content-Type: text/plain\n\n"; print $_ ."\n" foreach @INC; If you see the current directory in the path list ("."), do not include it in the paths you add to the plugin script. After running the above script and adding the listed directories to the plugin script, you can delete the above script from the server. Set the cron job Use the Cron Jobs icon in your CPanel to set this up, and use the following as the 'Command to run' (with the correct path to the script for your account): >/usr/bin/perl /home/myaccount/cgi-bin/dada/plugins/dada_bridge.pl >/dev/null 2>&1 All of the other instructions should be followed as they are given. Hope this helps...

In your .bottom style, you need to add a 'clear: both;' to make the bar appear below your content: >.bottom { width: 700px; margin: 10px 0px 10px 0px; padding: 10px; text-align: left; border: 1px solid #C05F97; background-color: white; clear: both; }