This module provides field formatters which display timer or countdown. Formatters can be used for Date fields or timer fields provided by this module. The start/target date on the timer field can be any date or an entity property which represent a date (for example, created date of a node). Module provides 3 field formatters: simple text and 2 formatters based on jQuery plugins County and jQuery Countdown.
D8
This module provides field formatters for core module Datetime which display timer or countdown. 3 field formatters are provided: simple text and 2 formatters based on jQuery plugins County and jQuery Countdown.
If you are looking for a configurable countdown/timer, this module is for you. It allows to configure backgrounds, effects, formats, language of timer, etc.
23 JUL 2013
This module now contains an submodule: Previous Next Field that provides a highly configurable Previous/Next field type. It is working, but needs quite a bit of work still. Right now the biggest roadblock is that I'm not sure if fields require some sort of DB storage or not (currently wading through the API docs). I'm storing "1" for each instance of this field currently, but that's not necessary; each instance of the field is identical. Perhaps it would be useful to store the actual previous next value in the field, but that kind of defeats the purpose of the original parent module's caching mechanism. And I still thing the original module is useful as a standalone.
Previous / Next Node ID
This module provides a function that retrives the previous and/or next Node ID
in a sequence as defined in a list of options passed as a param to the function
sorted by Node ID, Node Title, Published or Changed date. The queries used to
generate this sequence can be slow so this module also creates a table for
storage and quick retrieval of the values.
Sequences can be restricted by node status, node type and taxonomy terms.
USAGE
The following function is available after enabling the module:
In some situations you want to mark an entity field to indicate it should be completed but not enforce its completion at that time. This module extends the choice between Required and Not required to "desirable" completion.
This module overcomes the problems with the (otherwise excellent) Content Complete module which cannot cope with field collections or fields that link to other entities.
When you might want it
The module has two use cases:
Where you might (say) have a score of completeness on a user profile. You don't want to enforce filling in fields with a "required" but just encourage it by having a %age completion. (There's a nifty block that shows the level of completion and what could be filled in next.)
The other use case - and the reason I needed it - was having an absolutely huge application form that could not be filled in in one sitting and which also had all sorts of field collections and links to other content which also had to be filled in correctly.
Everything has to be filled in, but it might take weeks (in this case). So the user needs to be able to save it between times - but the ability to submit the final version does not appear until everything is filled in. (There's a Rules rule - which is in the documentation - to allow actions to take place when the form is finally completed.)