This module allows users to record a video with their webcam and post it to a Drupal website.
Videos are recorded using the JW player and must be pushed to a Flash video server.
Videos can be added in comments or nodes, using a CCK widget based on filefield.
This module is still in development.
Nodes in block makes it possible to add nodes into a block. A number of configurable blocks are generated which you can assign to a region. Visibility settings of this block are automatically set to 'Show on only the listed pages'. On the node content form, you define the weight and visibility per node thus making it easier for content administration as all your content is now in the same place. With this module, you don't have to explain your customers how blocks work but is still able to decide on which pages content must be rendered.
This is a simple module that adds a "node-content" theme hook to Drupal for theming the $node->content array. For example, with this module enabled, you can create a "node-content--page.tpl.php" file in your theme's folder, giving you templating control of the "Page" content type. This can be used for any content type, but the use-case I expect it to be most useful for is in having greater theming control of content types that use CCK fields.
The editing form of a node is themed using theme('node_form'), which is implemented by the theme_node_form() function in Drupal core's node module and can be overridden by adding a <theme_name>_node_form() function in the theme's template.php file. However, this is less convenient and less powerful than taking advantage of Drupal's templating system. Why not be able to override by placing a node-form.tpl.php file in the theme's folder and allow modules to use preprocess functions for customization? This module allows exactly that.
This module provides two theme functions which, in turn, provide an easy way to put multiple input form elements on the same line. No longer do you have to create large, unwieldy templates to make your input forms prettier and more compact.
The module can generate either an HTML table or
It is important to note, however, that this module does nothing on its own. You must refer to one of the included themes from PHP code in order for there to be any effect.
On 404 Not Found error pages, Drupal will skip rendering of several pieces of your website for performance reasons. Some of these include:
* Unless you have configured a "Default 404 (not found) page" on admin/settings/error-reporting.
But many websites find those items invaluable. Especially on 404 pages, when they want to show lost users how to get to real pages.
So this module simply revives those features on 404 pages. Simply install and enable the module. No configuration needed.
This module allows certain clients from using different themes, based on a defined string in the User Agent. Based on that string, a theme will be assigned to that particular kiosk. The theme can be shared for a group of kiosks, or restricted for an individual kiosk.
Drupal's normal mode page caching is supported.
The kiosk module has similar high level goals, but different design and implementation. Here are the important differences:
Simple per-node content access module that performs a little differently than the majority of access modules. This module replaces the content teaser/body with "This post has been restricted to certain users" to show users that they are missing content if they are not registered or are not a certain user role.
This module integrates with the API provided by theJQuery Menu module (version 1.8 and higher) to provide click and expand book menus with the ability to customize each block individually.
Not only can you set blocks to hold particular sets of books, but you can also set each block to enable new books on a per block level based on taxonomy terms which are assigned.
This an extension to the Domain Access module which is used to create many domains from a single installation.
For what I see as a problem is that the domain module uses the node access api's to determine which nodes are displayed on which site. This will work if you only use Domain access, and no other access module like simple access, tac, or Organic groups.
