Anonymous | Login | Signup for a new account | 2021-02-27 03:45 GMT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Revisions: Issue #1681 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0001681: Make plugin hooks consistent | ||
Revision | 2011-08-11 11:05 by ivan | ||
Description | Use a consistent naming and placing scheme for plugin hooks to assist plugin developers and fix the mess of names that we have right now. <page name> - Add content to the page in the most appropriate place for custom content <page name>_form - Placed at the end of the form inside the form table but before the buttons <page name>_form_more - Placed at the end of the collapsible form section (more/advanced), where there is one, inside the form table but before the buttons <page name>_submitted - Placed after form data has been submitted (and validated) but before it is saved to the database or actioned upon <page name>_saved - Placed after form data has been saved but before confirmation is output or the page is redirected |
||
Revision | 2011-08-11 11:04 by ivan | ||
Description | Use a consistent naming and placing scheme for plugin hooks to assist plugin developers and fix the mess of names that we have right now. <page name> - Add content to the page in the most appropriate place for custom content <page name>_form - Placed at the end of the form inside the form table but before the buttons <page name>_form_more - Placed at the end of the collapsible form section (more/advanced), where there is one, inside the form table but before the buttons <page name>_submitted - Placed after form data has been submitted (and validated) but before it is saved to the database <page name>_saved - Placed after form data has been saved but before confirmation is output or the page is redirected |
||
Revision | 2011-08-11 11:03 by ivan | ||
Description | Use a consistent naming and placing scheme for plugin hooks to assist plugin developers and fix the mess of names that we have right now. <page name> - Add content to the page in the most appropriate place for custom content <page name>_form - Placed at the end of the form inside the form table but before the buttons <page name>_form_more - Placed at the end of the collapsible form section (more/advanced), where there is one, inside the form table but before the buttons <page name>_pre-save - Placed after form data has been submitted (and validated) but before it is saved to the database <page name>_save - Placed after form data has been saved but before confirmation is output or the page is redirected |
||
Revision | 2011-08-11 11:00 by ivan | ||
Description | Use a consistent naming and placing scheme for plugin hooks to assist plugin developers and fix the mess of names that we have right now. <page name> - Add content to the page in the most appropriate place for custom content <page name>_form - Placed at the end of the form inside the form table but before the buttons <page name>_form_more - Placed at the end of the collapsible form section (more/advanced) inside the form table but before the buttons <page name>_pre-save - Placed after form data has been submitted (and validated) but before it is saved to the database <page name>_save - Placed after form data has been saved but before confirmation is output or the page is redirected |
Copyright © 2000 - 2021 MantisBT Team |