Development issueshttps://lab.civicrm.org/groups/dev/-/issues2022-06-11T14:54:37Zhttps://lab.civicrm.org/dev/core/-/issues/3576Error on Fetch Bounces Scheduled job2022-06-11T14:54:37ZcalbasiError on Fetch Bounces Scheduled jobI get this error:
> Parameters parsed (and passed to API method):
> a:1:{s:7:"version";i:3;}
>
> Full message:
> Finished execution of Fetch Bounces with result: Error, Error message: A fatal error was triggered: No s'ha pogut connec...I get this error:
> Parameters parsed (and passed to API method):
> a:1:{s:7:"version";i:3;}
>
> Full message:
> Finished execution of Fetch Bounces with result: Error, Error message: A fatal error was triggered: No s'ha pogut connectar a MailStore per xxxxx@xxxxx.xxx@xxxxx.xxxxx.xxx
>
> Missatge d'error:
>
> Could not create /var/www/xxx/xxx/xxx/private/xxx/custom//CiviMail.ignored/2019/07/03/cur
But if I fire manually this job, it succeed!
That's why I think it's a bug.
I found a [related issue](https://civicrm.stackexchange.com/questions/4045/email-to-activity-processing-error-message-process-activities-failed)
Pay attention on this Stackexchange reporded issue talk about an error on "second run"
I'm using: CiviCRM 5.10.4.
By the way, I initially tried to use IMAP, but I was not able to connect the mail server, so I've changed to POP3. I don't think it has any relationship, but...https://lab.civicrm.org/dev/wordpress/-/issues/79"Network Error" when sorting contact search results by City, Postcode or Country2020-10-19T11:16:20Zjern"Network Error" when sorting contact search results by City, Postcode or CountryIf you search for contacts and then try to sort the result list by clicking on City, Postcode or Country, a "Network Error Unable to reach the server. Please refresh this page in your browser and try again." modal window appears. Sorting...If you search for contacts and then try to sort the result list by clicking on City, Postcode or Country, a "Network Error Unable to reach the server. Please refresh this page in your browser and try again." modal window appears. Sorting by Name or Email is fine. This error was found in 5.30.0 (WP), but it's also present in the WP sandbox version 5.32.https://lab.civicrm.org/dev/core/-/issues/88Make sure financial_type_id is set when a contribution is created2018-06-18T20:13:30Zmattwiremjw@mjwconsult.co.ukMake sure financial_type_id is set when a contribution is createdOverview
----------------------------------------
When a contribution is created via a contribution page (with a confirmation page) the parameter `financial_type_id` is not set if the contribution is not being created with a recurring co...Overview
----------------------------------------
When a contribution is created via a contribution page (with a confirmation page) the parameter `financial_type_id` is not set if the contribution is not being created with a recurring contribution.
PR: https://github.com/civicrm/civicrm-core/pull/11907
Before
----------------------------------------
`financial_type_id` is not set when a non-recurring contribution is submitted via a contribution page (with a confirmation page). But it is set when a recurring contribution is being created at the same time.
After
----------------------------------------
`financial_type_id` is always set for contribution params when submitted via a contribution page (with a confirmation page).
This makes it more consistent for use in payment processor extensions etc.5.4.0https://lab.civicrm.org/dev/core/-/issues/3640Most recent contact note exposed in event confirmation emails.2022-06-11T14:57:56ZBobSMost recent contact note exposed in event confirmation emails.* Create an event where the on-line registration profile contain a Contacts:Note field.
* Contact leaves that field blank during form submission.
* Result: Contact receives a confirmation email showing the most recent note on that contac...* Create an event where the on-line registration profile contain a Contacts:Note field.
* Contact leaves that field blank during form submission.
* Result: Contact receives a confirmation email showing the most recent note on that contact.
Not sure if this behavior is intentional, but I consider it problematic.
- a) Showing a contact a note he might have submitted years ago is rather confusing.
- b) Backend users may have an expectation of confidentiality when they add notes to a contact record, believing that info will never be exposed to the contact.
Confirmed on CiviCRM 5.13.4, 5.15.1.https://lab.civicrm.org/dev/wordpress/-/issues/80Users cannot be created if no unsupervised deduping rule exists2021-10-20T09:51:13ZBradley TaylorUsers cannot be created if no unsupervised deduping rule existsWe have recently had an issue where users could not be added via the WordPress admin add new user screen. The following exception was logged: `Unsupervised rule for Individual does not exist`
**Steps to reproduce:**
- Go to the CiviCRM ...We have recently had an issue where users could not be added via the WordPress admin add new user screen. The following exception was logged: `Unsupervised rule for Individual does not exist`
**Steps to reproduce:**
- Go to the CiviCRM dedup rules config screen (/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fcontact%2Fdeduperules&reset=1)
- For any unsupervised rules under the "Individual Rules" table, either delete the rule, or change the usage type to "General".
- Try adding a new WordPress user at /wp-admin/user-new.php
I've not tested this, but I expect the easiest course of action is to wrap the call to `synchronizeUFMatch` in `CiviCRM_For_WordPress_Users` in a try-catch block. I've not checked to see if this issue affects Drupal/ Joomla.
There is currently nothing in the documentation to suggest having an unsupervised rule is a requirement, but if not having an unsupervised rule will cause other problems then this should be clearly stated in https://docs.civicrm.org/user/en/latest/common-workflows/deduping-and-merging/https://lab.civicrm.org/dev/core/-/issues/2918Users cannot be created if no unsupervised deduping rule exists2022-09-01T21:00:57ZBradley TaylorUsers cannot be created if no unsupervised deduping rule existsWe have recently had an issue where users could not be added via the WordPress admin add new user screen. The following exception was logged: `Unsupervised rule for Individual does not exist`
**Steps to reproduce:**
- Go to the CiviCRM ...We have recently had an issue where users could not be added via the WordPress admin add new user screen. The following exception was logged: `Unsupervised rule for Individual does not exist`
**Steps to reproduce:**
- Go to the CiviCRM dedup rules config screen (/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fcontact%2Fdeduperules&reset=1)
- For any unsupervised rules under the "Individual Rules" table, either delete the rule, or change the usage type to "General".
- Try adding a new WordPress user at /wp-admin/user-new.php
I've not tested this, but I expect the easiest course of action is to wrap the call to `synchronizeUFMatch` in `CiviCRM_For_WordPress_Users` in a try-catch block. I've not checked to see if this issue affects Drupal/ Joomla.
There is currently nothing in the documentation to suggest having an unsupervised rule is a requirement, but if not having an unsupervised rule will cause other problems then this should be clearly stated in https://docs.civicrm.org/user/en/latest/common-workflows/deduping-and-merging/5.49.0https://lab.civicrm.org/dev/core/-/issues/89Batch update participants with checkboxes fails2019-03-28T15:57:21ZStoobBatch update participants with checkboxes fails![gl-1](/uploads/4ef7cf6b8b67b0e784fadb2002700cbc/gl-1.png)
![gl-2](/uploads/d4291f1ad6a2bdfaecfb654e754cceba/gl-2.png)
Error message.
> Sorry, due to an error... '' is not a valid option for field custom_93![gl-1](/uploads/4ef7cf6b8b67b0e784fadb2002700cbc/gl-1.png)
![gl-2](/uploads/d4291f1ad6a2bdfaecfb654e754cceba/gl-2.png)
Error message.
> Sorry, due to an error... '' is not a valid option for field custom_935.2.0https://lab.civicrm.org/dev/core/-/issues/3574Password for mail accounts should not be stored in plain text2024-02-14T05:03:29ZscardiniusPassword for mail accounts should not be stored in plain textMySQL field civicrm_mail_settings.password contains password in plain text. Should it? I think not
This issue could by linked with https://lab.civicrm.org/dev/core/issues/236MySQL field civicrm_mail_settings.password contains password in plain text. Should it? I think not
This issue could by linked with https://lab.civicrm.org/dev/core/issues/236https://lab.civicrm.org/dev/wordpress/-/issues/81Synchronising WordPress Users and CiviCRM Contacts2020-11-24T15:11:13ZhaystackSynchronising WordPress Users and CiviCRM ContactsWhilst trying to clean up some logic in the CiviCRM-WordPress plugin I have come across a mismatch in how the CiviCRM-Drupal module and the CiviCRM-WordPress plugin synchronises the CMS User to the corresponding CiviCRM Contact. See [thi...Whilst trying to clean up some logic in the CiviCRM-WordPress plugin I have come across a mismatch in how the CiviCRM-Drupal module and the CiviCRM-WordPress plugin synchronises the CMS User to the corresponding CiviCRM Contact. See [this Mattermost thread](https://chat.civicrm.org/civicrm/pl/u95r1msnwinmdpne3kmjrwd8kh) for preliminary discussion.
There are currently two different types of call to `CRM_Core_BAO_UFMatch::synchronize()` happening:
1. In `CiviCRM_For_WordPress::initialize()` (set up the session)
2. In `CiviCRM_For_WordPress::invoke()` and `CiviCRM_For_WordPress_Users::sync_user()` (do a full User->Contact sync)
This is the reason for the behaviour that @totten identified and that I don't think should happen at that point, i.e.:
> If you access a `civicrm/*` page, then it autocreates a Contact.
As per the Mattermost discussion, it seems to me that the types of call should be:
1. In `CiviCRM_For_WordPress::initialize()` and `CiviCRM_For_WordPress::invoke()` (set up the session)
2. In `CiviCRM_For_WordPress_Users::sync_user()` (do a full User->Contact sync)
This pattern reverts the types of calls to their pre-4.6 state. My fault for the change back then :blush:
My proposal is to keep the calls to `CRM_Core_BAO_UFMatch::synchronize()` in both `CiviCRM_For_WordPress::initialize()` and `CiviCRM_For_WordPress::invoke()` but to make the calls indirectly via a new method in the `CiviCRM_For_WordPress_Users` class. The reason for this is that:
1. It is possible that some code calls `civi_wp()->initialize()`, `civicrm_wp_initialize()` or `civicrm_initialize()` before the WordPress User has been properly set up. I've seen this in the wild, though I can't remember where. When this happens, I don't think `CRM_Core_BAO_UFMatch::synchronize()` should be called. The `CiviCRM_For_WordPress_Users` class can keep track of the state of the WordPress User and make sure the call occurs only at the appropriate time.
2. If no calls have succeeded by the time `CiviCRM_For_WordPress::invoke()` runs, then `CRM_Core_BAO_UFMatch::synchronize()` will be called correctly when it's most definitely needed. The `CiviCRM_For_WordPress_Users` class will know if it's been called already.
I don't think this change will have any adverse effects (in fact it should have marginally beneficial effects by only calling `CRM_Core_BAO_UFMatch::synchronize()` when needed) but if anyone knows of code that expects Contacts to be created a `civicrm/*` page then shout here.haystackhaystackhttps://lab.civicrm.org/dev/core/-/issues/90Disable FULL GROUP BY where queries do not comply to allow for test runner to...2018-11-18T21:02:06ZseamusleeDisable FULL GROUP BY where queries do not comply to allow for test runner to switch to MySQL 5.7ping @eileen @monish.debping @eileen @monish.debseamusleeseamusleehttps://lab.civicrm.org/dev/core/-/issues/3641[Feature] More (privacy) options for click tracking2024-02-23T05:03:23Zmarcelklehr[Feature] More (privacy) options for click trackingHello,
I would like to have more options regarding click tracking in mailings.
1. Currently, every user can decide for themselves if they want to use it. I would like to be able override this with a setting, so i can e.g. disable click...Hello,
I would like to have more options regarding click tracking in mailings.
1. Currently, every user can decide for themselves if they want to use it. I would like to be able override this with a setting, so i can e.g. disable click tracking entirely.
2. Click-throughs are currently tracked by mail-adress, which is not conformant to the privacy laws in Germany, or at least requires additional consent. It would be nice to be able to limit this to just the numbers per link, without personal data. I would like to have this as an admin option, too.
Thanks for your consideration and this awesome software!https://lab.civicrm.org/dev/wordpress/-/issues/82Cannot create a WordPress account from the Contact record2021-10-16T08:08:01ZbgmCannot create a WordPress account from the Contact recordTo reproduce:
* As a WP admin, create a new contact record that has an email
* Click on the Actions menu
Expected: an option to create a new CMS account for this contact.
References:
* https://civicrm.stackexchange.com/questions/9092...To reproduce:
* As a WP admin, create a new contact record that has an email
* Click on the Actions menu
Expected: an option to create a new CMS account for this contact.
References:
* https://civicrm.stackexchange.com/questions/9092/wordpress-creating-new-wp-users-from-civi-contacts5.37.0https://lab.civicrm.org/dev/core/-/issues/91Prevent un-workable searches in search builder (was search builder improvements)2018-05-03T23:37:58ZMonish DebPrevent un-workable searches in search builder (was search builder improvements)Earlier there was a requirement where we need to remove specific MySQL operators which are not valid for specific data type e.g. String type doesn't work with >, <, <= and >= operators. And here's the fix https://github.com/civicrm/civic...Earlier there was a requirement where we need to remove specific MySQL operators which are not valid for specific data type e.g. String type doesn't work with >, <, <= and >= operators. And here's the fix https://github.com/civicrm/civicrm-core/commit/759094bdfa40531e4ec0cf0a644d9edd6b9247cf done earlier as per which it is fetching all columns which are String type and passing them into a separate JSON string identified as ```stringFields``` and another formatted list of valid string operators as ```stringOperators```. Similarly to identify date fields and to do a specific operation on such fields we are passing another variable ```dateFields```. These JSON object in JS are later used to specific operations. Now on the other hand, recently, I encountered another issue where the Boolean type columns don't work with IS EMPTY/IS NOT EMPTY operator and eventually leads to DB syntax error. So if I follow the same approach I need to assign another JSON string, which won't be an ideal fix. This lead me to do following 3 changes to improve the code:
1. Assign a single list of all data columns which are either Boolean, String or Date (as currently, these are the only kind that needs attention)
2. Use this list (as ```fieldTypes```) in JS to filter the operator or do field specific operations like covert a input search field to datepicker if the chosen search field is date kind.
3. Reduce list of variable assignment.5.2.0Monish DebMonish Debhttps://lab.civicrm.org/dev/core/-/issues/3567CiviMail: Provide transparency about (non)recipient details2023-09-05T10:28:43ZtottenCiviMail: Provide transparency about (non)recipient detailsTwo stories which are not-uncommon:
## Story 1
Someone starts using CiviMail. They spend a bunch of time arranging for the list of contacts (e.g. migrating from a previous system) and then go to send a mailing. They start composing a m...Two stories which are not-uncommon:
## Story 1
Someone starts using CiviMail. They spend a bunch of time arranging for the list of contacts (e.g. migrating from a previous system) and then go to send a mailing. They start composing a message and realize that the number of recipients is way off. What's going on? They start searching Google, Stackexchange, etc trying to understand why. Eventually, they learn that there are a half-dozen rules about who gets included or excluded from a mailing. (*Does the contact have an email address? Are they deceased? Have they opted-out of the specific mailing list? Have they opted-out of email generally? Have they had bounces? Does an extension - like GDPR - add more constraints?*) But they haven't solved the issue yet: now they need to figure out which criteria are affecting them, to what extent, and how to adapt.
And of course people have this problem - the "New Mailing" UX only presents the affirmative list of active recipients. It doesn't give any hint or detail about the omitted recipients.
![Screen_Shot_2019-09-03_at_12.58.40_PM](/uploads/73d40846bf379562ed119a317163b4e9/Screen_Shot_2019-09-03_at_12.58.40_PM.png)
## Story 2
A new user composes an email blast and discovers this incredible drop-down button with a list of tokens. They start throwing in tokens like there's no tomorrow. The blast goes out, and recipients complain: "Why are you sending me these weird messages with skipped words?"
And, again, of course people have this problem - the "New Mailing" UX lets you choose tokens without knowing if your recipient-data is up to the job.
## Discussion
These two stories are thematically similar: in both cases, we have a long list of potential recipients, and we have obscure/hidden criteria which determines whether the mailing goes out successfully to the target audience.
In both cases, there needs to be more transparency - adding UI-elements/UX-mechanisms to communicate what's going on. For example, the data-table in the pop-up might be updated with more columns/icons/color-coding.
I've logged the issue because I think, at some point, there should be discussion around design/resourcing. I don't want to prejudge that by saying the UX mechanisms to resolve these two issues must or must-not be the same - they might be totally different, or they might be one data-table. Either way, I think it's good to have a record of the issue.
## Related Links
* https://chat.civicrm.org/civicrm/pl/nn5rjzwiz3fc78pgojmhubx89a
* https://civicrm.org/blog/simonparkervitiligosocietyorguk/solution-all-recipients-not-showing-up-for-sending-mass-email
* https://civicrm.stackexchange.com/questions/5086/civimail-does-not-send-to-a-whole-group
* https://civicrm.stackexchange.com/questions/6346/after-import-to-group-individuals-in-that-group-not-showing-up-as-recipients-to
* https://civicrm.stackexchange.com/questions/26320/contacts-visible-in-mailing-list-group-not-on-hold-or-otherwise-dnd-but-skippe
* https://civicrm.stackexchange.com/questions/18199/in-mailing-all-recipients-are-not-showing/18201#18201
* https://civicrm.org/extensions/zombie-checkhttps://lab.civicrm.org/dev/wordpress/-/issues/83Avoid direct use of wp_new_user_notification2021-10-10T15:18:15ZBradley TaylorAvoid direct use of wp_new_user_notificationI was taking a look at https://github.com/civicrm/civicrm-core/pull/18982/ and noticed that CiviCRM currently calls `wp_new_user_notification` directly. Whilst this is not considered a private function in WordPress, I do believe its not ...I was taking a look at https://github.com/civicrm/civicrm-core/pull/18982/ and noticed that CiviCRM currently calls `wp_new_user_notification` directly. Whilst this is not considered a private function in WordPress, I do believe its not best practice to call it directly.
## The problem
`wp_new_user_notification` is a very opinionated function. A text-only email is sent via `wp_mail` with fixed (albeit translatable) text.
Site owners may want to replace this functionality:
- To disable new-user emails altogether
- To send a branded HTML email
- To send the email via an email service provider (MailChimp, DotDigital etc)
On sites I work on, we frequently replace the wp_new_user_notification with a more heavily branded custom email using code similar to this:
```
remove_action( 'register_new_user', 'wp_send_new_user_notifications' );
add_action( 'register_new_user', 'my_custom_new_user_notification' );
remove_action( 'edit_user_created_user', 'wp_send_new_user_notifications' );
add_action( 'edit_user_created_user', 'my_custom_new_user_notification' );
```
(Note slightly different actions would be needed to fully handle a multisite context).
These actions can also be used to trigger other functionality unrelated to email notifications.
## The solution
I would like to propose that CiviCRM replaces its direct call to `wp_new_user_notification` with a `do_action()` call, allowing the notification to be unhooked or replaced. The question in my mind is what action should be used. The options are:
- `register_new_user`
- `edit_user_created_user`
- A new CiviCRM specific action. (The `wp_send_new_user_notifications` function would then need to be attached to this action with `add_action`)
I don't have a particular preference either way on this last point.https://lab.civicrm.org/dev/core/-/issues/92Prevent deletion of groups which are used as search parameters of Smart Groups2023-04-20T08:59:49ZEvanPrevent deletion of groups which are used as search parameters of Smart GroupsIt seems that a group (static or Smart) being used a search parameter for a Smart Group can be deleted. Best case scenario is the Smart Group just has that many fewer contacts in it and we go on with life. We had an issue on a client sit...It seems that a group (static or Smart) being used a search parameter for a Smart Group can be deleted. Best case scenario is the Smart Group just has that many fewer contacts in it and we go on with life. We had an issue on a client site where there were so many contacts and so many groups, that rebuilding the Smart Group cache was causing a fatal DB error whether it (Updating Smart Group counts) was done manually or via the scheduled job. Proposed approach is to prevent deletion of groups that are dependencies for other groups. Example workflow:
1. A user with permissions to delete groups chooses to delete a group by selecting the "Delete" option from the "More" link on the Manage Groups page located here: Navigation Menu > Contacts > Manage Groups (this is the only place a user can delete a group, I believe)
1. The system (CiviCRM) does a check in the background to determine if the group being deleted is used as a search parameter in any active/non-deleted Smart Groups
1. If the group being deleted is determined to be "in use" by a Smart Group(s), don't allow the group to be deleted. Instead…
1. Show a message in the "Confirm Group Delete" notification that the group cannot be deleted as it's being used by a Smart Group(s). List the name of the Smart Group(s), preferably with the name(s) linked to that/those group(s)
I am inquiring with our client if they are willing to put funds (and how much) into fixing this. I have confirmed on demo master that one can delete a group that is a dependency for another group, though there were no ill effects. My assumption / theory is there just aren't enough contacts or groups for the rebuilding of Smart Group counts to fail.https://lab.civicrm.org/dev/core/-/issues/3642mailing.viewUrl token doesn't work in Drupal8 instance2022-06-14T21:21:06ZMonish Debmailing.viewUrl token doesn't work in Drupal8 instanceI wasn't able to replicate it in other CMSs but in Drupal8. When we sent a mail via cron, the 'View in your browser' link redirects to https://Array/ instead of https:://www.example.com/civicrm/mailing/view?reset=1&id=195. Strangely I w...I wasn't able to replicate it in other CMSs but in Drupal8. When we sent a mail via cron, the 'View in your browser' link redirects to https://Array/ instead of https:://www.example.com/civicrm/mailing/view?reset=1&id=195. Strangely I was not able to replicate it on test mail.
This is the fix which resolved my issue
```patch
diff --git a/CRM/Utils/Token.php b/CRM/Utils/Token.php
index b001c84..d1ad601 100644
--- a/CRM/Utils/Token.php
+++ b/CRM/Utils/Token.php
@@ -485,7 +485,7 @@ class CRM_Utils_Token {
$mailingKey = $hash;
}
$value = CRM_Utils_System::url('civicrm/mailing/view',
"reset=11&id={$mailingKey}",
- TRUE, NULL, FALSE, TRUE
+ TRUE
);
break;
```Monish DebMonish Debhttps://lab.civicrm.org/dev/wordpress/-/issues/84Fresh Install of 5.33 causes Fatal Error2021-01-07T09:47:05ZkcristianoFresh Install of 5.33 causes Fatal ErrorRan a new install of 5.33 today. On Plugin activation:
```
n error of type E_ERROR was caused in line 120 of the file /home/cv533/public_html/wp-content/plugins/civicrm/includes/civicrm.admin.php. Error message: Uncaught Error: Call t...Ran a new install of 5.33 today. On Plugin activation:
```
n error of type E_ERROR was caused in line 120 of the file /home/cv533/public_html/wp-content/plugins/civicrm/includes/civicrm.admin.php. Error message: Uncaught Error: Call to undefined method CiviCRM_For_WordPress_Admin::assert_php_pupport() in /home/cv533/public_html/wp-content/plugins/civicrm/includes/civicrm.admin.php:120
Stack trace:
#0 /home/cv533/public_html/wp-includes/class-wp-hook.php(287): CiviCRM_For_WordPress_Admin->run_installer('')
#1 /home/cv533/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array)
#2 /home/cv533/public_html/wp-includes/plugin.php(484): WP_Hook->do_action(Array)
#3 /home/cv533/public_html/wp-admin/admin.php(259): do_action('toplevel_page_c...')
#4 /home/cv533/public_html/wp-admin/options-general.php(10): require_once('/home/cv533/pub...')
#5 {main}
thrown
```
Plugin fatals on Activation, Install is just not possible.5.33.0https://lab.civicrm.org/dev/core/-/issues/93Update CRM_Utils_Rule::mysqlOrderBy() to accommodate more than 2 joins2018-11-10T00:41:10ZDon WijesooriyaUpdate CRM_Utils_Rule::mysqlOrderBy() to accommodate more than 2 joinsCurrently sorting only allows up to 2 joins: "membership_id.contact_id". If we go up a further level like "membership_id.contact_id.contact_type" it throws an error.
I suggest changing the regex:
```foreach ($parts as $part) {
...Currently sorting only allows up to 2 joins: "membership_id.contact_id". If we go up a further level like "membership_id.contact_id.contact_type" it throws an error.
I suggest changing the regex:
```foreach ($parts as $part) {
if (!preg_match('/^((`[\w-]{1,64}`|[\w-]{1,64})\.)?(`[\w-]{1,64}`|[\w-]{1,64})( (asc|desc))?$/i', trim($part))) {
return FALSE;
}
}```
to:
```/^((`[\w-]{1,64}`|[\w-]{1,64})\.)```{+ + +}```?(`[\w-]{1,64}`|[\w-]{1,64})( (asc|desc))?$/i```5.5.0https://lab.civicrm.org/dev/core/-/issues/3588Token unsubscribeUrl seemingly resolves to optOutUrl2022-06-11T14:55:01ZmarcelklehrToken unsubscribeUrl seemingly resolves to optOutUrlWhen using the action.unsubscribeToken in a mailing, the resulting URL prompts the user to confirm unsubscribing from all existing newletters instead of just the one that the link came with.When using the action.unsubscribeToken in a mailing, the resulting URL prompts the user to confirm unsubscribing from all existing newletters instead of just the one that the link came with.