Pollora 13.35.2: asynchronous actions
Add ->async() to an action, or #[Async] next to #[Action], and its handler runs after the request, through a Laravel queue worker, Action Scheduler or WP-Cron.
The Pollora blog
News from the hive
Releases and the reasons behind them, what we are building next, and tutorials that go from an empty file to a working page.
-
On the roadmap: async actions, in one word
A slow handler on save_post slows down every editor who saves. We are designing async() and #[Async] to move it out of the request, on WP-Cron, Action Scheduler or a Laravel queue, without changing the handler.
- Release v13.35.0
Pollora 13.35: typed meta, roles in code and Block Bindings
Declare a meta once as a typed PHP property, describe roles as classes, and fill core blocks with server values. Three experimental features that remove a lot of stringly-typed WordPress code.
- Release v13.34.0
Pollora 13.34: the first stable release
Eleven pre-releases later, Pollora is stable. It moves to Laravel 13.34, ships a command that finds the failures that stay silent, and adds a Full Site Editing theme to start from.
- Tutorial v13.32.0-beta.9
Build a Gutenberg block in Blade, inner blocks included
A step-by-step tutorial. Scaffold a dynamic block, render it with a Blade template, then let editors write inside it with <InnerBlocks />, the tag ACF users already know.
- Release v13.32.0-beta.5
Your login screen, dressed in your theme
Every WordPress site signs people in through the same grey form. From beta.5, Pollora prints your theme's colours, fonts and logo on wp-login.php, read straight from theme.json.
- Announcement v13.32.0-beta
Pollora is in public beta
WordPress running inside a Laravel application, with hooks, post types and REST routes declared as PHP attributes. The first public beta is out, and its version number now follows Laravel's.