Module Hooks
Return to Introduction  Previous page  Next page

The Module Hooks feature can be a great tool for developers to help narrow down module conflicts. This area provides a list of the module hooks used or skipped by various modules.

To access the Module Hooks tool:

1.In the admin menu, click the embim1next to Stores.  
 
2.Click on Your Store's Links.  
 
3.Click on the Module Hooks link.  

embim57

The Module Hooks section tells us what OpenUI™ Sub-Module is used by a specific module, the module's name, and the hooks used.

In this example, we see only four OpenUI™ modules in the store, and two of them use various sub-modules and hooks in order for them to work in the store.

When conflicts occur, developers can narrow down the cause by seeing which sub-modules and hooks are being called by the third-party modules and either modify their modules accordingly, or come to the conclusion that two modules that serve virtually identical purposes (for example, two modules that completely overwrite an entire identical function or screen) will not work together.

In the example image above, since we see no conflicts, further steps to troubleshooting problems can be taken.

 


Send feedback on this documentation.
© 2003 - 2000 Darren Ehlers & OpenUI Developer Consortium