Release Notes

v4.1.1

What changed

• ui-livewireflux-admin:install: Fortify publish now uses --tag=fortify-support only (action stubs under app/Actions/Fortify/, etc.). Fortify database migrations (fortify-migrations, including two-factor and passkeys) are no longer published by install, avoiding duplicate-column errors on apps that already had those columns. Publish migrations manually when needed: php artisan vendor:publish --tag=fortify-migrations (see README.md and docs/GUIDE.md).
• Docs & CLI: README.md documents optional Fortify migrations; docs/GUIDE.md explains Fortify tags and safer --force on fortify-support; php artisan ui-livewireflux-admin:help adds troubleshooting and an example for fortify-migrations.

Upgrade notes

• Existing apps: No action required if you already migrated. New installs that need Fortify’s 2FA/passkeys schema must run vendor:publish --tag=fortify-migrations (then migrate) when that schema is not already present.
• Re-publish Fortify stubs: Prefer vendor:publish --provider="Laravel\Fortify\FortifyServiceProvider" --tag=fortify-support (and --force only on that tag) instead of publishing the whole Fortify provider with --force, which can republish migrations and reintroduce duplicate files.

v4.1.0

What changed

• Composer require: livewire/livewire is now ^4.0 (previously ^4.1), so apps on Livewire 4.0.x satisfy the dependency without being forced to 4.1+ for this package alone.

Upgrade notes

• No stub or API changes. If you already use Livewire 4.1 or newer, behavior is unchanged. If composer update previously failed because you stayed on Livewire 4.0.x, try again after upgrading to this release.

Release Notes

v4.0.2

What changed

• Install publishes Fortify app stubs: php artisan ui-livewireflux-admin:install runs vendor:publish for Laravel\Fortify\FortifyServiceProvider when app/Actions/Fortify/PasswordValidationRules.php is missing, so admin views that use App\Actions\Fortify\PasswordValidationRules work out of the box. If publish fails or the file is still missing, the installer prints the manual command and points to docs/FORTIFY-IS-ACTIVE.md (including optional --force re-publish).
• Documentation: docs/FORTIFY-IS-ACTIVE.md covers PasswordValidationRules, install behavior, and careful use of --force. docs/ROLE-ON-REGISTRATION.md notes that CreateNewUser.php comes from Fortify publish. docs/UI-GUIDE.md and docs/AI-GUIDE.md clarify password forms and when App\... Fortify classes are intentional.
• README: Changelog section removed (release history lives here and in git tags). Install and verify steps updated for Fortify publish.
• ui-rules.mdc: Corrected outdated Volt / “light mode only” guidance; aligned with Livewire 4 anonymous components and dark:* stubs; points to the docs above.

Why this release

Consuming apps often lacked Fortify-published PasswordValidationRules and related actions, which broke admin user create/edit stubs. Automating Fortify publish during install (with safe skip when already present) reduces that failure mode.

Upgrade notes

• New installs: run php artisan ui-livewireflux-admin:install as usual; Fortify stubs publish when needed.
• Existing apps missing only PasswordValidationRules (or other Fortify files): see docs/FORTIFY-IS-ACTIVE.md for normal publish vs --force (backup customizations first).

v4.0.1

What changed

• Removed hardcoded Livewire layout from admin stubs: all admin stub page components no longer use #[Layout('layouts.admin')] and now rely on your app’s default Livewire layout.
• Updated docs + guides: README.md, docs/UI-GUIDE.md, and docs/AI-GUIDE.md were updated to match the new “default layout” approach.

Why this release

Projects without a layouts.admin view were hitting: Livewire page component layout view not found: [layouts.admin]. Removing the attribute prevents that mismatch and lets the consuming app control layout globally.

Upgrade notes

