About the manifest.xml:
ASm I correct to assume I could include the complete installation (including tables that are outside of the 'normal' entity module scope) in here? And could I create an 'after install event/handler' that could point to a script file that automatically installs my workflow files?
Also:
I think the variables like '$MODULE$' are automatically available? Or should I do something to create them? And could I skip writing an install script using this?
Do you have an example of this on github?
ASm I correct to assume I could include the complete installation (including tables that are outside of the 'normal' entity module scope) in here? And could I create an 'after install event/handler' that could point to a script file that automatically installs my workflow files?
Also:
PHP Code:
<customlink>
<linktype>DETAILVIEWWIDGET</linktype>
<linklabel>Stopwatch</linklabel>
<linkurl><![CDATA[module=Timecontrol&action=TimecontrolAjax&file=StopWatch&return_module=$MODULE$&record=$RECORD$]]></linkurl>
<linkicon><![CDATA[]]></linkicon>
<sequence>0</sequence>
<handler_path><![CDATA[]]></handler_path>
<handler_class><![CDATA[]]></handler_class>
<handler><![CDATA[]]></handler>
</customlink>
I think the variables like '$MODULE$' are automatically available? Or should I do something to create them? And could I skip writing an install script using this?
Quote: I understand you are talking about the vtlib_handler() method. These are a set of events that are launched when installation related things happen. For example, when you install a module the module.postinstall event is launched so you can do some additional administration tasks. The most normal ones is to relate your new module with other modules in the system.
Do you have an example of this on github?