dr:classified
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
dr:classified [2010/09/17 20:24] – created fgm | dr:classified [2016/10/22 17:54] – Battle plan for Multiple node types fgm | ||
---|---|---|---|
Line 5: | Line 5: | ||
Download or clone from http:// | Download or clone from http:// | ||
+ | ===== Battle plan for multiple node types ===== | ||
+ | < | ||
+ | <div class=" | ||
+ | < | ||
+ | <p>As per #195494, the goal is to support multiple node types.</ | ||
+ | <ul> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | fields by a proper field</ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | automatically be identified by the presence of an instance of the | ||
+ | expiration field</ | ||
+ | </ul> | ||
+ | |||
+ | < | ||
+ | < | ||
+ | and < | ||
+ | <ul> | ||
+ | < | ||
+ | < | ||
+ | <ul> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | < | ||
+ | fields.</ | ||
+ | < | ||
+ | the new custom view mode introduced in 7.3. With multiple node types, this | ||
+ | is no longer doable so we replace these lists by taxonomy-filtered views.</ | ||
+ | |||
+ | < | ||
+ | |||
+ | <ul> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | sub-category links, and breadcrumbs generation. This is likely to | ||
+ | involve attached views and/or new specific handlers.</ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ul> | ||
+ | |||
+ | < | ||
+ | <ul> | ||
+ | < | ||
+ | < | ||
+ | </ul> | ||
+ | |||
+ | < | ||
+ | < | ||
+ | expires generation and update. This needs to be adapted for the additional | ||
+ | complexity of a field over an extra field. Existing node form hooks and | ||
+ | handlers must be replaced by field hooks since we no longer know which forms | ||
+ | to intercept.</ | ||
+ | |||
+ | < | ||
+ | <p>A number of users have expressed frustration at the lack of i18n support | ||
+ | in the module. Switching the extra fields to a field and the custom lists | ||
+ | to Views will help with this. New code should be i18n-compatible, | ||
+ | later changes can bring full i18n compliance</ | ||
+ | |||
+ | < | ||
+ | < | ||
+ | increase towards 100% C0.</ | ||
+ | |||
+ | <ul> | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | < | ||
+ | The move from an extra field to a normal field is in the right direction. Other significant | ||
+ | changes regard code placement outside the module file and the use of | ||
+ | autoloaded namespaced classes, one per file.</ | ||
+ | |||
+ | <ul> | ||
+ | < | ||
+ | methods</ | ||
+ | < | ||
+ | < | ||
+ | usable at the admin level by exposing it as a core action, typically for | ||
+ | the user or node entities</ | ||
+ | < | ||
+ | to apply PSR-0, or declare classes the D7 way, manually in the info file.</ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | | ||
===== OK Paths ===== | ===== OK Paths ===== | ||
dr/classified.txt · Last modified: 2020/11/23 17:23 by 127.0.0.1