Price calculation fails due to different field name

Created on 20 March 2013, almost 12 years ago
Updated 3 June 2024, 7 months ago

The default rule shipped with the module assumes a certain field name. But if you name your field differently, it will fail. So, instead of using a default rule, we could just generate the right rule when the field is created and remove it when it is deleted?

For that we can use the module name as machine-name prefix instead of the regular 'rules_' prefix - which is for rules created via the admin UI. That way we can make sure we do not run into any conflicts.

๐Ÿ› Bug report
Status

Needs review

Version

1.0

Component

Code

Created by

๐Ÿ‡ฆ๐Ÿ‡นAustria fago Vienna

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024