Contribution recur checkout pp - #14
Open
ufundo wants to merge 631 commits into
Open
Conversation
Add `/lintroll` github action
Fix recaptcha2 on Afform
This regressed when 'extra' fields were introduced in 6.15 (e6e67dc). Fixes dev/core#6576
Switch accesskeys css to a class
We still have calls to this function but this makes it obvious we are encouraging the api instead
Search aggregate totals can now be shown in the header, footer, or both. Standardized on user-facing text "Totals" instead of "Tally". Fixes dev/core#6544
dev/core#6576 Afform - Fix viewing form submissions
PR Commands: Fix /lintroll action restrictions on civicrm/civicrm-core
…xtcol, tidies css
SearchKit - Enable totals in header as well as footer
Add /port command to PR commands workflow
Fix example event to have from email (used in tests)
dev/core#6570 duplicate translation_source
Fixes dev/core#6575
GH Actions: Fix push target branch for `/port` when HEAD is detached
Deprecate getLineItems function & remove some test calls
…reams Riverlea Theme Editor - better support for packaged streams
RiverLea: `.odd` should take precedence over `.even-row`
Port: "SearchKit - Restore title on standalone search display page" to 6.16
dev/core#6574 permit logging hook to run during upgrade
Fixing no validation message for required fields after a required Dat…
…ault Get default values for hidden fields
[PHP8.5] Fix notice error on running ECK unit tests
Refactor CRM_Core_BAO_Country to use Civi::$statics
Order API: Remove ContributionRecur::Create from calculateContributionRecurValues()
No, 'default_callback' is not a thing for custom fields. It's not a column on the `civicrm_custom_field` table.
Fixes a bug where default values for custom fields overwrite exiplicit values when the explicit value is written with suffix notation e.g. `Group.Field:name`. Fixes dev/core#6605
…hen-render dev/core#6557 Standalone ErrorHandler - collect messages then render later
…ation on MariaDB 10.6
(dev/core#6609) CRM_Core_I18n_SchemaTest - Accept equivalent DDL variant on MariaDB 10.6
(dev/core#6609) SchemaHelper - Normalize table ordering across DBMS's
…ait_pledgeblock Allow for NULL values to be returned if in entity definition
…l-fields make CRM_Core_Payment::getAllFields public
Api4 - Fix saving custom fields with default values
Fix batch export download file
(EXP) OAuth for Payment Processor Setup
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
A brief description of the pull request. Keep technical jargon to a minimum. Hyperlink relevant discussions.
Before
What is the old user-interface or technical-contract (as appropriate)?
For optimal clarity, include a concrete example such as a screenshot, GIF (LICEcap, SilentCast), or code-snippet.
After
What changed? What is new old user-interface or technical-contract?
For optimal clarity, include a concrete example such as a screenshot, GIF (LICEcap, SilentCast), or code-snippet.
Technical Details
If the PR involves technical details/changes/considerations which would not be manifest to a casual developer skimming the above sections, please describe the details here.
Comments
Anything else you would like the reviewer to note