-
Notifications
You must be signed in to change notification settings - Fork 4
Custom modules
zzolo edited this page Dec 9, 2011
·
6 revisions
The following is a description of the custom module created for the site. Please indicate at least the following:
- Goal of the module
- The Drupal structures it hooks into
- Why the module is needed (what is lacking with Drupal)
- What may be the limitations of the module
All custom modules should be in the following location in the code base: sites/all/modules/custom
- Module short name:
cc_awe - Alterations to Address Field. (why??)
- (What is lacking with Drupal??)
- No limitations known.
- Module short name:
cc_flag_block - Puts Flag links that would normally be in the node links into a block.
- There is no built-in way to do this. This might be able to be accomplished with Display Suite.
- Limitations: The module hides the Flag links whether the block is available or not. This could cause some confusion when adding new flags or content types.
- Module short name:
cc_formatters - Provides various formatters (field display mechanisms), specifically:
- A "Image Content Reference" formatter for specifically showing Image node references through Shadowbox.
- A "City only" formatter for the Address field, that shows only the city.
- No built-in way to do this with Drupal. Some of this could have been done in theme as well.
- No known limitations.
- Module short name:
cc_helper - Provides lots of things. (?????)
- (why needed??)
- Limitations: This module probably has too many things going on. It is hard to determine what its purpose is and what it affects.
- Module short name:
cc_import_data - Allows for (??) to import data from a CSV file. (one time or for regular imports??)
- Note sure why this was written??. The Feeds module does this well.
- Limitations: It's hard to understand the full nature of this module. This seems like it may be a liability code wise, and should be removed if not needed.
- Module short name:
cc_interactions - Enhances the user experience for creating Interactions, from within the Application nodes.
- Written because of the limitations with usability of node references.
- Limitations:
- There is not a whole lof abstraction with the module.
- It is specific specific to individual fields.
- Overrides some JS functions in Drupal core and in ReferencesDialog (not a hack but could cause problems later)
- Module short name:
cc_node_title - Specifically creates a description for the title field of Organizations.
- Limitation of Drupal, seriously. There does not seem to be a module to do this.
- No known limitations.
- Module short name:
cc_places - Provides ??.
- Created because ??
- Limitations: Geocodes on every place page load. Hard coded field values.
- Module short name:
cc_ratings - Custom rating processing involving Fivestar module. (goal ??)
- Created because ??
- Limitations: Hard coded field values.
- Module short name:
cc_secure_site_lite - Provides a basic mechanism to close out the site to all non-logged-in users, except for the user pages and a preview page.
- Drupal does have node access modules, but they are usually very heavy.
- Limitations: Does not utilize Form API properly. Hard codes preview page and content.
- Module short name:
cc_string_overrides - Provides a very basic way of overriding for strings on the Javascript side.
- This is needed because the string overrides module did not have support for JS yet. Also, Drupal's Locale module is for languages translations, not simply changing some strings.
- Limitations: Might affect translations if the application gets translated. Should be replaced with StringOverrides module if more overrides are needed, and the JS patch gets submitted.