2.2.0: Error when deleting a price option from a price set

[ken]

When deleting a price-option from a price-set (task=civicrm/admin/price/field/option) I get the following error:

Sorry. A non-recoverable error has occurred.

civicrm_event_page is not supported in PriceSet::usedBy()

Return to home page.

I tried duplicating this on the Drupal demo but this failed.

Looking at the code for PriceSet::getUsedBy() in CRM/Core/BAO/PriceSet.php I notice the following at line 165 ...

Code: [Select]

$queryString = "SELECT entity_table, entity_id FROM civicrm_price_set_entity ";
When I run that query I get 5 rows returned where the entity_table column is set to 'civicrm_event_page'.

It appears these rows were not updated during the data conversion to 2.2.0. What should I do?

Thanks,
Ken

[Donald Lobo]

can you change the rows via sql to 'civicrm_event', you might also need to tweak the entity_id to match civicrm_event id

If this works, can you please file an issue and link to this forum. We'll fix the upgrade script for 2.2.1

thanx

lobo

[ken]

Thanks, Lobo.

I will do as you suggest and report the results.

However, I'm concerned that some urgent action may be required!

The event Id's and the event_page Id's don't always line up - so people who do the upgrade and don't keep a backup of their original database are in trouble. Even those who do keep a backup may have trouble getting the data out of their backup.

When I run this query ...

Code: [Select]

SELECT `civicrm_event_page`.`event_id` , `civicrm_event_page`.`id`
FROM civicrm_event_page, civicrm_price_set_entity
WHERE `civicrm_event_page`.`id` = `civicrm_price_set_entity`.`entity_id`
AND `civicrm_price_set_entity`.`entity_table` = 'civicrm_event_page'
ORDER BY `civicrm_event_page`.`event_id` ASC
... I get the following result ...

Code: [Select]

event_id id
389 389
390 390
391 391
401 400
409 407
... showing the event Ids and event-page Ids are not always equal.

Ken

[Kurund Jalmi]

Ken:

Can you file an issue for this.

Kurund

[Donald Lobo]

i'm not sure what we can do for sites already upgraded (since event_page and event_page_id are different). We will probably change the reference automatically and ask the admin to manually verify and fix the price sets for each event

lobo