Merged
Conversation
tw2113
added a commit
that referenced
this pull request
Nov 10, 2025
* Release2141 (#774) * allow for only spans with a class attribute through (#771) * version bumps and changelog * start new field types * remove birthday year as that property does not exist. fill in day/month values * remove legacy date methods that were based on dropdowns. we will not be using * begin integration for birthday allowance as separated number fields * rename variable to not be birthday specific * add date part based maxlenth values * add in a year field now, for anniversary use later, fix space in attributes * fields wrapper for styling purposes, date separator * helper method to allow for customizing date field separator character. Not everyone may use forward slashes * future us note * adjust show_label usage to prevent extra unneeded markup from showing * make use of label placement for birthday wrapper * birthday specific layout fields * rebase * rebase * add in anniversary values, rename separator class * rebase * anniversary typo, only one property instead of 3 * rebase * remove commented out code from early approach attempt * hardcode for the moment * switch key order * custom handling for anniversary date values and api attribute * if we are handling date fields, prefix key with date part. make sure we have a date part to use * add some basic editor styling to match frontend * update block styles for anniversary/birthday dates * remove old, never actually used, dates method * fill in @next tags for next major release * publicly declare to avoid php notices * break early on partial dates * avoid php notices around missing array keys * handle anniversaries and birthdays in email message. * key mapping
tw2113
added a commit
that referenced
this pull request
Nov 18, 2025
* Release2141 (#774) * allow for only spans with a class attribute through (#771) * version bumps and changelog * start new field types * remove birthday year as that property does not exist. fill in day/month values * remove legacy date methods that were based on dropdowns. we will not be using * begin integration for birthday allowance as separated number fields * rename variable to not be birthday specific * add date part based maxlenth values * add in a year field now, for anniversary use later, fix space in attributes * fields wrapper for styling purposes, date separator * helper method to allow for customizing date field separator character. Not everyone may use forward slashes * future us note * adjust show_label usage to prevent extra unneeded markup from showing * make use of label placement for birthday wrapper * birthday specific layout fields * rebase * rebase * add in anniversary values, rename separator class * rebase * anniversary typo, only one property instead of 3 * rebase * remove commented out code from early approach attempt * hardcode for the moment * switch key order * custom handling for anniversary date values and api attribute * if we are handling date fields, prefix key with date part. make sure we have a date part to use * add some basic editor styling to match frontend * update block styles for anniversary/birthday dates * remove old, never actually used, dates method * fill in @next tags for next major release * publicly declare to avoid php notices * break early on partial dates * avoid php notices around missing array keys * handle anniversaries and birthdays in email message. * key mapping
tw2113
added a commit
that referenced
this pull request
Nov 18, 2025
* Release2141 (#774) * allow for only spans with a class attribute through (#771) * version bumps and changelog * start new field types * remove birthday year as that property does not exist. fill in day/month values * remove legacy date methods that were based on dropdowns. we will not be using * begin integration for birthday allowance as separated number fields * rename variable to not be birthday specific * add date part based maxlenth values * add in a year field now, for anniversary use later, fix space in attributes * fields wrapper for styling purposes, date separator * helper method to allow for customizing date field separator character. Not everyone may use forward slashes * future us note * adjust show_label usage to prevent extra unneeded markup from showing * make use of label placement for birthday wrapper * birthday specific layout fields * rebase * rebase * add in anniversary values, rename separator class * rebase * anniversary typo, only one property instead of 3 * rebase * remove commented out code from early approach attempt * hardcode for the moment * switch key order * custom handling for anniversary date values and api attribute * if we are handling date fields, prefix key with date part. make sure we have a date part to use * add some basic editor styling to match frontend * update block styles for anniversary/birthday dates * remove old, never actually used, dates method * fill in @next tags for next major release * publicly declare to avoid php notices * break early on partial dates * avoid php notices around missing array keys * handle anniversaries and birthdays in email message. * key mapping
tw2113
added a commit
that referenced
this pull request
Dec 3, 2025
* CON-440 - Anniversary and Birthday fields support. (#770) * Release2141 (#774) * allow for only spans with a class attribute through (#771) * version bumps and changelog * start new field types * remove birthday year as that property does not exist. fill in day/month values * remove legacy date methods that were based on dropdowns. we will not be using * begin integration for birthday allowance as separated number fields * rename variable to not be birthday specific * add date part based maxlenth values * add in a year field now, for anniversary use later, fix space in attributes * fields wrapper for styling purposes, date separator * helper method to allow for customizing date field separator character. Not everyone may use forward slashes * future us note * adjust show_label usage to prevent extra unneeded markup from showing * make use of label placement for birthday wrapper * birthday specific layout fields * rebase * rebase * add in anniversary values, rename separator class * rebase * anniversary typo, only one property instead of 3 * rebase * remove commented out code from early approach attempt * hardcode for the moment * switch key order * custom handling for anniversary date values and api attribute * if we are handling date fields, prefix key with date part. make sure we have a date part to use * add some basic editor styling to match frontend * update block styles for anniversary/birthday dates * remove old, never actually used, dates method * fill in @next tags for next major release * publicly declare to avoid php notices * break early on partial dates * avoid php notices around missing array keys * handle anniversaries and birthdays in email message. * key mapping * version bumps and changelog so far for this release * move required php to version 8 * more version bumps * move to 8.1 instead of 8.0. * Feature/con 486 composer packages updates (#775) * update defuse * update monolog * update the date format to be more readable * update google recaptcha * Feature/con 480 custom fields (#776) * update our custom fields api methods to take a customizable limit * list out available custom fields from given users account * make sure we have data to work with before outputting anything * only attempt any fetching if connected * cap custom field labels at 50 characters. Matches CTCTs limit when creating in their UI * admin builds * fill in next value * CON-479 - not connected optin messaging (#773) * add some default messaging to the optin tab if NOT connected. Disable the "Save changes" button * add new custom classes to our submit button * remove small script block. taking different approach * hide our submit button just on optin page, if not connected * build files * we have 2 years of upgrades that would put people above version 2.0.1 now. we will also make use of the migrated flag (#772) * css builds * begin changelog * more changelog items * Feature/con 490 i18n updates (#780) * remove pot command, amend redundant commands in build:release command * remove languages folder reference and load_plugin_textdomain * npm updates * Bump node-forge from 1.3.1 to 1.3.2 (#784) Bumps [node-forge](https://github.com/digitalbazaar/forge) from 1.3.1 to 1.3.2. - [Changelog](https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md) - [Commits](digitalbazaar/forge@v1.3.1...v1.3.2) --- updated-dependencies: - dependency-name: node-forge dependency-version: 1.3.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Michael Beckwith <tw2113@gmail.com> * changelog updates * Feature/con 481 assign list reminder (#781) * notification content * conditional logic to display our new notification * fix typo * update wording from client feedback * update NEXT tags for intended release * bump tested up to version * apply inline styles for bottom/right label placement (#783) * update readme --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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
1 participant
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.
This PR fixes some escaping of HTML that's preventing a dashicon from accurately rendering. Ready for release.