CiviCRM Community Forums (archive)

No questions - just some things that worked which might help someone else that I couldn't find exactly, but had a need to do for clients.
CMS = joomla 1.5x, civicrm 3.3, linux, php5,

Go Daddy or it's reseller shared hosting has a CRON job setup.  It wants you to browse script or executable.  It will then affix the php interpretter for you. so browse to the civimail.cronjob.php (or whatever civi script applies) & select it.  they will set the rest of the path variable also (as $HOME).  then you append name, pass, key to the end of the command as shown.  final version will look like this:
 /web/cgi-bin/php5 "$HOME/html/administrator/components/com_civicrm/civicrm/bin/civimail.cronjob.php" name=<joomla mail user> pass=<some-real-password> key=<the-real-key-in-your-setting>   use custom button to set more time options.  Go Dad only allows 2 jobs per hour by default.  create multiple jobs each at different times if you need more.   

for plesk,  the wget version was the only version I got running.  Cron setup is a scheduled task under the specific domain . 
This will work: (the time setting first:)
*/2 * * * *  (the actual command:) wget -O - -q -t 1 --post-data='name=<joomla-user>&pass=<some-real-password>&key=<the-real-key-in-your-setting>' http://www.somesite.tld/administrator/components/com_civicrm/civicrm/bin/civimail.cronjob.php   this runs every 2 minutes

Hope it helps some one else.

The clients on Go Dad reseller will migrate up to joomla 1.7 & Civi 4, but wanted to change servers before doing upgrade, so I had to learn all the stuff anyway.  If I find it's different there, will post back.

Wes.