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 Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • Cron Job passwords emails etc.
Pages: [1]

Author Topic: Cron Job passwords emails etc.  (Read 850 times)

EdP

  • I post frequently
  • ***
  • Posts: 260
  • Karma: 7
  • CiviCRM version: 4.4
  • CMS version: Joomla 2.5.x
Cron Job passwords emails etc.
February 02, 2010, 06:19:36 am
As I understand it to use the cron jobs you have to edit the specific cron job files to insert some information - mainly email addresses, passwords and site keys. There are several files to edit and they don't all have the information you have to edit at the top of the file. When you upgrade your version of CiviCRM, all this data gets lost and you have to renter it.

This is a nuisance, and oddly un-user friendly when compared to the rest of the (easy) upgrade process. Have I misunderstood how this works?

Alternatively couldn't all these files either be (a) configurable from the admin section of civicrm, or (b) all include (as in the php command) a single file that they all share so I could configure the detail once per install not several times? If the former is doable, why is this data not saved (like all the other configuration detail) to make it even more painless to upgrade?

Thanks.

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Cron Job passwords emails etc.
February 02, 2010, 06:38:18 am

a couple of issues:

1. Our joomla upgrade process can be improved so folks can skip the uninstall/install routine and do an upgrade inplace. We ran into some bugs with this early on and could not figure it out. Might be fixed in more recent versions of joomla/civicrm, but we have not tested

2. we need to do a better job managing and monitoring the cron jobs and putting them all in one package. If you are interested in working on this and improving it contact us. If you are not a developer, consider sponsoring a developer to work on this. I suspect its a 50 hour or so project.

Would be great and help the whole community if we fix and improve the cron process for all CMS's

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • Cron Job passwords emails etc.

This forum was archived on 2017-11-26.