View Issue Detail

ID	Project	Category	Submitted / Last Updated
01373	UserSpice	Feature Request	2021-10-19 10:58:36 / 2021-10-19 22:29:30
Reported	James Erikson	Assigned To	Unassigned
Priority	none	Reported	5.3.5
Status	feature-request	Resolution Version and Commit
Summary	Allow core page hooks/plugins to be called from another custom file
Description	I know userspice has default pages for account, login, etc - but an idea I had to make it more adaptable would be to allow the hooks to be called from a different directory and still work. For instance, I had my own account page made a long time ago that gives a lot more information and usability than userspice's template does, but I can't use it because I won't get things like the membership or other plugins to work on it. Same with the login page, I can't get the remember me or Google login to work... This is mainly an issue with hooks/plugins I've noticed. Just an idea for expansion, not complaining or anything. This would allow the userspice pages to be left untouch and can be updated over time, while allowing more advanced customization for the ones who have or want custom made pages for login/etc

November 2021

But this may require some other logic like where to direct the user so I understand if not. Also made a typo, meant to say "untouched"
November 2021

Hooks are included based on a page name and section that you define if I remember correctly, are you sure you can't use them elsewhere? Despite, the point of plugins/hooks are meant to link with core-UserSpice files, not custom ones. Plugins (for example the Coupons plugin) that add their own functionality that don't depend on core, should make their own files, and not expect the user creates a set of hooks on a page. Certainly an option in the future to reduce the code footprint, but with the way it was designed at this time, it doesn't fit the current scope.