Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev/financial#171 - False INTL warning when adding a price field #19929

Merged
merged 1 commit into from
Mar 28, 2021

Conversation

demeritcowboy
Copy link
Contributor

Overview

https://lab.civicrm.org/dev/financial/-/issues/171#note_56522

  1. Turn off popups. (You don't have to but you won't see the message as easily.)
  2. Make a membership type and leave minimum fee blank.
  3. Make a price set for memberships.
  4. Add a price field and make it a radio or select.
  5. In the option choice rows there's a dropdown for the type. Pick the type you made.
  6. What's supposed to happen is the row is supposed to autofill. It doesn't.
  7. Click cancel.
  8. Message about missing INTL even though it's installed.

Before

False warning about missing INTL extension.
Hidden php type error.
Row doesn't autofill.

After

Good.

Technical Details

The field allows both null and 0. A blank gets stored as null, but then is_numeric is false when it tries to round it and the INTL message comes up when is_numeric is false. There's also then a type error which causes the ajax call to 500, so it doesn't autofill.

Comments

The second change is something not used at this point on the form but is clearly wrong and gives its own warning. It's been like that for about 8 years.

@civibot
Copy link

civibot bot commented Mar 28, 2021

(Standard links)

@eileenmcnaughton
Copy link
Contributor

Wow that last one survived a while

@eileenmcnaughton eileenmcnaughton merged commit 5bf266b into civicrm:master Mar 28, 2021
@demeritcowboy demeritcowboy deleted the fake-intl-warning branch March 29, 2021 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants