@ruslan piskarov, thanks for the testing!
Committed to a brand new 1.2.x branch (a branch for D11 support).
Those changes will be a part of the future 1.2.0 module release.
A part of the changes are also committed at 📌 CI implementation for the module Active .
Committed to a brand new 1.2.x branch (a branch for D11 support).
Those changes will be a part of the future 1.2.0 module release.
Thanks!
@divyansh.gupta, please stop just move the patch files to merge requests on all issues without testing them, and mark issues as Needs review with failed pipelines. Thanks.
1) Please do not put `Needs review` status for MR with failed pipelines (if the branch pipeline is not failing). All pipelines must pass.
2) Were the changes tested with Mailgun API, or was the patch just moved to MR?
Thanks.
Changed the version of this issue. Version 2.2.0 is now released, which means new developments and disruptive changes should be targeted against the 2.2.x development branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Version 2.2.0 is now released, which means new developments and disruptive changes should be targeted against the 2.2.x development branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
If the issue's topic is actual in D10+ versions, please create a follow-up issue or comment on this one (to re-open and switch to the 2.2.x development branch).
Thanks!
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
Still, everyone can apply the patch above (not tested/reviewed by the maintainers) to their В7 projects.
If the issue's topic is actual in D10+ versions, please create a follow-up issue or comment on this one (to re-open and switch to the 2.2.x development branch).
Thanks!
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
Still, everyone can apply the patch above to their projects.
If the issue's topic is actual in D10+ versions, please create a follow-up issue or comment on this one (to re-open and switch to the 2.2.x development branch).
Thanks!
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
Still, everyone can apply the patch above (not tested by the maintainers) to their projects.
If the issue's topic is actual in D10+ versions, please create a follow-up issue or comment on this one (to re-open and switch to the 2.2.x development branch).
Thanks!
Additionally, the status has been changed as per comment #4 above.
Changed the version of this issue. Version 2.2.0 is now released, which means new developments and disruptive changes should be targeted against the 2.2.x development branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
If the issue's topic might be helpful in D10+ versions, please create a follow-up issue or comment on this one (to re-open and switch to the 2.2.x development branch).
Thanks!
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
If the issue's topic might be helpful in D10+ versions, please create a follow-up issue or comment on this one (to re-open and switch to the 2.2.x development branch).
Thanks!
Changed the version of this issue. Version 2.2.0 is now released, which means new developments and disruptive changes should be targeted against the 2.2.x development branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
This issue has been resolved as part of 📌 CI implementation Active .
A new release with D11 support has been released:
https://www.drupal.org/project/extrafield_views_integration/releases/2.2.0 →
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.
Thanks!
Thanks @konot for your contribution!
As for now:
- A new branch 2.2.x has been created.
- A new dev release 2.2.x-dev has been created.
- The current changes are committed to this new branch.
Those changes will be a part of a new stable release within
📌
Automated Drupal 11 compatibility fixes for extrafield_views_integration
Needs review
.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
As per MR:
1) It doesn't mention a possibility of
Key →
module usage.
2) It should contain an example with a code snippet for settings.php
Merge requests changes from the community will be incredibly welcome.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Duplicates ✨ Add domain specific Sending API Key Active
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Changed the version of this issue. Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
Merge requests from the community will be incredibly welcome.
Note: Only GitLab merge requests (not *.patch files) are reviewed by the currently active maintainer.
Thanks!
Mailgun 2.1.0 is now released, which means new developments and disruptive changes should be targeted against the 2.1.x-dev branch.
As per MR:
1) core_version_requirement should follow the identical core versions as the main module;
2) all phpcs warnings must be fixed;
3) let's add to the module title "(Experimental)" so users will be aware that the module is not well tested yet;
Thanks!
Hi @aaronbauman,
Thank you for the email ping!
Here are the results of it:
-
https://www.drupal.org/project/mailgun/issues/3451175#comment-16208934
📌
Automated Drupal 11 compatibility fixes for mailgun
Needs review
-
https://www.drupal.org/project/mailgun/releases/2.1.0 →
= = =
The active maintainer (me 🙃 ) is here.
Still, the module will be happy to receive contributions from anyone via merge requests, and the module is open to getting a new (additional) active maintainer onboard for its support/maintenance.
Once someone (interested in being an active maintainer) resolves a few (more or less complex) issues from the queue,
those issues and their corresponding MRs and/or comments will be reviewed/committed,
and new maintainership will be considered.
Feel free to ping further either on this issue or via drupal-org user contact form.
Thanks!
All the needed changes (on this issue and a few parallel ones) are committed to 2.1.x-dev branch.
The main module functionality was also tested locally on Drupal 11.1.8.
As a result, a new 2.1.0 release of the module (with D11 compatibility) has been released.
Here are the full release notes:
https://www.drupal.org/project/mailgun/releases/2.1.0 →
Many thanks to everyone for your contributions!
This is fixed now and committed to 2.1.x-dev branch.
This will be a part of the future module releases.
Committed to the 2.1.x-dev branch, and it will be part of the next module releases.
Thanks!
As:
- no further information has been provided to the maintainers in 3+ years,
- a few new versions of the module have been released after this issue was created,
the issue is now marked as "cannot reproduce".
If the issue remains active for D10+ versions, please either create a new follow-up issue or comment to re-open this one.
Thanks!
The SwiftMailer library is no longer maintained, and SwiftMailer module is obsolete and unsupported due to security issues.
@see:
https://www.drupal.org/project/swiftmailer →
This issue is now marked as outdated.
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.
Everyone can apply the patch above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.
Thanks!
This is fixed now and committed to 2.1.x branch (it will be a part of the future D11 release).
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
Still, everyone can apply the patch above (not tested by the maintainers) to their projects.
Thanks!
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.
All D7-related issues are marked as outdated in a bunch.
If/once the issue still arises in D10+ versions, please create a follow-up issue.
Thanks!
This one is fixed now at 2.1.x branch.
Thanks everyone for your contribution!
As for now:
- A new branch has been created.
- A new dev release 2.1.x-dev has been created.
- The current changes (MR #27) are committed to this new branch/version as a start for D11 compatibility release.
There are a few more checks and changes to create a non-dev version of the module for D11:
- there is section extra > drush > services in composer.json file (which states ` "^9 || ^10"`);
- all pipelines need to be green (before this non-dev version of the module) and all `allow_failure: true` should be removed;
- there is a chance that the test should be updated accordingly.
All of these will be addressed either in this issue or in separate issues in the following weeks.
And then, a new non-dev release of the module will be published.
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module. Development or support is not planned for D7.
Additionally, no support for the Rules module is planned (and its necessity for D10+ versions is doubtful).
This issue is marked as outdated.
If/once someone needed Rules support for D10+ version of Mailgun, please create a follow-up issue with your MR.
Thanks.
Just a quick overview:
1) cspell
The number of distinct unrecognised/misspelled words is 2
------------
doesn
extrafields
There is no much sense in creating separate issues to address those further.
We need to fix "doesn't" and to add "extrafields" to cspell allow a list of the module in this PR (as this is really quick fix to make this step green).
2) The same with phpcs - "Missing short description in doc comment"
This is a one-line and a few-second fix. I think it should be done here as well (with no additional issues).
Thanks!
We want to respect all people and companies that were taking part in Drupal Global Contribution Weekend Lutsk 2025 back in January.
With a bit of delay, but still for everyone: attendees, sponsors, partners, hosts, and volunteers!
The report details about mentors, sponsors, and volunteers will be available here:
https://www.facebook.com/media/set/?set=oa.934518842124605&type=3
Thanks to @all!
We want to respect all people and companies that were taking part in Drupal Global Contribution Weekend Lutsk 2024 back in January.
With a bit of delay, but still for everyone: attendees, sponsors, partners, hosts, and volunteers!
The photo report is available here:
https://www.facebook.com/media/set/?set=oa.2507987712714139&type=3
Thanks to @all!
We want to respect all people and companies that were taking part in Drupal Global Contribution Weekend Lutsk 2025 back in January.
With a bit of delay, but still for everyone: attendees, sponsors, partners, hosts, and volunteers!
The photo report is available here:
https://www.facebook.com/media/set/?set=oa.934518842124605&type=3
Thanks to @all!