forked from civicrm/civicrm-core
-
Notifications
You must be signed in to change notification settings - Fork 1
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
5.64 one click #7
Open
seamuslee001
wants to merge
12
commits into
5.64
Choose a base branch
from
5.64_one_click
base: 5.64
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Commits on Jan 25, 2024
-
Configuration menu - View commit details
-
Copy full SHA for b1566a3 - Browse repository at this point
Copy the full SHA b1566a3View commit details -
Configuration menu - View commit details
-
Copy full SHA for b1a7983 - Browse repository at this point
Copy the full SHA b1a7983View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4ee68b0 - Browse repository at this point
Copy the full SHA 4ee68b0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 53a1f9b - Browse repository at this point
Copy the full SHA 53a1f9bView commit details -
(REF) civicrm/mailing/unsubscribe - Add page-controller in front of f…
…orm-controller Before: `civicrm/mailing/unsubscribe` points directly to `CRM_Mailing_Form_Unsubscribe` After: `civicrm/mailing/unsubscribe` points to `CRM_Mailing_Page_Unsubscribe`, which MAY delegate to `CRM_Mailing_Form_Unsubscribe` Comments: * This is a step toward supporting one-click subscribe. * The problem is that one-click unsubscribe MUST receive a POST on the same URL as a user-visible form. * In Quickform (esp `CRM_Mailing_Form_Unsubscribe`), every POST MUST give a `qfKey`. * We need a place to process the one-click POST *without* requiring `qfKey`. * There is a pre-existing class `CRM_Mailing_Page_Unsubscribe`. This was dead code. The patch co-opts/re-uses the class for its own purpose. * The old `Page` class was not referenced anywhere (by routes or other classes). * What appears to have happened: this screen was originally a `Page`; then it was renamed/converted to a `Form`; then shortly after, the original `Page` was re-imported verbatim by a gsoc student. Their commit doesn't appear to make substantive use of the `Page`. This smells like mistake in handling branches/merges/rebases.
Configuration menu - View commit details
-
Copy full SHA for b61dbd6 - Browse repository at this point
Copy the full SHA b61dbd6View commit details -
Configuration menu - View commit details
-
Copy full SHA for d998ae7 - Browse repository at this point
Copy the full SHA d998ae7View commit details -
Configuration menu - View commit details
-
Copy full SHA for d780b22 - Browse repository at this point
Copy the full SHA d780b22View commit details -
(REF) Move testGitLabIssue1108() to its own class
BEFORE: `MailingSystemTest` (which extends `BaseMailingSystemTest`) includes `testGitLabIssue1108($isMultilingual)`. This is a transactional test (per `BaseMailingSystemTest::setUp()`). AFTER: `MultingualSystemTest` includes `testGitLabIssue1108()`. This is not a transactional test. COMMENTS: This resolves some circumstantial flakiness in the tests. * The problem appeared when adding an unrelated test `BaseMailingSystemTest` -- the new test failed because of a conflict with `testGitLabIssue1108()`. * You could also produce the problem in other cases by switching around the order of `testGitLabIssue1108()` (e.g. hack data-provider `multiLingual()`) * I believe the root problem is that `BaseMailingSystemTest` is written as a transactional test -- but `testGitLabIssue1108()` does large-scale schema changes (whenever it toggles multilingual), which makes it non-transactional. * The patch here prevents these kind of conflicts by putting `testGitLabIssue1108()` in a separate (non-transactional) context.
Configuration menu - View commit details
-
Copy full SHA for e2c4e48 - Browse repository at this point
Copy the full SHA e2c4e48View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5433d59 - Browse repository at this point
Copy the full SHA 5433d59View commit details -
ListUnsubscribe - Ensure URL is always absolute
When delivering via unit-test or cron job, the URL came out absolute. But when using web UI to "Send test", the URL was relative. It should be absolute.
Configuration menu - View commit details
-
Copy full SHA for bfcfcf9 - Browse repository at this point
Copy the full SHA bfcfcf9View commit details -
Configuration menu - View commit details
-
Copy full SHA for f5c242a - Browse repository at this point
Copy the full SHA f5c242aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2d5a82b - Browse repository at this point
Copy the full SHA 2d5a82bView commit details
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.