fix: catch Nectar up with framework v13.32 - #2
Merged
Merged
Conversation
active_theme_info read resources/blocks only, where themes no longer keep their blocks: it reported none. It reads resources/views/blocks, counts a directory only when it holds a block.json, and reports the blocks left in the deprecated resources/blocks separately.
The guidelines listed the Loop and Query facades, removed from the framework, and the blocks skill taught resources/blocks, render.php and a hand-written BlocksServiceProvider. They now teach what v13.32 does: blocks in resources/views/blocks rendered with Blade and registered by Pollora, the facades that exist, __() routing, pollora_register(), #[Ajax], #[Ability], #[SkipDiscovery], the login screen, the template marker, the full list of commands, and the 13.x requirements. A pollora-abilities skill covers the WordPress Abilities API.
No prompt covered the move from 13.4 to 13.32, whose breaking changes are many: composer-patches 2, renamed commands, classes moved to extracted packages, Loop and Query removed, blocks moved, skeleton files changed. The upgrade-pollora-v13-32 prompt walks through them, registered when 13.0 to 13.4.x is installed. The 12 to 13 prompt no longer adds a copy-theme-json build step: copying the built theme.json over the theme's own froze its palette.
orchestra/testbench stopped at ^10, Laravel 12, so the suite ran against pollora/framework 12.0 whatever the package claimed. It accepts ^11 now, and pollora/framework is bounded to ^12.0 || ^13.0 instead of *. On framework 13, Pollora's Route class has the methods WordPressRoutes probed with method_exists(): the probes and their phpstan-ignore comments go.
This was referenced Sep 28, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nectar had not followed the framework since 0.2.0 (June 2026): its guidelines, which Boost copies into every project's
AGENTS.md, and its skills taught things v13.32 removed or changed. Audit: every framework change from v13.4.1 to v13.32.0-beta.8 checked against Nectar.Wrong, now fixed
active_theme_infolisted no block for a theme made since v13.32: it readresources/blocksonly. It readsresources/views/blocks(a directory counts only with ablock.json) and reportsblocks_in_deprecated_directory.LoopandQueryfacades, removed from the framework (their aliases made pages crash).pollora-blocksskill taughtresources/blocks,--dynamic+render.php, and a hand-writtenBlocksServiceProvider(whose blocks exist in WP-CLI only). Rewritten:resources/views/blocks, dynamic Blade blocks by default,--static, registration by Pollora, migration steps.copy-theme-jsonbuild step — the step that froze apiary's palette (fix: keep the palette to the theme's own colours, each with a value theme-apiary#11). Removed, with the reason.pollora:make-post-type→pollora:make:post-type; 13.x guidelines:illuminate/*^13.32, WordPress 7.Missing, now covered
upgrade-pollora-v13-32prompt, registered for 13.0 to 13.4.x: dependencies and wp-packages, composer-patches 2 (patches-relock,patches.lock.json, checking WordPress is patched), renamed commands, class map forpollora/hook/option/ajax,Loop/Queryreplacements,Translaterdomain, blocks, skeleton files (routes/web.php, cache table,.htaccess), theme.json from@theme.pollora-abilitiesskill (WordPress Abilities API).pollora_register(),#[Ajax],#[Ability],#[SkipDiscovery],__()routing, login screen,get_theme_file_uri(), template marker, full command list.Package
orchestra/testbenchstopped at^10. It accepts^11now;pollora/frameworkis bounded to^12.0 || ^13.0instead of*.WordPressRoutesno longer needsmethod_exists()probes and@phpstan-ignorecomments.Checked
@theme,@posts,#[Ajax]and the marker come through intact.Not in this PR: the release (
Nectar.phpstill says 0.2.0 while the only tag isv1.0.0; to align at release time).