drupal/modules/trigger/trigger.info

; $Id$
name = Trigger
description = Enables actions to be fired on certain system events, such as when new content is created.
package = Core - optional
version = VERSION
core = 7.x
files[] = trigger.module
files[] = trigger.admin.inc
files[] = trigger.install
#172773 by numerous contributors: Make the actions interface usable by mere mortals (including rename of actions.module to trigger, but keeping the actions themselfs). Complete previous history of actions module: - #148410 by jvandyk: added rewrite of the actions module! - #155986 by Uwe: fixed typos. - #155828 by Eaton, pwolanin and jvandyk: let actions live even if actions.module is not turned on 2007-09-11 14:50:05 +00:00			`; $Id$`
			`name = Trigger`
			`description = Enables actions to be fired on certain system events, such as when new content is created.`
			`package = Core - optional`
			`version = VERSION`
- Patch #221384 by webernet: update core compatibility to Drupal 7. 2008-02-18 19:19:49 +00:00			`core = 7.x`
- Patch #221964 by chx, dopry, webernet, moshe, webchick, justinrandall, flobruit et al. Can you say 'registry'? Drupal now maintains an internal registry of all functions or classes in the system, allowing it to lazy-load code files as needed (reducing the amount of code that must be parsed on each request). The list of included files is cached per menu callback for subsequent loading by the menu router. This way, a given page request will have all the code it needs but little else, minimizing time spent parsing unneeded code. 2008-05-06 12:18:54 +00:00			`files[] = trigger.module`
			`files[] = trigger.admin.inc`
#318892 by justinrandell and chx: Add .install files to the list of files added to .info files. 2008-10-09 22:51:41 +00:00			`files[] = trigger.install`