Modifying/expanding core module buttons?
Created 1 year ago by failcookie

I am looking at modifying the User Module to add a new button option for a custom module I am created. Example - I am creating a payments module for the admin users to view payments that were submitted by a user. What is the best approach for handling this situation? In particular, ensuring that the buttons are only changed on the User Module table listing. I don't want to affect the buttons that are being used in a Relationship field type query table (as an example).

piterden  —  1 year ago

First bind existed to your, then your should extend existed.

ryanthompson  —  1 year ago

Yep bind the table builder or button handler if there is one. Keep in mind after binding you’ll need to manually define handlers that were originally automatically detected. Cause by binding you effectively change the location of the class and it won’t auto detect in the original location.

failcookie  —  1 year ago

I'll just need to make sure I check the core module for updates when new stuff happens? Sounds easy enough to me. I just wanted to make sure there wasn't a better way first.

ryanthompson  —  1 year ago

@failcookie ya just in case you miss any new features but it should be generally safe.