You will need to remove php_value and php_flag from ALL .htaccess files you may have

In .htaccess under public_html, add the following:

suPHP_ConfigPath /home/AccountUserName/public_html
<Files php.ini>
order allow,deny
deny from all
</Files>

In php.ini under public_html add the settings that you want to use:

register_globals = On
post_max_size 6M
upload_max_filesize 6M
max_execution_time 90
max_input_time 90
....

Bookmark It

Is it possible to get Awstats to send a monthly report with some basic stats  to Email?

Script to send last months AwStats report to an email address: www.sitepoint.com/forums/showthread.php?t=275042

This scipt will run on a web server with CPanel.  It uses the CPanel  system to log in and get the report page from AwStats for the previous month.

To use this script:

• change the strings located in the first block of code to match  information for your domain and CPanel account.
• Install the two script files into a location on your web server outside of the public html area (you don’t want someone accidently seeing the account details).
• Then set up a cron job to run the php program sometime after the first of the month. The command for the cron job might look like:php -q /home/userid/scripts/stats.php

Based on a script from Ronan Magee (ronanmagee on the SitePoint.com forum)
Modified by David K. Goodwin (dkg2000 on the SitePoint.com forum)

Bookmark It

I was recently surprised to see that my wordpress install folders have swelled up in size like anything. I have 3 installs of WP and I noticed that in the root of each install there were dump files with a name pattern “core.*” and with sizes to the tune of 12MB each.

core files come from a core dump. A core dump can happen for lots of reasons, but in shared hosting it generally occurs if:

1. Your site software is not compatible with the latest server software versions.

2. The server software itself was/is having issues.

• Check the content of the core dump files for clues. It is probably because one of your binaries (i.e. unzip, imagemagick) is not working correctly. If the core files point back to php, then it could be a a memory limit problem, a g2 bug, or a php bug.
• Try a clean install of WordPress (delete all old files, re-upload, new, empty database). Make sure you backup your blog (export all posts and also back up the database).
• ( System Administrator ) -  You can stop core files from being produced as a result of suPHP and Rlimit stoppages. In /etc/init.d/httpd at the top of the file you’ll see the ulimit command line. Add a “-c 0″ (slash-c-zero) to the line:
  Code:

  ulimit -c 0 -n x

  where the x above is the number previously assigned by your Rlimit script. That should stop core dump files

Bookmark It