Weave Code
Profile Laravel Package
laralum/profile
Laralum Profile is a profile management module for the Laralum admin panel, letting users view and update personal details, avatars, and account information. It integrates with Laravel and Laralum’s authentication and permissions system.
Profile module for laralum
Frequently asked questions about Profile
- What is Laralum Profile and what does it add to a Laravel application?
- Laralum Profile is a profile management module for the Laralum administration panel. It gives authenticated users a dedicated page to view and update their account details, avatars, and personal information. Instead of writing custom controllers and views, you get profile screens that follow Laralum's existing user model, routing, and menu conventions.
- How do I install laralum/profile with Composer?
- Install it with composer require laralum/profile from your Laravel project root. Because it is a Laralum module, it expects the core laralum/laralum package to already be installed and configured. After installation, register the module's service provider following Laralum's module registration convention and publish any config or view assets with artisan vendor:publish if the package ships them.
- Does Laralum Profile work without the Laralum admin panel?
- No. Laralum Profile is built as a module on top of Laralum, so it depends on Laralum's user model, routing, permissions, and menu system. If you only need profile editing in a plain Laravel app, a dedicated package such as Laravel Breeze, Jetstream, or Fortify is a better fit. Laralum Profile is intended for projects already standardised on the Laralum panel.
- Which Laravel versions are supported by Laralum Profile?
- Laralum and its modules target the Laravel 5.x era and follow that generation's service provider and package discovery conventions. Because the repository metadata is not published here, always check the composer.json requirements of the exact version you install before upgrading Laravel. Running it on modern Laravel releases is likely to require adaptation work.
- How do I customize the profile routes and Blade views?
- Routes and views are configurable rather than hard-coded, which is the point of the module's Laralum integration. Publish the package assets and override the Blade templates in your application's resources/views directory to change the profile layout or field markup. Route prefixes and middleware can be adjusted through the published configuration so the profile pages sit behind your existing auth and permission middleware.
- Can I add custom profile fields to the profile page?
- Yes, the module is described as extensible for custom profile fields. In practice you extend the user-related model or migration with the extra columns, then add the matching inputs to the overridden profile Blade view. Remember to add validation and mass-assignment protection for any new attributes so users cannot write to fields they should not control.
- How does Laralum Profile integrate with Laralum users and permissions?
- It hooks into Laralum's existing user model and permission layer instead of defining its own authentication stack. That means access to the profile pages can be governed by the same roles and permissions you already use across the panel. It also registers a menu entry so users can reach their profile quickly from the admin navigation.
- Is Laralum Profile actively maintained, and what are the alternatives?
- The Laralum ecosystem has seen little recent activity, so treat the module as a legacy dependency and review its commit history and issue tracker before adopting it. If maintenance is a concern, equivalent functionality is available through Laravel Breeze, Jetstream with Fortify, or a small custom controller and Blade view. For existing Laralum projects, the module remains the most consistent option because it matches the panel's conventions.
- How do I test the profile pages in my application?
- Use Laravel's HTTP testing helpers to authenticate a user with actingAs and then request the profile route, asserting that the page renders and that updates persist. Cover both the happy path and validation failures, plus a permission check for users who should be denied access. If you override the published views, add assertions on the fields you introduced so regressions surface early.
- What should I check before using Laralum Profile in production?
- Verify that the profile routes sit behind authentication and the correct Laralum permissions, and that only whitelisted attributes can be updated. If avatars or file uploads are enabled, confirm the storage disk, public symlink, file size limits, and image validation are configured properly. Finally, pin the package version in composer.json and test the upgrade path, since the Laralum ecosystem is not actively evolving.
Weaver
How can I help you explore Laravel packages today?