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) »
  • Upgrading from 4.2.7 to 4.3.3 - cron and custom field errors
Pages: [1]

Author Topic: Upgrading from 4.2.7 to 4.3.3 - cron and custom field errors  (Read 1457 times)

cath

  • I’m new here
  • *
  • Posts: 7
  • Karma: 0
  • CiviCRM version: 4.3.3
  • CMS version: Drupal 7.22
  • MySQL version: 5.1.68
  • PHP version: 5.3.10
Upgrading from 4.2.7 to 4.3.3 - cron and custom field errors
May 20, 2013, 03:55:45 pm
Hi,

Last week I upgraded from 4.2.7 to 4.3.3 (on Drupal 7.22). I have had two odd issues:

1. Cron jobs - the cron.php script is being triggered using curl. I can see from the logs that the cron is running every hour, as it should, but it doesn't seem to be triggering the send mail scheduled task. This seems to be the same problem as CRM-12648, except I'm using curl rather than wget. Will the fix in 4.3.4 fix this for curl as well as wget?

2. Membership sign-up form - we have a profile containing some custom fields as part of the membership sign-up form. Most of the fields are showing correctly. However, any fields with check-boxes (e.g., tick the 5 that apply, etc) are not displaying. If I preview the profile in Civi, all is well; however, the page on Drupal is not displaying the tick options. If I view the source of the Drupal page, the code where the tick boxes should be is as follows:
Code: [Select]
<table class="form-layout-compressed"><tr></tr></table> - i.e., there are no td elements (which is presumably where the tick options should reside) and only one (empty) row. There is nothing obvious in the css which would make the tick options/table cells disappear so I'm not sure what to look for next?

I have successfully upgraded from 4.2.7 to 4.3.1 for another client, with no issues (also Drupal 7.22 - same server, so same versions of PHP, hardware etc.) so I'm not sure whether something has been introduced in 4.3.2 or 4.3.3 which might have caused either of these?

Thanks in anticipation!

Cath

cath

  • I’m new here
  • *
  • Posts: 7
  • Karma: 0
  • CiviCRM version: 4.3.3
  • CMS version: Drupal 7.22
  • MySQL version: 5.1.68
  • PHP version: 5.3.10
Re: Upgrading from 4.2.7 to 4.3.3 - cron and custom field errors
July 19, 2013, 05:37:03 pm
Hi,

Just to follow this one up - I have upgraded to 4.3.5 today and both problems are fixed. Thanks for building the fixes into the new releases!

Cath

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrading from 4.2.7 to 4.3.3 - cron and custom field errors

This forum was archived on 2017-11-26.