• If you previously published/copied the admin stub views into your app, re-run your package update/install flow (or manually remove #[Layout('layouts.admin')] from those files).

Release Notes

v4.0.1

What changed

• Removed hardcoded Livewire layout from admin stubs: all admin stub page components no longer use #[Layout('layouts.admin')] and now rely on your app’s default Livewire layout.
• Updated docs + guides: README.md, docs/UI-GUIDE.md, and docs/AI-GUIDE.md were updated to match the new “default layout” approach.

Why this release

Projects without a layouts.admin view were hitting: Livewire page component layout view not found: [layouts.admin]. Removing the attribute prevents that mismatch and lets the consuming app control layout globally.

Upgrade notes

• If you previously published/copied the admin stub views into your app, re-run your package update/install flow (or manually remove #[Layout('layouts.admin')] from those files).

v4.0.0

What changed

• Fixed stub trait import: Livewire stub views now import WithNotifications from the Vormia package namespace:
  • Vormia\Vormia\Traits\Livewire\WithNotifications
• Updated Taxonomy model usage in stubs: stub views no longer reference \App\Models\Vrm\Taxonomy; they now use:
  • Vormia\Vormia\Models\Taxonomy
• Updated MediaForge import in stubs: stub views now import:
  • VormiaPHP\Vormia\Facades\MediaForge
• Added build guides:
  • docs/UI-GUIDE.md (flow + style guide for building consistent admin UI)
  • docs/AI-GUIDE.md (promptbook + workflow for using AI to generate consistent UI)

Why this release

Fresh installs (or projects without local App\... shims) could break because some shipped stub views were referencing app namespaces. This release aligns stub imports and model usage with the package-provided namespaces.

Upgrade notes

• If you previously copied older stubs into your app, re-run your install/update flow (or manually update your copied files) so your local Livewire views match the new namespaces.

Release Notes

v4.0.0

What changed

• Fixed stub trait import: Livewire stub views now import WithNotifications from the Vormia package namespace:
  • Vormia\Vormia\Traits\Livewire\WithNotifications
• Updated Taxonomy model usage in stubs: stub views no longer reference \App\Models\Vrm\Taxonomy; they now use:
  • Vormia\Vormia\Models\Taxonomy
• Updated MediaForge import in stubs: stub views now import:
  • VormiaPHP\Vormia\Facades\MediaForge
• Added build guides:
  • docs/UI-GUIDE.md (flow + style guide for building consistent admin UI)
  • docs/AI-GUIDE.md (promptbook + workflow for using AI to generate consistent UI)

Why this release

Fresh installs (or projects without local App\... shims) could break because some shipped stub views were referencing app namespaces. This release aligns stub imports and model usage with the package-provided namespaces.

Upgrade notes

• If you previously copied older stubs into your app, re-run your install/update flow (or manually update your copied files) so your local Livewire views match the new namespaces.

• Restored all admin stub views and AdminPanel component
• Upgraded all Livewire components to Livewire 4 (Livewire\Component + #[Layout('layouts.admin')])
• Removed all Livewire\Volt\Component references

Allowing Laravel 13 support

Changelog

All notable changes to vormiaphp/ui-livewireflux-admin will be documented here.

v3.0.5 - 2026-03-11

• Add UILivewireFluxAdminServiceProvider.
• Register all package Artisan commands when the application is running in the console.
• Fix Laravel package discovery error for the missing service provider.

v3.0.4 - 2026-03-11

• Require vormiaphp/vormia ^5.0 and livewire/livewire ^4.0 only.
• Tighten dependency constraints to match Vormia v5 stack.

v3.0.3 - 2026-03-11

• Support vormiaphp/vormia ^5, livewire/flux ^2, and laravel/fortify ^1|^2.
• Improve composer constraints for better compatibility.

v3.0.2 - 2026-03-11

• Require Flux and Fortify when using Vormia v5.
• Drop explicit Volt requirement (bundled with Livewire 4).
• Update README to clarify Vormia v5 / Livewire 4 assumptions.

Release Notes — Vormia UI Livewire Flux Admin

Package

vormiaphp/ui-livewireflux-admin — Admin panel for Laravel apps using Livewire Volt and Flux (Vormia ecosystem).

What’s New (v3.x)

Vormia v5 & stack

• Vormia v5 — Package targets Vormia v5 (README: vormiaphp/vormia ^5.0, no less).
• Flux & Fortify — livewire/flux ^1.0 and laravel/fortify ^2.0 are required.
• Volt — Volt is not a separate dependency; with Vormia v5 / Livewire 4 it’s bundled with Livewire.
• Laravel & PHP — Laravel ^12.0, PHP ^8.2.

Admin panel features

• AdminPanel component — Reusable Blade component for consistent admin layouts (<x-admin-panel>).
• Pre-configured admin routes — CRUD under /admin for:
  • Categories, Inheritance, Countries, Cities, Availability, Admins
• Livewire Volt components — Single-file components per section (index, create, edit) for:
  • Admins, Categories, Inheritance, Locations (countries/cities), Availability
• Sidebar integration — Automatic injection of admin menu into the Flux sidebar (Platform group); reference stubs in src/stubs/reference/.
• Role management — Documentation for using Vormia\Vormia\Models\Role and assigning roles on registration (see docs/ROLE-ON-REGISTRATION.md).
• Fortify — Optional EnsureUserIsActive.php stub and docs (docs/FORTIFY-IS-ACTIVE.md) for active-user checks.

Artisan commands

• ui-livewireflux-admin:install — Install (copy stubs, inject routes & sidebar, optional Fortify stub, clear caches).
• ui-livewireflux-admin:update — Update package files (with backup under storage/app/ui-livewireflux-admin-backups/).
• ui-livewireflux-admin:uninstall — Remove installed files, routes, and sidebar items.
• ui-livewireflux-admin:help — Show usage and troubleshooting.
• ui-livewireflux-admin:check-dependencies — Verify required packages (Vormia, Flux, Fortify).

Documentation & clarity

• README updated for Livewire 4 / Volt (no separate Volt install).
• Role management and Vormia integration clarified (Role model, registration).
• Changelog section in README for v3.0.0.

Quick reference

You can delete this file after use; it is not intended to be committed.

Full Changelog: https://github.com/vormiaphp/ui-livewireflux-admin/compare/v3.0.0...v3.0.1

Release Notes – v3.0.0

Release Date: March 1, 2025

Summary

Version 3.0.0 introduces improved Fortify integration, better sidebar integration, and a simplified project structure.

What's New

Fortify Integration

• EnsureUserIsActive only – The install process now copies EnsureUserIsActive.php instead of CreateNewUser.
• Role assignment – Role assignment on registration is documented in docs/ROLE-ON-REGISTRATION.md; this package no longer modifies CreateNewUser.
• HelpCommand – Updated to describe the new role assignment flow and Fortify integration.

Sidebar Integration

• Path resolution – Sidebar checks both resources/views/layouts/app/sidebar.blade.php and resources/views/components/layouts/app/sidebar.blade.php.
• InstallCommand / UninstallCommand – Improved sidebar detection and clearer feedback when the sidebar menu is injected or must be added manually.

Project Structure

• Cleanup – Removed redundant files (including the old CHANGELOG.md).
• Documentation – README updates for role management and sidebar integration, plus a changelog section in the README.

Dependencies

• livewire/livewire added as an explicit requirement (^3.0 || ^4.0).
• laravel/fortify suggestion version set to ^2.0.

Upgrade from v2.x

1. Run composer update vormiaphp/ui-livewireflux-admin.
2. If you use Fortify: role assignment logic is no longer in this package; see docs/ROLE-ON-REGISTRATION.md for setup.
3. Run php artisan ui-livewireflux-admin:update to refresh stubs if needed.

Requirements

• PHP >= 8.2
• Laravel >= 12.0
• vormiaphp/vormia ^2.0 || ^3.0 || ^4.0
• livewire/livewire ^3.0 || ^4.0
• livewire/volt ^1.0

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[2.0.2] - 2026-01-29

Added

• Fortify integration: InstallCommand now copies EnsureUserIsActive.php and FortifyServiceProvider.php from package stubs into the application for Laravel Fortify user-activation support
• UninstallCommand Fortify handling: UninstallCommand warns when removing EnsureUserIsActive and reverting FortifyServiceProvider changes; file operations skip backup files

Improved

• Photo validation: Consolidated photo validation rules in admin edit view into a single line; removed unnecessary array wrapper
• Admin edit view: Clearer HTML structure in the admin information section
• File handling: Stub operations skip backup files (e.g. *.backup) in UILivewireFlux file handling

[2.0.1] - 2025-01-29

Improved

• Admin edit view: Refactored photo validation and improved code readability

[2.0.0] - 2024-12-19

Added

• Dark Mode Support: Full dark mode support for all admin panel components and views
• Improved Uninstallation: Enhanced uninstall process that properly clears sidebar menu items and restores default configurations

Improved

• Route Removal: Route removal process now completes without errors, ensuring clean uninstallation
• Sidebar Menu Clearing: Uninstall command now properly clears all sidebar menu items added during installation
• Default Restoration: Fortify CreateNewUser.php file is now restored to default state during uninstallation, removing any custom role attachments

Changed

• Backward Compatibility: This release maintains full backward compatibility with previous versions while introducing new features and improvements

[1.0.5] - 2024-12-19

Improved

• Sidebar Menu Installation: The installation command now correctly finds and inserts the sidebar menu after the Platform navlist.group closing tag instead of after the Dashboard menu item. This provides more reliable insertion point detection.
• Sidebar Menu Uninstallation: The uninstall command has been enhanced to read exact patterns from the stub file (sidebar-menu-to-add.blade.php) for more accurate removal of menu items. This ensures all menu items are properly removed during uninstallation.
• Pattern Matching: Improved pattern matching logic for sidebar menu injection with better handling of whitespace variations and formatting differences.

Changed

• Sidebar menu insertion point changed from "after Dashboard menu item" to "after Platform navlist.group closing tag"
• Uninstall command now uses a two-pass approach: first identifies lines to remove, then builds new content without removed lines

Fixed

• Fixed sidebar menu injection to work correctly with the Platform group structure
• Improved accuracy of sidebar menu removal during uninstallation

[1.0.4] - Previous Release

[Previous release notes...]

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[2.0.0] - 2024-12-19

Added

• Dark Mode Support: Full dark mode support for all admin panel components and views
• Improved Uninstallation: Enhanced uninstall process that properly clears sidebar menu items and restores default configurations

Improved

• Route Removal: Route removal process now completes without errors, ensuring clean uninstallation
• Sidebar Menu Clearing: Uninstall command now properly clears all sidebar menu items added during installation
• Default Restoration: Fortify CreateNewUser.php file is now restored to default state during uninstallation, removing any custom role attachments

Changed

• Backward Compatibility: This release maintains full backward compatibility with previous versions while introducing new features and improvements

[1.0.5] - 2024-12-19

Improved

• Sidebar Menu Installation: The installation command now correctly finds and inserts the sidebar menu after the Platform navlist.group closing tag instead of after the Dashboard menu item. This provides more reliable insertion point detection.
• Sidebar Menu Uninstallation: The uninstall command has been enhanced to read exact patterns from the stub file (sidebar-menu-to-add.blade.php) for more accurate removal of menu items. This ensures all menu items are properly removed during uninstallation.
• Pattern Matching: Improved pattern matching logic for sidebar menu injection with better handling of whitespace variations and formatting differences.

Changed

• Sidebar menu insertion point changed from "after Dashboard menu item" to "after Platform navlist.group closing tag"
• Uninstall command now uses a two-pass approach: first identifies lines to remove, then builds new content without removed lines

Fixed

• Fixed sidebar menu injection to work correctly with the Platform group structure
• Improved accuracy of sidebar menu removal during uninstallation

[1.0.4] - Previous Release

[Previous release notes...]

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[1.0.5] - 2024-12-19

Improved

• Sidebar Menu Installation: The installation command now correctly finds and inserts the sidebar menu after the Platform navlist.group closing tag instead of after the Dashboard menu item. This provides more reliable insertion point detection.
• Sidebar Menu Uninstallation: The uninstall command has been enhanced to read exact patterns from the stub file (sidebar-menu-to-add.blade.php) for more accurate removal of menu items. This ensures all menu items are properly removed during uninstallation.
• Pattern Matching: Improved pattern matching logic for sidebar menu injection with better handling of whitespace variations and formatting differences.

Changed

• Sidebar menu insertion point changed from "after Dashboard menu item" to "after Platform navlist.group closing tag"
• Uninstall command now uses a two-pass approach: first identifies lines to remove, then builds new content without removed lines

Fixed

• Fixed sidebar menu injection to work correctly with the Platform group structure
• Improved accuracy of sidebar menu removal during uninstallation

[1.0.4] - Previous Release

[Previous release notes...]

v1.0.2 (Current) Fixed admin-panel.blade.php references in UILivewireFlux, UpdateCommand, and UninstallCommand Removed duplicate admin-panel.php file (kept only .blade.php) Standardized all file references to use .blade.php extension Updated category management: replaced 'Video' with 'Category' references Enhanced README with installation note for existing vormia users