Overview
Customizing Bagisto views is common in extensions. Earlier view files were published, but now Laravel view namespaces are preferred for overrides.
Previous Method: Publishing Views
Earlier, view files were copied into the resources directory and directly modified to customize the UI by overriding package views locally.
|
1 2 3 4 |
$this->publishes([ __DIR__.'/../Resources/views/shop/default/checkout/cart/index.blade.php' => resource_path('views/vendor/shop/checkout/cart/index.blade.php'), ]); |
After publishing, developers edited the copied files to customize the storefront or admin panel layout, behavior, and appearance as needed, without modifying the original package code.
Drawbacks
- Extra setup step to publish files.
- Difficult to track overridden files.
- Updates to the original package may not reflect in published copies.
- Maintenance becomes harder as the project grows.
Recommended Method: Namespace Override
Instead of copying files, register your custom view path using prependNamespace().
|
1 |
$this->app['view']->prependNamespace( 'shop', __DIR__.'/../Resources/views/shop/default' ); |
|
1 |
$this->app['view']->prependNamespace( 'admin', __DIR__.'/../Resources/views/admin/default' ); |
Example
Suppose Bagisto loads the following view:
|
1 |
view('shop::checkout.cart.index'); |
Laravel will first check:
|
1 |
packages/Webkul/YourPackage/src/Resources/views/shop/default/checkout/cart/index.blade.php |
If the file exists, it will be used instead of the original Bagisto view.
Directory Structure
|
1 2 3 4 5 6 7 8 9 10 11 |
Resources └── views ├── admin │ └── default │ └── sales └── shop └── default └── checkout └── cart └── index.blade.php |
Why Use This Approach?
- o view publishing is required, avoiding duplication of package files in the application.
- The package remains self-contained, keeping all original views inside the module.
- Bagisto upgrades become easier with no risk of losing or merging published view changes.
- Cleaner code organization by separating core package logic from custom overrides.
- Faster development and easier long-term maintenance using
prependNamespace()instead of manual file copying.
Final Thoughts
For modern Bagisto development, prependNamespace() is the recommended way to override core views. It reduces maintenance, avoids file publishing, and provides a clean and efficient customization workflow.
