You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fixed
A page template declared in the theme's config/templates.php is rendered by its Blade view: WordPress puts the template slug first in the page hierarchy without extension (landing), which Pollora looked up as a file named landing instead of landing.blade.php, so page.blade.php answered (#159)
Before the database is configured, the WordPress fallback route answers 503 instead of 500 (Call to undefined function wp_using_themes()): with APP_DEBUG, a "Pollora is not set up yet" page names the missing settings (DB_CONNECTION=mysql, DB_HOST, DB_DATABASE, DB_USERNAME, DB_PASSWORD) and the commands to run (pollora:env:setup, pollora:install, pollora:doctor); without it, the application's or Laravel's 503 page. Laravel routes keep working (#78)
composer create-project pollora/pollora without a database no longer ends with a failing script ("Database name is required"): Composer runs pollora:env:setup without a terminal, which the command now treats as non-interactive, printing the settings to fill and the commands to run (#78)
A theme, plugin or module whose Vite build is missing (npm absent, a failed build, public/build deleted) no longer takes the whole site down: every request, wp-login.php and wp-admin included, answered 500 Vite manifest not found because blocks resolve their scripts while WordPress boots. A container with neither a hot file nor a manifest now gives no asset URLs (blocks register without scripts, Asset::url() gives an empty string), the missing build is logged once per request and an admin notice names the manifest and the commands to run (npm run build, pollora:doctor) (#79)