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) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 2.1 Release Testing »
  • CiviCRM 2.1b6 - Include Profiles - Upgrade bug
Pages: [1]

Author Topic: CiviCRM 2.1b6 - Include Profiles - Upgrade bug  (Read 4963 times)

ansm

  • Guest
CiviCRM 2.1b6 - Include Profiles - Upgrade bug
September 24, 2008, 09:28:14 am
After upgrading from a perfectly working 2.06, I can no longer see any of my profiles for inclusion to a contribution page.  The workaround for this bug is to edit one field in each of the profiles and re-save it with no changes.  Now the Profiles and selectable in Contribution pages.
This also makes the Type column filled in under the contribution page list.
« Last Edit: September 26, 2008, 08:10:38 am by ansm »

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: CiviCRM 2.1b5 - Include Profiles - Upgrade bug
September 24, 2008, 10:31:28 am
May be a bug in upgrade. Can you file an issue for this and send your 2.0.x db to kurund at civicrm dot org. We can check and fix it.

thanx,

Kurund
Found this reply helpful? Support CiviCRM

ansm

  • Guest
Re: CiviCRM 2.1b5 - Include Profiles - Upgrade bug
September 26, 2008, 08:10:12 am
This bug has been created also in 2.1b6.  A bug report has been filed, and you have also been sent a copy of the databases.

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: CiviCRM 2.1b6 - Include Profiles - Upgrade bug
September 26, 2008, 12:57:47 pm
We will investigate and get back to you on this issue.

thanx

Kurund
Found this reply helpful? Support CiviCRM

ansm

  • Guest
Re: CiviCRM 2.1b6 - Include Profiles - Upgrade bug
October 02, 2008, 06:03:35 am
This was fixed in 303.

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Re: CiviCRM 2.1b6 - Include Profiles - Upgrade bug
October 06, 2008, 07:18:05 am
I just did an upgrade from 2.0.6 to 2.1 stable and ran into what would appear to be a related bug --

When I go into my event config, online reg, and seek to add a profile to the form, not all of the profiles show up on the list. After playing around with it for a while, it appears that the dropdown won't let you add certain mixed-type profiles.

For example, there is a profile that is added to all event registrations to capture details on the participant. It includes individual type fields, participant type, and contribution type (relevant to the payment for registration taking place).

After further testing, it appears that the presence of the contribution field to this profile disables it from being placed on an event page. I imagine it's a little tricky to try to sort out a mixed use profile like that. But I think this particular form was working correctly in 2.0, so just wondering if this is a bug, or a limitation.
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Re: CiviCRM 2.1b6 - Include Profiles - Upgrade bug
October 06, 2008, 07:33:11 am
I think there are more bugs going on with the profile usage. I'm working with an upgrade from v2.0.

I'm working in an event config and have noticed the following behaviors with adding profiles to forms --

It appears the interface does not handle the removal of a profile from an event very well. For example, if I add profile1 to the top, and then go back and remove from the top and add it to the bottom, it doesn't always remove it -- sometimes it changes it to the bottom location AND adds a new one.

I'm not describing this very well... let me explain what I'm seeing at the database level --

