-
-
Notifications
You must be signed in to change notification settings - Fork 668
Filament admin #1344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filament admin #1344
Conversation
Hey @theHocineSaad , not al all!! I'm really happy someone is making the push!! I've been not having time, it happens to us all, I didn't want to give up because I eventually will be more free, still this year, but in the end, what matters is that it gets DONE, so THANK YOOOOU! ❤️ |
Thanks a lot for this @theHocineSaad! you can rip the old admin panel out and move the filament one to /admin instead. Thanks also for kickstarting this @ijpatricio ! |
You're welcome .. Thanks for your understanding .. Glad to help |
You're welcome .. done => 6071d21 .. I just need to update some tests in |
My absolute pleasure, @driesvints I'm just sorry I couldn't find more time, but this is the magic of open source, @theHocineSaad came and joined!! |
@driesvints Just following up on this PR. Please let me know if there’s any feedback. |
Thanks @theHocineSaad. Been a bit under snowed with other work and PR's but planning on getting this one in soonish. |
Ok great |
Finally got this merged. I reverted some queueing you added to a few jobs, not sure if that was necessary? These actions should execute immediately so you see the effect on the subsequent page reload. Thanks a bunch you to @ijpatricio & @theHocineSaad! I really appreciate the help with this one 😄 |
Ah one thing I notice now in production: a link to get back to the main website in the nav somewhere would be great. |
You're welcome. Without the Queueable trait, you will get this error: ![]() And I used |
This PR introduces an admin panel built with Filament.
I'm aware of #1179, but I think the contributor doesn't have time to continue it, and they haven't made much progress. Also, Filament 3 (not 4) was used, so I believe this PR is justified. If this is a wrong move, I'm truly sorry, @ijpatricio.
@driesvints
Note: The old admin panel still exists at its original route /admin, while the new one is located at /admin-filament.