Task #44

Abilty for modules to edit other modules

Added by Robert Clipsham over 3 years ago. Updated about 1 year ago.

Status:Closed Start date:2008-10-22
Priority:Critical Due date:
Assignee:Robert Clipsham % Done:

100%
Category:Zula::Internal
Target version:2.3.0
PHP Version:

Description

Allow for modules to add content to the controllers of other modules (notably the config controllers). This will allow modules to take advantage of tags and aliases at the same time content is added. This could be achieved using a combination of hooks and tags in view files eg.

{ADDITIONAL_CONTENT}

In the view file would have a table assigned to it using hooks to get each row.

Related issues

related to TangoCMS - Task #123: Add {ADDITIONAL_CONTENT} to modules other than page. Closed 2009-03-23
precedes TangoCMS - Feature #42: Content Tagging Closed 2008-10-23 2008-10-23

History

#1
Updated by Robert Clipsham about 3 years ago

  • % Done changed from 0 to 40

Can now add to the top/bottom of modules using hook module_output_(top|bottom). r1998

#2
Updated by Alex Cartwright about 3 years ago

  • Tracker changed from Feature to Task

#3
Updated by Robert Clipsham almost 3 years ago

  • % Done changed from 40 to 70

Most of {ADDITIONAL_CONTENT} is implemented @ localhost now.

#4
Updated by Alex Cartwright almost 3 years ago

  • Priority changed from High to Critical

#5
Updated by Robert Clipsham almost 3 years ago

  • % Done changed from 70 to 100

Now implemented in r2219. Seems to work nicely for the page module, haven't added the functionality to other modules yet.

#6
Updated by Lucas Wojciechowski almost 3 years ago

What is the advantage of this system over having a way for modules to embed another module within their own controller/view?

#7
Updated by Alex Cartwright almost 3 years ago

A module ideally shouldn't be aware of other modules. This feature is more about letting another module add form elements into an existing modules form, to extend the ability of a module. For example, this feature will let you add an alias while making a page (a feature already present, but done quite hackly as the page module explicitly checks for the alias module), add tags when making an article etc. From what I can recall (I've not really work on this feature much myself), a controllers form can say what sort of content type, and another module can respond to that.

This feature coupled with some new hooks, will let you fully extend the functionality of a module - since other modules will now be able to add content to the top and bottom of a controllers output (which will let us easily have comments and a 'Share This' type of thing implemented much nicer).

#8
Updated by Alex Cartwright almost 3 years ago

  • % Done changed from 100 to 80

#9
Updated by Alex Cartwright almost 3 years ago

  • % Done changed from 80 to 90

Revisions r2257 and r2259 implemented some cleanups/changes to this feature. Just need to change {ADDITIONAL_CONTENT} to something such as {AMC.TABLE} (and others) to allow for greater flexibility, and also figure out a way to nicely implement restoring the posted value if validation failed.

#10
Updated by Alex Cartwright over 2 years ago

  • Category set to Zula::Internal
  • Status changed from Approved to Confirmed
  • % Done changed from 90 to 100

r2428 has changed the hook name to 'amc_form_table' and the content tag to {AMC.TABLE}

#11
Updated by Alex Cartwright over 2 years ago

  • Status changed from Confirmed to Closed

Also available in: Atom PDF