CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • CiviMail Cron Jobs w/ Standalone CRM
Pages: [1]

Author Topic: CiviMail Cron Jobs w/ Standalone CRM  (Read 2114 times)

lewayotte

  • Guest
CiviMail Cron Jobs w/ Standalone CRM
January 26, 2010, 05:32:40 am
I have a client who needs an install of the CiviCRM Standalone, which is setup and running. He will be doing mass mailings, so I thought it was be nice to have a cron job setup to check for new mails. The documentation (http://wiki.civicrm.org/confluence/display/CRMDOC/CiviMail+Installation#CiviMailInstallation-SettingUptheCronJob) seems to indicate that I can use the civimail.cronjob.php with a valid un/pw combo - but only from a drupal/joomla user with access to the CRM.

Since this is a standalone install, how do I get around this?

Thanks.
Lew

Tiggr

  • I post occasionally
  • **
  • Posts: 38
  • Karma: 1
    • Rodgauer Workshop
  • CiviCRM version: 4.7.beta3
  • CMS version: Drupal 7
Re: CiviMail Cron Jobs w/ Standalone CRM
January 27, 2010, 01:11:28 am
Hello!

Just comment out the line, that does the authentification in civimail.cronjob.php:

Code: [Select]
    $config =& CRM_Core_Config::singleton();

    // this does not return on failure
    // CRM_Utils_System::authenticateScript( true );

    // we now use DB locks on a per job basis
    processQueue( )

I think, this only has a small impact on security.

Bye
Tiggr (aka Marcus)

cap10morgan

  • I post occasionally
  • **
  • Posts: 56
  • Karma: 9
Re: CiviMail Cron Jobs w/ Standalone CRM
January 29, 2010, 11:05:59 am
The alternative, in recent versions of CiviCRM, is that you can use your OpenID and the API Key as the username and password, respectively. You'd set the api_key field manually in the civicrm_contact table in the database (for the contact record whose OpenID you want to use for this). Set it to a secure password-like value.

So, for example, if my OpenID is http://foo.myopenid.com/ and the api_key value is "gabbagabbaH3y" then you would use "http://foo.myopenid.com/" is the username (make sure it's exactly the same as the value in civicrm_openid for that contact record) and "gabbagabbaH3y" as the password.

This is a bit cumbersome right now, we realize. Here's the ticket tracking the implementation of a better way (but it's not done yet--patches welcome!): http://issues.civicrm.org/jira/browse/CRM-5131

lewayotte

  • Guest
Re: CiviMail Cron Jobs w/ Standalone CRM
February 02, 2010, 10:14:34 am
Thanks guys! Tiggr's solution was good enough for me.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • CiviMail Cron Jobs w/ Standalone CRM

This forum was archived on 2017-11-26.