I go into civicrm_uf_join and see multiple instances of the event form -- profile join, some of which are identical (which is why I think it's not removing them correctly). When duplicates are present, one shows up in the top space, one in the bottom (apparently weight=1 for the top and weight=4 for the bottom locations are not restrictive -- multiple profiles with a weight=4 results in one on the top, one on the bottom).

At least some piece of this puzzle is related to the upgrade process, I believe. I have numerous duplicate joins in that table (which results in the same profile set appearing in the form twice).
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

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: CiviCRM 2.1b6 - Include Profiles - Upgrade bug
October 06, 2008, 08:40:53 am
Quote from: lcdweb on October 06, 2008, 07:18:05 am
After further testing, it appears that the presence of the contribution field to this profile disables it from being placed on an event page. I imagine it's a little tricky to try to sort out a mixed use profile like that. But I think this particular form was working correctly in 2.0, so just wondering if this is a bug, or a limitation.

This is a limitation for 2.1 (and 2.2). We've restricted profile types that can be exposed in event/contrib pages and disallowed use of mixed profiles in those pages

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

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: CiviCRM 2.1b6 - Include Profiles - Upgrade bug
October 06, 2008, 08:44:01 am
Quote from: lcdweb on October 06, 2008, 07:33:11 am
I go into civicrm_uf_join and see multiple instances of the event form -- profile join, some of which are identical (which is why I think it's not removing them correctly). When duplicates are present, one shows up in the top space, one in the bottom (apparently weight=1 for the top and weight=4 for the bottom locations are not restrictive -- multiple profiles with a weight=4 results in one on the top, one on the bottom).

At least some piece of this puzzle is related to the upgrade process, I believe. I have numerous duplicate joins in that table (which results in the same profile set appearing in the form twice).

can u check the 2.0 db and check if there were multiple uf join records there to begin with? there was a reported bug (which we could not reproduce) about multiple uf join records being present in the db in 1.9 / 2.0.

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

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Re: CiviCRM 2.1b6 - Include Profiles - Upgrade bug
October 06, 2008, 08:54:43 am
Re: the limitation (and as a general comment) -- we need to figure out a way to communicate those limitations on the profile field creation form. It's been misleading for quite some time, as it's easy for people to think they can add any combination of field types to a profile, without restriction.

What's difficult, it seems, is that some type pairs are acceptable -- e.g. I can do Individuals + Participants, or Individuals + Contacts + Participants, but Individuals + Participants + Contribs doesn't fly.

Re: the 2.0 db check -- yes, there were duplicates, but they had different weight values. Post-upgrade, several of those dups had weight values changed to "4". Here's a snapshot of the data from my pre-upgrade backup:

Code: [Select]
(1, 1, 'Profile', NULL, NULL, 1, 1),
(2, 1, 'Profile', NULL, NULL, 2, 2),
(3, 1, 'Search Profile', NULL, NULL, 2, 2),
(4, 1, 'Profile', NULL, NULL, 3, 3),
(5, 1, 'Profile', NULL, NULL, 4, 4),
(6, 1, 'Profile', NULL, NULL, 5, 5),
(7, 1, 'CiviEvent', 'civicrm_event', 1, 5, 5),
(8, 1, 'CiviEvent', 'civicrm_event', 2, 5, 5),
(9, 1, 'CiviEvent', 'civicrm_event', 2, 1, 5),
(10, 1, 'CiviEvent', 'civicrm_event', 1, 1, 5),
(11, 1, 'Profile', NULL, NULL, 5, 6),
(12, 1, 'CiviContribute', 'civicrm_contribution_page', 3, 1, 6),
(13, 1, 'Search Profile', NULL, NULL, 6, 7),
(14, 1, 'Search Profile', NULL, NULL, 7, 8),
(15, 1, 'CiviEvent', 'civicrm_event', 3, 1, 5),
(16, 1, 'CiviEvent', 'civicrm_event', 4, 5, 5),
(17, 1, 'CiviEvent', 'civicrm_event', 4, 1, 5),
(18, 1, 'CiviContribute', 'civicrm_contribution_page', 4, 1, 6),
(19, 1, 'Profile', NULL, NULL, 8, 9),
(20, 1, 'CiviEvent', 'civicrm_event', 9, 5, 5),
(21, 1, 'CiviEvent', 'civicrm_event', 9, 1, 5),
(22, 1, 'CiviEvent', 'civicrm_event', 10, 5, 5),
(23, 1, 'CiviEvent', 'civicrm_event', 10, 1, 5),
(24, 1, 'CiviEvent', 'civicrm_event', 7, 1, 5),
(25, 1, 'CiviEvent', 'civicrm_event', 11, 1, 5);
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 2.1 Release Testing »
  • CiviCRM 2.1b6 - Include Profiles - Upgrade bug

This forum was archived on 2017-11-26.