Skip to content

Releases: soup-bowl/simple-smtp

1.3.4.1

11 Aug 18:55
022b999

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.3.4...1.3.4.1

1.3.4

09 Aug 21:37
d1023d2

Choose a tag to compare

What's Changed

  • Branding changes to comply with WordPress trademark policies.
  • Bump the dev-dependencies group with 5 updates by @dependabot[bot] in #155
  • Bump the dev-dependencies group with 1 update by @dependabot[bot] in #158
  • WordPress Coding Standards Linting by @soup-bowl in #157
  • Automatic Changelog by @soup-bowl in #159
  • Pipeline replacement for asset upload by @soup-bowl in #160
  • Bump the dev-dependencies group with 2 updates by @dependabot[bot] in #163
  • Bump phpunit/phpunit from 9.6.18 to 9.6.19 in the dev-dependencies group by @dependabot[bot] in #167
  • Change log expiry via hook & expiry visibility by @soup-bowl in #165
  • Verify post type before executing delete by @soup-bowl in #169
  • Bump vlucas/phpdotenv from 5.6.0 to 5.6.1 in the dev-dependencies group by @dependabot[bot] in #171

Full Changelog: 1.3.3...1.3.4

Version 1.3.3

12 Oct 21:02
d0da416

Choose a tag to compare

  • Verified working with WordPress 6.3.
  • Fix: $log_service deprecation notice (#146).
  • Added: None encryption setting (#148).

Version 1.3.2.2

12 Apr 20:10
a910a43

Choose a tag to compare

  • Verified working with WordPress 6.1 and 6.2.
  • Fix: PHP warning on the CLI interface (#140).

ℹ️ Notice

You may notice there's 3 unexpected new files in the wp-simple-smtp directory:

  • DOCKER_ENV
  • docker_tag
  • output.log

These files were unfortunately introduced during the deployment pipeline, and have subsequently been packaged into the release file. I've since added these to the exclusion list, so in later deployments they won't be present.

Until next release, you can delete these files without detrimental effect. Next update should remove these anyway.

Version 1.3.2.1 (Hotfix)

22 Oct 19:04
c18f806

Choose a tag to compare

  • Rollback: #116 fix regressed due to relying on a function not found in the general scope.

Version 1.3.2

01 Oct 13:03
870692f

Choose a tag to compare

  • Added: Mail view now displays from, cc, bcc & the headers stored when logging is enabled.
  • Fix: Infinite loop when a plugin hooks into the mail routine functions and sends an email (#116).

Version 1.3.1.1

22 May 20:22
c3d844b

Choose a tag to compare

  • Verified working with WordPress 6.0.

Note: #109 has not reached main yet, so the deployment hasn't fully succeeded. However this release is purely to update the WordPress state, and is not required for GitHub & manual deployments.

Version 1.3.1

09 Apr 21:03
78bc02c

Choose a tag to compare

  • Added: Glance view on the dashboard to see mail usage (Thanks Kebbet - PR 101, PR 102).
  • Fix: Table view appears correctly on mobile (Thanks Kebbet - PR 93).
  • Fix: Log view table navigation (Thanks Kebbet - PR 106).

Version 1.3

23 Jan 15:50
2946c9d

Choose a tag to compare

The minor release version is bumped for capability changes and the log storage goes from indefinite to monthly. A filter is provided to reverse this change, and it does not take effect on new installs, but this will hopefully reduce the contribution to database bloat and data collection that can fall foul of GDPR restrictions (although users switching back to indefinite can benefit from privacy integrations).

  • Added: Read logged emails via WP-CLI.
  • Added: Status message from testing emails (#81).
  • Change: Uninstalling the plugin will remove the lingering logs (#70).
  • Change: (For new installs) logs purge automatically after a month (#71).
  • Change: Quick config settings now contained within plugin (#78).
  • Change: Tightened permissions to the log viewer (#74).
  • Fix: Incorrect capability type used by the log viewer. Thanks to Benoît Chantre #74.

Version 1.2.3

12 Dec 23:35

Choose a tag to compare

  • Add: WordPress CLI support. See the FAQ for usage details.
  • Change: Password not returned plaintext in settings (#61).
  • Fix: Multisite-only config caused an instantiation error (#67).