First and intitial release. Module has been deployed on two sites before the release, so more testing is required before we can call it really production ready. Use at own risk.
Added an option for specifying which event/date the timeline views should initially be centered on after loading.
Fixed widget creation so that the 'Loading...' bubble is displayed.
#94031: Allow using custom CCK fields as the start/end date, title and description of timeline events (kudos to John Stalcup).
#79472: Fix asynchronous timeline loading problems occuring in IE6 (kudos to John Stalcup and Erwin Lion).
#91081: Corrected the timeline popup node links (kudos to Eric Charikane).
#90660: Prevented other modules (e.g. devel.module) from intefering with timeline JSON or XML feed output (kudos to Steve Yelvington).
#90272: Extended the module's installation and usage instructions, and reorganized the code for better extensibility.
#90272: Implemented an installation hook which verifies that the required Views module is installed and enabled, and outputs a warning in case it is not.
#90272: Implemented JSON output and added a setting for specifying whether to use JSON or XML for loading the timeline data feed.
#90272: Simplified the XML output code by making use Drupal's built-in function format_xml_elements().
#90272: Changed dates/times in data feed to use the ISO-8601 format, and added explicit date format specifier to data feeds.
#90272: Added a setting for specifying the base URL to load the timeline JavaScript widget from.
#90272: Added a setting and cache control implementation for specifying the client-side cache lifetime for timeline data feeds.
#90272: Changed timeline data feed loading to use a relative, instead of absolute, URL to counteract problems when accessing a site via HTTP/HTTPS both.
#90272: Added an explicit UTF-8 character set specifier to the HTTP Content-Type header of the data feeds.
#90272: Implemented some initial Simpletest unit tests for verifying the well-formedness of the data feeds provided by the timeline module.
#90272: Implemented a best-effort workaround for the widget's timezone display bugs, claiming dates are GMT while they're in fact explicitly adjusted to the current user's timezone.
#90272: Added a wrapper DIV element around timeline DIV for easier control over theming, and added a visible border around the timeline widget for stylistic effect.
#90272: Changed the default timeline CSS class name and width, and set the timeline XHTML element ID to the name of the current timeline view in order to facilitate custom theming.
#90272: Separated timeline creation JavaScript code out of the module and into a file called timeline.js; also added an initial timeline.css stylesheet file.
#90272: Successfully tested vertical timeline views (with newest version of the timeline widget).
Enhancements:
- #311343: Warn about bad 'http://' site url.
- #299259: Add option to hide "Subscribe to this page", update .pot and de.po files.
Bugs fixed:
- #315304: Avoid using empty anchor tag.
- #308801: Fix enable-subscriptions-block-warning link.
Some new features and lots of bug fixes.
+ Keep attached files when creating translations.
+ New i18nprofile module to translate profile field names.
+ Some basic workflow support for translations.
+ Content administration tab for translations
+ Allow translation of products.
The relatedlinks module enables nodes to display related URLs to the user via blocks. Related links can be defined in 3 ways:
* Parsed links: links that are retrieved from the body of a node.
* Manual links: links that are added manually.
* Discovered links: links that are discovered by the module using various criteria, including the category terms of a node and suggestions provided by the search module (when enabled).
Related links are defined in 3 ways:
1) For certain content types, HTML links are automatically discovered and included.
2) The author may manually add HTML links that will appear at the top of the 'Related links' block.
3) An optional related terms block can be enabled to display links to nodes that share common terms with the displayed node.
updated the required modules list, description, and added a tutorial to the README.txt
added an option to require delete confirmation
added support for keeping fieldsets open between page loads
fixed a child type calculation bug
added views cache clearing on subform creation (without this, views driven selection lists won't work)
In this release, subform gains relationship cardinality control, improved selection lists (now with functioning filters and paging), a cleaner look, and Views 1.2 compatibility.
Right now i'm feeling like the short term roadmap includes granular relation creation restrictions based on user role, and allowing nested subforms.
This release fixes a security vulnerability, all users of cvs.module (4.7.x-1.0 or 4.7.0 from before the new release system) are urged to upgrade. For more details, see DRUPAL-SA-2006-028.
This release includes a new database update: cvs_update_5() which removes a stale entry from the {variable} table. After you upgrade, you should run update.php for your site.
Other changes since cvslog 4.7.x-2.0:
#94000 by dww: adding $Name$ tags for automated version identification.
#97031 by Zen: CVS application form fixes + move all strings to the settings page.
#97128 by dww: don't make the body field required when project administrators edit project releases.
This release fixes a security vulnerability, all users of cvs.module (4.7.x-1.0 or 4.7.0 from before the new release system) are urged to upgrade. For more details, see DRUPAL-SA-2006-028.
This release includes a new database update: cvs_update_5() which removes a stale entry from the {variable} table. After you upgrade, you should run update.php for your site.
Updated version of MicroID module. This version generates the MicroID correctly based on the posters email and the URL of the post that has been created. JS fixed to only add correct microID to correct node.
The bloginfo module adds a blog title and description to your blogs. It is a simple module that adds 2 additional fields to the users account screen, for those who have permission, to have a blog title and blog description. These are then put into a block that can be placed like any other block. The title is the block title and the description is the block content.
The idea is to have a blog title and description like one via blogger.com.
The block will only display on a users blog list or blog post who have filled in the settings.