-
Notifications
You must be signed in to change notification settings - Fork 373
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
Custom Header Action Not Displaying in MyManageOrder in LunarPHP #2043
Comments
It looks like you are trying to extend the main class. This isn't the correct approach. ManagerOrder is a page, so you need to use its page extension. It's the same concept as this |
Thanks you
Thanks you, My update code: ManageOrderExtension
AppServiceProvider
Right now is working! Thank you for helping me! |
That's great news. I'm going to leave this open, as I expected us to have the page extension in the codebase and it wasn't. We should really have something like |
@glennjacobs I'm not sure why we need a |
Hello, I am facing an issue with adding a custom header action to the MyManageOrder page in LunarPHP. I have extended the ManageOrder class and overridden the getDefaultHeaderActions() method to include a new action using Filament's Action::make.
The custom action appears to be correctly added to the $actions array, and I confirmed that the MyManageOrder class is loaded by testing it with dd(). However, the action does not render on the page. I have already tried the following:
When I directly edit the vendor-provided ManageOrder class (within the LunarPHP vendor folder) and add the same Action::make, the button is rendered and works as expected. This makes me think that I may be missing a configuration or process when extending the ManageOrder class with my own.
Could you provide guidance on what might be causing the custom action to not render in my extended class? My task is simply to add a button to the header that performs a specific action. Any advice or suggestions would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: