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 »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
Pages: [1]

Author Topic: Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs  (Read 1766 times)

ceres_systems

  • I’m new here
  • *
  • Posts: 8
  • Karma: 0
  • CiviCRM version: 3.2.2
  • CMS version: Drupal 6.17
  • MySQL version: 5.5
  • PHP version: 5.3.2-2.1
Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
September 12, 2011, 10:42:21 pm
Hi All,

I finally got around to upgrading to 3.4. But now the UpdateMemberShipRecords.php cron task says it has an invalid key.
This is not the case. No matter what key I use I always get an invalid key.

This is obviously causing head aches as we cannot update memberships that have expired.

If I run the update script from the console I get -- Usage: Please define CIVICRM_CONFDIR in settings_location.php at the top level civicrm directory --

But alas I connot seem to find a settings_location.php file with CIVICRM_CONFDIR inside it.

Any ideas?

-Matt

ceres_systems

  • I’m new here
  • *
  • Posts: 8
  • Karma: 0
  • CiviCRM version: 3.2.2
  • CMS version: Drupal 6.17
  • MySQL version: 5.5
  • PHP version: 5.3.2-2.1
Re: Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
September 12, 2011, 10:56:02 pm
Also we used to be able to click into the membership record and save, causing the record to update.

I now get this....
---
Please correct the following errors in the form fields below:

    * There is no valid Membership Status available for selected membership dates.
---

But I have all the standard membership status setup.

I have tried to create a new to test. But it does not work either.

-Thanks.

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
September 12, 2011, 11:02:02 pm
Hi,

Don't mix different issues in the same thread, the click and the cli issue are unlikely linked, start a new thread.

For the cli:

you don't need to provide the key anymore, just be sure it's defined and long enough in your civicrm.setting (should be).

You can either apply this patch (or wait until it gets approved)
http://issues.civicrm.org/jira/browse/CRM-8851

or you need to create a file named 'settings_location.php' in the top-level directory of your CiviCRM codebase as follows:

Code: [Select]
<?php
// the following (/home/lobo/public_html/drupal/sites/)
// should be changed to your sites directory
define( 'CIVICRM_CONFDIR', '/home/lobo/public_html/drupal/sites/' );


-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

ceres_systems

  • I’m new here
  • *
  • Posts: 8
  • Karma: 0
  • CiviCRM version: 3.2.2
  • CMS version: Drupal 6.17
  • MySQL version: 5.5
  • PHP version: 5.3.2-2.1
Re: Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
September 12, 2011, 11:15:49 pm
Thanks.

I will try the location file before the patch.

-Matt

ceres_systems

  • I’m new here
  • *
  • Posts: 8
  • Karma: 0
  • CiviCRM version: 3.2.2
  • CMS version: Drupal 6.17
  • MySQL version: 5.5
  • PHP version: 5.3.2-2.1
Re: Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
September 12, 2011, 11:31:54 pm
No dice.

I have defined a 'settings_location.php' but unfortunately I have now gone full circle and I'm getting a invalid key error again.

The invalid key comes after running --
   php bin/UpdateMembershipRecord.php -u cron -p password -s default

Which as I understand should not happen anymore after defining a user and pssword?

Thanks.

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
September 12, 2011, 11:39:17 pm
Which version of 3.4 are you upgrading to?

are you sure the key is defined in default/civicrm.settings.php ?

X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

ceres_systems

  • I’m new here
  • *
  • Posts: 8
  • Karma: 0
  • CiviCRM version: 3.2.2
  • CMS version: Drupal 6.17
  • MySQL version: 5.5
  • PHP version: 5.3.2-2.1
Re: Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs
September 12, 2011, 11:45:47 pm
The Key definitely defined in the sites/default/civicrm.settings.php file

upgraded to civicrm 3.4.5


Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrade from 3.2.2 to 3.4. Causes invalid key when runnning cron jobs

This forum was archived on 2017-11-26.