Comments (5)
hi @vijayrana99 are you using any other plugins/packages that might interfere with these routes?
Can you also share your config?
from filament-breezy.
@jeffgreco13
This is my packages list from composer.json file.
"require": {
"php": "^8.0.2",
"3x1io/filament-browser": "^1.0",
"awcodes/filament-quick-create": "^1.0",
"bezhansalleh/filament-shield": "^1.1",
"filament/filament": "^2.0",
"filament/spatie-laravel-media-library-plugin": "^2.0",
"guzzlehttp/guzzle": "^7.2",
"jeffgreco13/filament-breezy": "^1.3",
"laravel/framework": "9.19",
"laravel/sanctum": "^2.14.1",
"laravel/tinker": "^2.7",
"martin-ro/filament-charcount-field": "^0.1.5",
"phpsa/filament-password-reveal": "^1.1",
"ralphjsmit/laravel-filament-seo": "^1.0",
"ralphjsmit/laravel-seo": "^1.0",
"ryangjchandler/filament-profile": "^0.2.0",
"saade/filament-fullcalendar": "^1.3",
"sebastiaankloos/filament-code-editor": "^1.0",
"shuvroroy/filament-spatie-laravel-backup": "^1.2",
"shuvroroy/filament-spatie-laravel-health": "^1.4",
"spatie/laravel-activitylog": "^4.5",
"spatie/laravel-health": "^1.11",
"spatie/laravel-permission": "^5.5",
"z3d0x/filament-logger": "^0.2.3"
},
And below is my config file for filamentphp.
<?php
use Filament\Http\Middleware\Authenticate;
use Filament\Http\Middleware\DispatchServingFilamentEvent;
use Filament\Http\Middleware\MirrorConfigToSubpackages;
use Filament\Pages;
use Filament\Widgets;
use Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse;
use Illuminate\Cookie\Middleware\EncryptCookies;
use Illuminate\Foundation\Http\Middleware\VerifyCsrfToken;
use Illuminate\Routing\Middleware\SubstituteBindings;
use Illuminate\Session\Middleware\AuthenticateSession;
use Illuminate\Session\Middleware\StartSession;
use Illuminate\View\Middleware\ShareErrorsFromSession;
return [
/*
|--------------------------------------------------------------------------
| Filament Path
|--------------------------------------------------------------------------
|
| The default is `admin` but you can change it to whatever works best and
| doesn't conflict with the routing in your application.
|
*/
'path' => env('FILAMENT_PATH', 'admin'),
/*
|--------------------------------------------------------------------------
| Filament Core Path
|--------------------------------------------------------------------------
|
| This is the path which Filament will use to load its core routes and assets.
| You may change it if it conflicts with your other routes.
|
*/
'core_path' => env('FILAMENT_CORE_PATH', 'filament'),
/*
|--------------------------------------------------------------------------
| Filament Domain
|--------------------------------------------------------------------------
|
| You may change the domain where Filament should be active. If the domain
| is empty, all domains will be valid.
|
*/
'domain' => env('FILAMENT_DOMAIN'),
/*
|--------------------------------------------------------------------------
| Homepage URL
|--------------------------------------------------------------------------
|
| This is the URL that Filament will redirect the user to when they click
| on the sidebar's header.
|
*/
'home_url' => '/',
/*
|--------------------------------------------------------------------------
| Brand Name
|--------------------------------------------------------------------------
|
| This will be displayed on the login page and in the sidebar's header.
|
*/
'brand' => env('APP_NAME'),
/*
|--------------------------------------------------------------------------
| Auth
|--------------------------------------------------------------------------
|
| This is the configuration that Filament will use to handle authentication
| into the admin panel.
|
*/
'auth' => [
'guard' => env('FILAMENT_AUTH_GUARD', 'web'),
'pages' => [
// 'login' => \Filament\Http\Livewire\Auth\Login::class,
'login' => \JeffGreco13\FilamentBreezy\Http\Livewire\Auth\Login::class,
],
],
/*
|--------------------------------------------------------------------------
| Pages
|--------------------------------------------------------------------------
|
| This is the namespace and directory that Filament will automatically
| register pages from. You may also register pages here.
|
*/
'pages' => [
'namespace' => 'App\\Filament\\Pages',
'path' => app_path('Filament/Pages'),
'register' => [
Pages\Dashboard::class,
],
],
/*
|--------------------------------------------------------------------------
| Resources
|--------------------------------------------------------------------------
|
| This is the namespace and directory that Filament will automatically
| register resources from. You may also register resources here.
|
*/
'resources' => [
'namespace' => 'App\\Filament\\Resources',
'path' => app_path('Filament/Resources'),
'register' => [],
],
/*
|--------------------------------------------------------------------------
| Widgets
|--------------------------------------------------------------------------
|
| This is the namespace and directory that Filament will automatically
| register dashboard widgets from. You may also register widgets here.
|
*/
'widgets' => [
'namespace' => 'App\\Filament\\Widgets',
'path' => app_path('Filament/Widgets'),
'register' => [
// Widgets\AccountWidget::class,
// Widgets\FilamentInfoWidget::class,
],
],
/*
|--------------------------------------------------------------------------
| Livewire
|--------------------------------------------------------------------------
|
| This is the namespace and directory that Filament will automatically
| register Livewire components inside.
|
*/
'livewire' => [
'namespace' => 'App\\Filament',
'path' => app_path('Filament'),
],
/*
|--------------------------------------------------------------------------
| Dark mode
|--------------------------------------------------------------------------
|
| By enabling this feature, your users are able to select between a light
| and dark appearance for the admin panel, or let their system decide.
|
*/
'dark_mode' => true,
/*
|--------------------------------------------------------------------------
| Layout
|--------------------------------------------------------------------------
|
| This is the configuration for the general layout of the admin panel.
|
| You may configure the max content width from `xl` to `7xl`, or `full`
| for no max width.
|
*/
'layout' => [
'forms' => [
'actions' => [
'alignment' => 'left',
],
'have_inline_labels' => false,
],
'footer' => [
'should_show_logo' => false,
],
'max_content_width' => null,
'notifications' => [
'vertical_alignment' => 'top',
'alignment' => 'center',
],
'sidebar' => [
'is_collapsible_on_desktop' => false,
'groups' => [
'are_collapsible' => true,
],
'width' => null,
],
],
/*
|--------------------------------------------------------------------------
| Favicon
|--------------------------------------------------------------------------
|
| This is the path to the favicon used for pages in the admin panel.
|
*/
'favicon' => null,
/*
|--------------------------------------------------------------------------
| Default Avatar Provider
|--------------------------------------------------------------------------
|
| This is the service that will be used to retrieve default avatars if one
| has not been uploaded.
|
*/
'default_avatar_provider' => \Filament\AvatarProviders\UiAvatarsProvider::class,
/*
|--------------------------------------------------------------------------
| Default Filesystem Disk
|--------------------------------------------------------------------------
|
| This is the storage disk Filament will use to put media. You may use any
| of the disks defined in the `config/filesystems.php`.
|
*/
'default_filesystem_disk' => env('FILAMENT_FILESYSTEM_DRIVER', 'public'),
/*
|--------------------------------------------------------------------------
| Google Fonts
|--------------------------------------------------------------------------
|
| This is the URL for Google Fonts that should be loaded. You may use any
| font, or set to `null` to prevent any Google Fonts from loading.
|
| When using a custom font, you should also set the font family in your
| custom theme's `tailwind.config.js` file.
|
*/
'google_fonts' => 'https://fonts.googleapis.com/css2?family=DM+Sans:ital,wght@0,400;0,500;0,700;1,400;1,500;1,700&display=swap',
/*
|--------------------------------------------------------------------------
| Middleware
|--------------------------------------------------------------------------
|
| You may customise the middleware stack that Filament uses to handle
| requests.
|
*/
'middleware' => [
'auth' => [
Authenticate::class,
],
'base' => [
EncryptCookies::class,
AddQueuedCookiesToResponse::class,
StartSession::class,
AuthenticateSession::class,
ShareErrorsFromSession::class,
VerifyCsrfToken::class,
SubstituteBindings::class,
DispatchServingFilamentEvent::class,
MirrorConfigToSubpackages::class,
],
],
];
from filament-breezy.
I am a bit confused as to why the NGINX 404 page is appearing and not the Laravel 404 route. It's as if the router is not working properly in your app.
I would be curious if the same error occurs for you on a fresh install of Filament + Breezy. Also, perhaps one of the SEO plugins is conflicting if they do any URL rewriting.
from filament-breezy.
I've the same issue. Working perfectly on local when deployed same issue
from filament-breezy.
I think this is a livewire bug
from filament-breezy.
Related Issues (20)
- Overriding PersonalInfo doesn't work HOT 1
- Missing CI / Github Actions HOT 1
- Call to a member function getPlugin() on null HOT 3
- Missing string in it lang HOT 3
- Unable to call component method. Public method [submit] not found on component HOT 3
- Config not serializable HOT 4
- Breezy not show in panel at laravel filament fresh install
- 2FA: Filament's Notification and Profile menus are visible before 2FA is completed HOT 2
- Using a custom TwoFactorPage causes a Livewire error
- Breezy tests
- allow modification of sanctum permissions in tenantMiddleware()
- How to reveal the password while typing for update? HOT 1
- Why this code not work when change Force status?
- How to use this code in Two Factor Authentication
- rember 2FA when remember logging in HOT 4
- How can I change the navigation page icon? HOT 7
- Impersonate 2FA Problem
- How to add "revealable" option to password field?
- Bug : User Avatar Doesn't Show in edit profile page HOT 1
- Impersonation, SSO / bypass for specific users
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from filament-breezy.