4.0.2

Summary

• use wpdb->last_error directly when get_results() returns null
• enrich record-not-found exceptions with the actual query or update identity context
• improve support visibility for hidden WordPress datastore failures

Included

• #27

Why

This patch came out of the Siren obligation investigation. The WordPress query layer was discarding the most useful wpdb error text and throwing unhelpful not-found exceptions in the exact places support needed more context.

4.0.1

Allow phpnomad/loader ^2.0 and phpnomad/framework ^3.0 for phpnomad/di v2.0 compatibility.

v4.0.0

Breaking Changes

• TranslationStrategy updated for phpnomad/translate v2.0.0
  • Old: translate(string $translate, ?string $language, $context): string
  • New: translate(string $text, ?string $context = null): string and translatePlural(string $singular, string $plural, int $count, ?string $context = null): string
• HasLanguage removed from constructor — WordPress manages locale via its own globals
• Requires phpnomad/translate ^2.0

Bug Fixes

• Fixed _x() call — was passing domain as context argument instead of the actual context

3.0.2

What's Changed

• Fix: Correct option parameter parsing in ConsoleStrategy by @alexstandiford in #26

Full Changelog: 3.0.1...3.0.2

Release 3.0.1

updates SiteVisited trigger to parse_request, refines REST context detection.

Release 3.0.0

What's Changed

A sore spot in WordPress is background tasks. Yes, it's been solved several times, but to this day, there's still a fair bit of scaffolding that goes just into making it possible to do.

That's why I'm so excited that I've published a new update to PHPNomad's WordPress integration to finally leverage the tasks integration that I've been using for several months in non-WordPress solutions.

This update makes it possible to use PHPNomad to dispatch asynchronous tasks consistently, and reliably in WordPress in exactly the same way it's done outside of WordPress.

This update comes in the 3.0 version of the WordPress integration and up. Behind the scenes it leverages WooCommerce's action scheduler utility, automatically loading it and bundling it into any plugin that you create using PHPNomad.

The power of this comes from the changes that came to the task library in 2.0, which includes a nice decoupled architecture, separating tasks from execution and working much like how event architecture.

Adds support for PHPNomad tasks and action scheduler, drastically improving background task support in WordPress and making asynchronous tasks possible.

• Issue/18 by @alexstandiford in #24

Full Changelog: 2.1.0...3.0.0

Release 2.1.0

Full Changelog: 2.0.5...2.1.0

2.0.5

Adds support for WP CLI commands via PHPNomad console

2.0.3

What's Changed

• deps(deps): bump phpnomad/auth from 1.0.0 to 1.0.1 by @dependabot in #8
• deps(deps): bump phpnomad/cache from 1.0.1 to 1.0.2 by @dependabot in #7
• deps(deps): bump phpnomad/db from 2.0.0 to 2.0.1 by @dependabot in #6
• Fix package dependency issue by @malayladu in #9
• Fix http namespace issue by @malayladu in #10
• Fixed namespace by @malayladu in #11

New Contributors

• @malayladu made their first contribution in #9

Full Changelog: 2.0.1...2.0.3

2.0.1

What's Changed

• deps(deps): bump phpnomad/cache from 1.0.0 to 1.0.1 by @dependabot in #5

Full Changelog: 2.0.0...2.0.1