<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" version="2.0" xml:base="http://drupal.org">
<channel>
 <title>drupal.org - Modules</title>
 <link>http://drupal.org/taxonomy/term/14/0</link>
 <description>Contributed (contrib) modules are plugins for Drupal that extend, build or enhance Drupal core functionality.  Use matching versions (modules released for Drupal 5.x will not work for Drupal 6.x).

Contributed modules are not part of Drupal core releases and may or may not have optimized code/functionality.  If a module solves your needs please consider joining forces and helping the maintainer.</description>
 <language>en</language>
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.0/</creativeCommons:license><image><link>http://www.feedburner.com</link><url>http://drupal.org/themes/bluebeach/logo.png</url><title>This Feed Powered by FeedBurner.com</title></image><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/drupalmodules" type="application/rss+xml" /><item>
 <title>Contact Form On Node</title>
 <link>http://drupal.org/project/contact_form_on_node</link>
 <description>&lt;p&gt;This simple module add a contact form right under the node. You can choose:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;to add a contact form on teaser,&lt;/li&gt;
&lt;li&gt;to add a contact form on full view,&lt;/li&gt;
&lt;li&gt;to add a contact link on teaser,&lt;/li&gt;
&lt;li&gt;to add a contact link on full view,&lt;/li&gt;
&lt;li&gt;which content types these settings will apply to.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This check if user has rights to access contact forms.&lt;br /&gt;
It needs &lt;a href="" rel="nofollow"&gt;Contact&lt;/a&gt; module.&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/58">Content display</category>
 <category domain="http://drupal.org/taxonomy/term/66">Mail</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Mon, 20 Jul 2009 19:51:40 +0000</pubDate>
 <dc:creator>cfab</dc:creator>
 <guid isPermaLink="false">525416 at http://drupal.org</guid>
</item>
<item>
 <title>Publication Date</title>
 <link>http://drupal.org/project/publication_date</link>
 <description>&lt;h2&gt;Description&lt;/h2&gt;
&lt;p&gt;This module adds to each node a field containing the date when it has been&lt;br /&gt;
published.&lt;/p&gt;
&lt;p&gt;Without this, the only dates available are the creation date and the&lt;br /&gt;
update date.&lt;/p&gt;
&lt;p&gt;This new field can be used for example in any templates or in any views.&lt;/p&gt;
&lt;p&gt;This module integrates well also with &lt;a href='/project/scheduler' rel="nofollow"&gt;Scheduler&lt;/a&gt; for example.&lt;/p&gt;
&lt;p&gt;This module is written by &lt;a href='http://www.clever-age.org' rel="nofollow"&gt;Clever Age&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/publication_date" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/57">Content</category>
 <category domain="http://drupal.org/taxonomy/term/75">Utility</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Mon, 20 Jul 2009 19:20:45 +0000</pubDate>
 <dc:creator>Clever Age</dc:creator>
 <guid isPermaLink="false">525402 at http://drupal.org</guid>
</item>
<item>
 <title>Jango Mail</title>
 <link>http://drupal.org/project/jangomail</link>
 <description>&lt;p&gt;This module provides a way to opt for the jangomail configuration for your drupal site. &lt;/p&gt;
&lt;p&gt;If enabled, all mails will be sent using jangomail from your drupal site. It also provides a way to opt out at any moment of instance. When opted out, drupal's traditional mail system will work.&lt;/p&gt;
&lt;p&gt;You require your jangomail account's username and password for the configuration.&lt;/p&gt;
&lt;p&gt;To install, enable the module in /admin/build/modules, and visit admin/settings/jangomail .&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/66">Mail</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Mon, 20 Jul 2009 17:18:54 +0000</pubDate>
 <dc:creator>Glick Interactive</dc:creator>
 <guid isPermaLink="false">525310 at http://drupal.org</guid>
</item>
<item>
 <title>Environments</title>
 <link>http://drupal.org/project/envts</link>
 <description>&lt;p&gt;Envts (Environments) module&lt;br /&gt;
by Ben Buckman (thebuckst0p) @ EchoDitto (ben at echoditto dot com)&lt;/p&gt;
&lt;p&gt;This module was created to fill the need for &lt;b&gt;*two-dimensional* environment/host management&lt;/b&gt;.&lt;br /&gt;
* &lt;b&gt;What's an environment?&lt;/b&gt; An environment is a development or server location where a full Drupal build (possibly including multiple hosts) is set up. In our work, we tend to have&lt;br /&gt;
  1) a primary 'dev' environment (site.dev.ourwork.com),&lt;br /&gt;
  2) local environments for each developer (site.dev.local),&lt;br /&gt;
  3) a staging environment (staging.site.com),&lt;br /&gt;
  4) a live site (&lt;a href="http://www.site.com" title="www.site.com" rel="nofollow"&gt;www.site.com&lt;/a&gt;), etc.&lt;br /&gt;
But each of these environments can have &lt;b&gt;multiple sites/hosts&lt;/b&gt;, making the number of actual hosts to track and toggle grow exponentially.&lt;br /&gt;
The domain_access module does a good job of tracking hosts, but in only one environment.&lt;/p&gt;
&lt;p&gt;It's lightweight, has no UI (yet), but simply allows other modules to define environments with a hook.&lt;br /&gt;
(Anyone is welcome to create a UI for the module, since my time is limited!)&lt;/p&gt;
&lt;p&gt;TERMINOLOGY USED:&lt;br /&gt;
 &lt;b&gt;'envt':&lt;/b&gt; a code environment with multiple sites, such as 'dev', 'live', 'local'&lt;br /&gt;
 &lt;b&gt;'site':&lt;/b&gt; a site NAME, possibly used in multiple environments, e.g. 'primary', 'secondary'&lt;br /&gt;
 &lt;b&gt;'host':&lt;/b&gt; the domain of a site, e.g. &lt;a href="http://www.site.com" title="www.site.com" rel="nofollow"&gt;www.site.com&lt;/a&gt; or site.dev.local, preferably matching the /sites/ folder and $base_root (without http:// prefix)&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/envts" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/53">Administration</category>
 <category domain="http://drupal.org/taxonomy/term/59">Developer</category>
 <category domain="http://drupal.org/taxonomy/term/124">Site navigation</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Mon, 20 Jul 2009 17:18:04 +0000</pubDate>
 <dc:creator>thebuckst0p</dc:creator>
 <guid isPermaLink="false">525308 at http://drupal.org</guid>
</item>
<item>
 <title>Markup</title>
 <link>http://drupal.org/project/markup</link>
 <description>&lt;p&gt;This tiny module adds the ability for site admins to add "Markup" widgets to the form. These essentially let designers of cck content-types insert additional markup into the node/edit form to display to content-authors. This is the equivalent of adding additional elements to $form of the type '#markup'.&lt;/p&gt;
&lt;p&gt;The module does not add anything to the $node object for the content being created, and utilizes form_alter to remove unnecessary fields from the '_content_admin_field' form when this widget is being created.&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/88">Content Construction Kit (CCK)</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Mon, 20 Jul 2009 14:41:18 +0000</pubDate>
 <dc:creator>ebeyrent</dc:creator>
 <guid isPermaLink="false">525164 at http://drupal.org</guid>
</item>
<item>
 <title>Background</title>
 <link>http://drupal.org/project/background</link>
 <description>&lt;div style="width: 250px" class="image-attach-teaser"&gt;&lt;a href="/project/background"&gt;&lt;img src="http://drupal.org/files/images/Picture 3_11.thumbnail.png" alt="Screenshot of the background settings. (Below favicon and logo settings)" title="Screenshot of the background settings. (Below favicon and logo settings)"  class="image image-thumbnail " width="250" height="217" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;Allows for themes to upload a background image in theme settings.&lt;/p&gt;
&lt;p&gt;This works best in themes with fixed width, where a background shows.&lt;/p&gt;
&lt;h3&gt;Features&lt;/h3&gt;

&lt;li&gt;Choose a color&lt;/li&gt;
&lt;li&gt;Uses native drupal API for file uploading&lt;/li&gt;
&lt;li&gt;Located in theme settings form&lt;/li&gt;
&lt;li&gt;Positioning&lt;/li&gt;
&lt;li&gt;Repeat&lt;/li&gt;
&lt;li&gt;Attachment (Scroll, fixed)&lt;/li&gt;

</description>
 <category domain="http://drupal.org/taxonomy/term/62">File management</category>
 <category domain="http://drupal.org/taxonomy/term/73">Theme related</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <enclosure url="http://drupal.org/image/view/524816/preview" length="58351" type="image/png" />
 <pubDate>Mon, 20 Jul 2009 06:26:24 +0000</pubDate>
 <dc:creator>skiquel</dc:creator>
 <guid isPermaLink="false">524810 at http://drupal.org</guid>
</item>
<item>
 <title>Smart menus, Smart tabs</title>
 <link>http://drupal.org/project/smart_menus</link>
 <description>&lt;p&gt;The &lt;a href="http://drupal.org/project/smart_menus" rel="nofollow"&gt;Smart menus, Smart tabs&lt;/a&gt; duo of modules make everyone's Drupal experience just that little bit more convenient. The two modules give menus and tabs a memory, so that when you revisit a page, your previous tab or menu choice is already pre-selected for you. Not only will this save you numerous clicks, it will almost feel like the system senses where you'd like to go, making the experience more intuitive. No longer will you have to retrace your clicks to get back to where you wanted to stay or waste clicks to escape from Drupal's rigid default selections. Instead you'll find that Smart menus and Smart tabs create default selections naturally, based on your personal click patterns as they evolve during the session.&lt;br /&gt;
Once you've used these modules for a while you won't notice they're there -- but you'll miss them when they're gone.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/smart_menus" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/124">Site navigation</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Mon, 20 Jul 2009 06:16:41 +0000</pubDate>
 <dc:creator>RdeBoer</dc:creator>
 <guid isPermaLink="false">524808 at http://drupal.org</guid>
</item>
<item>
 <title>Views UI: Edit Headers/Footers</title>
 <link>http://drupal.org/project/views_header_footer</link>
 <description>&lt;p&gt;Does your client want to modify the header or footer of a view, but you don't want to train them on the rather intimidating Views UI admin interface, or give them access to pages that may allow them to mess up their site?  Then this handy little module is the solution for you! &lt;/p&gt;
&lt;p&gt;"Views UI: Edit Headers/Footers" provides a separate interface that displays a list of views (defined by you, so you can exclude certain views) and allows users with the correct permission to modify the header and footer content. &lt;/p&gt;
&lt;h2&gt;Compatibility&lt;/h2&gt;
&lt;p&gt;Views 6.x-2.x&lt;/p&gt;
&lt;h2&gt;How-To&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The edit page is accessed via "Content management" --&amp;gt; "Edit Views headers/footers."
&lt;/li&gt;&lt;li&gt;To define which views to display, visit "Site Configuration" --&amp;gt; "Views" --&amp;gt; "Editable headers/footers"
&lt;/li&gt;&lt;li&gt;Make sure the user role has the "edit views headers/footers" permission.
&lt;/li&gt;&lt;li&gt;Please note that the  "override" button will be hidden, so if your view uses multiple displays, you will probably want to modify the header/footer fields to be "overriden," otherwise it will update the default display when the user goes in and modifies them.
&lt;/li&gt;&lt;/ul&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/53">Administration</category>
 <category domain="http://drupal.org/taxonomy/term/57">Content</category>
 <category domain="http://drupal.org/taxonomy/term/89">Views</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Sun, 19 Jul 2009 23:22:27 +0000</pubDate>
 <dc:creator>Jonah Ellison</dc:creator>
 <guid isPermaLink="false">524580 at http://drupal.org</guid>
</item>
<item>
 <title>Quick filter</title>
 <link>http://drupal.org/project/quick_filter</link>
 <description>&lt;p&gt;&lt;strong&gt;This module is a functional duplicate of http://drupal.org/project/module_filter&lt;/strong&gt;&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/53">Administration</category>
 <category domain="http://drupal.org/taxonomy/term/75">Utility</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Sun, 19 Jul 2009 22:28:03 +0000</pubDate>
 <dc:creator>restyler</dc:creator>
 <guid isPermaLink="false">524546 at http://drupal.org</guid>
</item>
<item>
 <title>Permit own permissions</title>
 <link>http://drupal.org/project/pwn</link>
 <description>&lt;dl&gt;
&lt;dt&gt;pwn&lt;/dt&gt;
&lt;dd&gt;to utterly own someone&lt;/dd&gt;
&lt;/dl&gt;
&lt;h3&gt;Problem:&lt;/h3&gt;
&lt;p&gt;  A site is beautifully set up and guards against catastrophic user error (blowing things up) while giving the person you made it for as much flexibility and power to add to it as is possible...  almost.&lt;/p&gt;
&lt;p&gt;He can't change what permissions other roles have...  unless you give him &lt;em&gt;administer permissions&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Now Mr. Just-Learned-Drupal-From-You (in five-minute impromptu sessions because he cut the training budget from the project) can see the &lt;em&gt;configure nuclear options&lt;/em&gt; permission, and he thinks it would be nifty to play around with that himself.&lt;/p&gt;
&lt;p&gt;Before his assistants can use their delegated permissions, on the day of his Superbowl ad announcing the site he puts it into offline mode, the smiling blue Druplicon becomes that much more (in)famous, and he sues you for a half-million dollars.&lt;/p&gt;
&lt;p&gt;Don't let this happen to you!&lt;/p&gt;
&lt;h3&gt;Solution:&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;P&lt;/strong&gt;ermit o&lt;strong&gt;wn&lt;/strong&gt; permissions provides the &lt;em&gt;share permissions&lt;/em&gt; permission.  A user in a role with this permission can grant (or revoke) any permission that she has.&lt;/p&gt;
&lt;p&gt;It's that simple.  That's why we needed a big lead-up.&lt;/p&gt;
&lt;p&gt;For getting something like this into Drupal core, potentially, see &lt;a href="http://drupal.org/node/48544" rel="nofollow"&gt;Do not let grant more permissions than you actually have&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/pwn" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/53">Administration</category>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/76">User management</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Sun, 19 Jul 2009 20:55:30 +0000</pubDate>
 <dc:creator>Benjamin Melançon</dc:creator>
 <guid isPermaLink="false">524478 at http://drupal.org</guid>
</item>
<item>
 <title>Cache</title>
 <link>http://drupal.org/project/cache</link>
 <description>&lt;p&gt;Yet another caching system for Drupal.&lt;/p&gt;
&lt;p&gt;Started as fork of &lt;a href="/project/cacherouter" rel="nofollow"&gt;Cache Router&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;Testing&lt;/h2&gt;
&lt;p&gt;This module is in alpha and needs your help with some testing especially - xcache and eaccelerator engines, session handler.&lt;/p&gt;
&lt;h2&gt;About&lt;/h2&gt;
&lt;p&gt;"Cache" module provides bridge between Drupal and alternative cache handler&lt;br /&gt;
implementators: e.g. APC, memcache, redis.&lt;/p&gt;
&lt;p&gt;It provides implementation of page_fast_cache() function.&lt;/p&gt;
&lt;h2&gt;Features&lt;/h2&gt;
&lt;p&gt;- Additional cache handlers.&lt;br /&gt;
- page_fast_cache() implementation.&lt;br /&gt;
- hook_requirements() implementation. See report status of used&lt;br /&gt;
  cache handlers.&lt;br /&gt;
- Alternative session handler.&lt;br /&gt;
- Set of core patches to improve performance on big Drupal web-sites.&lt;br /&gt;
- In case all alternative cache handlers fail (e.g. no APC, memcache installed)&lt;br /&gt;
  it will use standard database caching. Administrator then may check&lt;br /&gt;
  "Status report" page and see why any of cache handler fails.&lt;br /&gt;
- Cache handlers chaining.&lt;/p&gt;
&lt;h2&gt;Requirements&lt;/h2&gt;
&lt;p&gt;By default, "Cache" module doesn't require any additional cache handler&lt;br /&gt;
implementations. It will use database for cache storage as default&lt;br /&gt;
Drupal installation does.&lt;/p&gt;
&lt;h2&gt;Optional requirements&lt;/h2&gt;
&lt;p&gt;To gain all the features of "Cache" module you might want to install one&lt;br /&gt;
or more alternative cache handler engines:&lt;br /&gt;
  - PHP APC&lt;br /&gt;
  - memcache&lt;br /&gt;
  - redis&lt;/p&gt;
&lt;h2&gt;Installation&lt;/h2&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/cache" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/123">Performance and Scalability</category>
 <category domain="http://drupal.org/taxonomy/term/52">Third-party integration</category>
 <category domain="http://drupal.org/taxonomy/term/75">Utility</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Sun, 19 Jul 2009 19:09:59 +0000</pubDate>
 <dc:creator>doq</dc:creator>
 <guid isPermaLink="false">524420 at http://drupal.org</guid>
</item>
<item>
 <title>RealChat module</title>
 <link>http://drupal.org/project/realchat</link>
 <description>&lt;div style="width: 300px" class="image-attach-teaser"&gt;&lt;a href="/project/realchat"&gt;&lt;img src="http://drupal.org/files/images/ChatExample.thumbnail.jpg" alt="An example of chatting from a Drupal site using a RealChat server" title="An example of chatting from a Drupal site using a RealChat server"  class="image image-thumbnail " width="300" height="189" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;The &lt;strong&gt;RealChat Module&lt;/strong&gt; lets the users of a Drupal site chat via a &lt;a href="http://www.realchat.com" rel="nofollow"&gt;RealChat&lt;/a&gt; server.  It adds a single link to Drupal's menu system called "Chat now!" by default.   An authenticated user who clicks this link enters a chat at a designated RealChat server with her chat nickname set to her Drupal username, chat profile pointing to her user profile page on the Drupal site, and avatar set to her picture (if available) on the Drupal site.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/realchat" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <enclosure url="http://drupal.org/image/view/524374/preview" length="28044" type="image/jpeg" />
 <pubDate>Sun, 19 Jul 2009 17:51:05 +0000</pubDate>
 <dc:creator>crotown</dc:creator>
 <guid isPermaLink="false">524378 at http://drupal.org</guid>
</item>
<item>
 <title>Book Inherit Type</title>
 <link>http://drupal.org/project/book_inherit_type</link>
 <description>&lt;p&gt;Book Inherit Type alters the "Create Child Page" link on book pages so that new child pages are created with the same type as the parent.&lt;/p&gt;
&lt;p&gt;This module is based on the patches created by kassissieh and JuliaKM in this issue:&lt;/p&gt;
&lt;p&gt;&lt;span class="project-issue-status-13 project-issue-status-info"&gt;&lt;a href="/node/460736" title="Status: needs work"&gt;#460736: Add child page should inherit parent&amp;#039;s content type. Or should it ? &lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Additional features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Per node type override of the book module default.&lt;/li&gt;
&lt;/ul&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/57">Content</category>
 <category domain="http://drupal.org/taxonomy/term/124">Site navigation</category>
 <category domain="http://drupal.org/taxonomy/term/75">Utility</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Sun, 19 Jul 2009 06:10:55 +0000</pubDate>
 <dc:creator>criznach</dc:creator>
 <guid isPermaLink="false">523952 at http://drupal.org</guid>
</item>
<item>
 <title>Wibiya</title>
 <link>http://drupal.org/project/wibiya</link>
 <description>&lt;div style="width: 300px" class="image-attach-teaser"&gt;&lt;a href="/project/wibiya"&gt;&lt;img src="http://drupal.org/files/images/wibiya.thumbnail.png" alt="Wibiya toolbar" title="Wibiya toolbar"  class="image image-thumbnail " width="300" height="125" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;Integrate Wibiya social toolbar in Drupal&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/57">Content</category>
 <category domain="http://drupal.org/taxonomy/term/58">Content display</category>
 <category domain="http://drupal.org/taxonomy/term/60">Evaluation/rating</category>
 <category domain="http://drupal.org/taxonomy/term/101">Javascript Utilities</category>
 <category domain="http://drupal.org/taxonomy/term/67">Media</category>
 <category domain="http://drupal.org/taxonomy/term/97">Multilingual</category>
 <category domain="http://drupal.org/taxonomy/term/105">Search</category>
 <category domain="http://drupal.org/taxonomy/term/124">Site navigation</category>
 <category domain="http://drupal.org/taxonomy/term/119">Statistics</category>
 <category domain="http://drupal.org/taxonomy/term/70">Syndication</category>
 <category domain="http://drupal.org/taxonomy/term/73">Theme related</category>
 <category domain="http://drupal.org/taxonomy/term/52">Third-party integration</category>
 <category domain="http://drupal.org/taxonomy/term/75">Utility</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <enclosure url="http://drupal.org/image/view/523458/preview" length="14076" type="image/png" />
 <pubDate>Sat, 18 Jul 2009 14:36:42 +0000</pubDate>
 <dc:creator>vitzo.com</dc:creator>
 <guid isPermaLink="false">523438 at http://drupal.org</guid>
</item>
<item>
 <title>Community Tasks</title>
 <link>http://drupal.org/project/community_tasks</link>
 <description>&lt;p&gt;Support the request / commit /acknowledgement process for volunteering tasks.&lt;/p&gt;
&lt;p&gt;Typical story of a task&lt;br /&gt;
1 The community organiser posts a task to the site&lt;br /&gt;
2 A member commits to do this task&lt;br /&gt;
3 The organiser marks the task as complete, and the member's task counter increases.&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Sat, 18 Jul 2009 02:02:10 +0000</pubDate>
 <dc:creator>matslats</dc:creator>
 <guid isPermaLink="false">523098 at http://drupal.org</guid>
</item>
<item>
 <title>Google Search Appliance Simple Search</title>
 <link>http://drupal.org/project/gsa_search</link>
 <description>&lt;p&gt;This project is meant to provide a simpler / more themeable alternative to the module below:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/google_appliance" title="http://drupal.org/project/google_appliance" rel="nofollow"&gt;http://drupal.org/project/google_appliance&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I ported some code from the other google appliance module, but I drastically reduced to the code that builds the query that hits GSA. The search results pages are broken up into either templates or theme functions and are meant to be easily overridable from the site theme. This project to my knowledge only supports GSA - I haven't integrated anything for GSA mini.&lt;/p&gt;
&lt;p&gt;This project has stemmed from our company's need to have a simple GSA implementation that's easily themeable and with code someone can actually read and understand. One of the problems we had with the other implementation was drilling down to where the query was being made to find out what was happening on the back end.&lt;/p&gt;
&lt;p&gt;Also I have added an API hook called hook_parse_gsa_result_row() allowing developers who need to override the parsing of each GSA result row the ability to do additional parsing in addition to being able to theme the results from an included .tpl. The goal of this project was to prevent continually having to hack a GSA module for each site when typically all that's needed to be modified are look and feel.&lt;/p&gt;
&lt;p&gt;Please give us feedback and let us know how we can improve this module.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/gsa_search" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/52">Third-party integration</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Fri, 17 Jul 2009 20:25:26 +0000</pubDate>
 <dc:creator>jaykali</dc:creator>
 <guid isPermaLink="false">522824 at http://drupal.org</guid>
</item>
<item>
 <title>Media: Bits On The Run</title>
 <link>http://drupal.org/project/media_bitsontherun</link>
 <description>&lt;p&gt;This adds support for the custom premium players of Bits On The Run hosted content, available from &lt;a href="http://bitsontherun.com/" title="http://bitsontherun.com/" rel="nofollow"&gt;http://bitsontherun.com/&lt;/a&gt;. (Yes that's by the same guy who did JW FLV Media Player and Longtail...)&lt;/p&gt;
&lt;p&gt;To use this module, you'll first need to install Embedded Video Field, which is packaged with Embedded Media Field (from &lt;a href="http://drupal.org/project/emfield" title="http://drupal.org/project/emfield" rel="nofollow"&gt;http://drupal.org/project/emfield&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;Set up a content type to use a Third Party Video field as you normally would. Also ensure that you have enabled the new Bits On The Run provider from the Admin screen at /admin/content/emfield.&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/88">Content Construction Kit (CCK)</category>
 <category domain="http://drupal.org/taxonomy/term/67">Media</category>
 <category domain="http://drupal.org/taxonomy/term/52">Third-party integration</category>
 <category domain="http://drupal.org/taxonomy/term/89">Views</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Fri, 17 Jul 2009 18:02:47 +0000</pubDate>
 <dc:creator>aaron</dc:creator>
 <guid isPermaLink="false">522702 at http://drupal.org</guid>
</item>
<item>
 <title>Ubercart Price Per Role</title>
 <link>http://drupal.org/project/uc_price_per_role</link>
 <description>&lt;p&gt;This module allows you to enter different sale prices per product for different roles in an &lt;a href="http://drupal.org/project/ubercart" rel="nofollow"&gt;Ubercart&lt;/a&gt; store.&lt;/p&gt;
&lt;p&gt;Install and enable the module as normal. In the store configuration menu there will be a new "Price per role settings" page, here you can select the roles for individual pricing and set a priority order for the prices. After setting this up, the new price entry fields will be available from the product edit pages. When viewing or adding a product to the cart, if a role-specific price is available and the user has that role, that price will be used. If no prices are available that match the user's role, the standard product sell price will be used.&lt;/p&gt;
&lt;h2&gt;Credits&lt;/h2&gt;
&lt;p&gt;Developed by &lt;a href="http://www.longwaveconsulting.com/" rel="nofollow"&gt;Longwave Consulting&lt;/a&gt;, sponsored by &lt;a href="http://www.3xlogic.com" rel="nofollow"&gt;3xLOGIC&lt;/a&gt;.&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/104">e-Commerce</category>
 <category domain="http://drupal.org/taxonomy/term/74">User access/authentication</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Fri, 17 Jul 2009 17:39:10 +0000</pubDate>
 <dc:creator>longwave</dc:creator>
 <guid isPermaLink="false">522666 at http://drupal.org</guid>
</item>
<item>
 <title>Ubuntu Drupal Planet</title>
 <link>http://drupal.org/project/udplanet</link>
 <description>&lt;h2&gt;Not Released&lt;/h2&gt;
&lt;p&gt;Because of the unforgiving nature of CVS, all development will occur on Launchpad until a beta release is available.&lt;/p&gt;
&lt;h2&gt;Description&lt;/h2&gt;
&lt;p&gt;This module will add a page to your site. This will function similarly to PlanetPlanet which powers planet.ubuntu.com. One significant difference between this module and the aggregator module is the fact that any user can edit any feed. All feeds are open to users that can attach images to be displayed with the feeds. Administrators can place locks on the feeds to prohibit this action. This module will also contain significant styling to make the page look like planet.ubuntu.com.&lt;/p&gt;
&lt;h2&gt;Settings&lt;/h2&gt;
&lt;p&gt;This module contains the ability for any user to add a feed and contribute it the their user account to display their profile image next to the feed. Administrators can choose to lock feeds so no other users can edit them or disable feeds to prevent them from being parsed or displayed.&lt;/p&gt;
&lt;h2&gt;Development&lt;/h2&gt;
&lt;p&gt;Development occurs on Launchpad. Support requests, bug reports, latest code, etc can be found at this project page.&lt;/p&gt;
&lt;p&gt;Development Page: &lt;a href="https://launchpad.net/ubuntu-drupal-planet" title="https://launchpad.net/ubuntu-drupal-planet" rel="nofollow"&gt;https://launchpad.net/ubuntu-drupal-planet&lt;/a&gt;&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Fri, 17 Jul 2009 02:38:22 +0000</pubDate>
 <dc:creator>MTecknology</dc:creator>
 <guid isPermaLink="false">521938 at http://drupal.org</guid>
</item>
<item>
 <title>Ubuntu Drupal LoCo Map</title>
 <link>http://drupal.org/project/udlocomap</link>
 <description>&lt;h2&gt;Not Released&lt;/h2&gt;
&lt;p&gt;Because of the unforgiving nature of CVS, all development will occur on Launchpad until a beta release is available.&lt;/p&gt;
&lt;h2&gt;Description&lt;/h2&gt;
&lt;p&gt;This module will add a page to your site. It displays a map of all Ubuntu Local Communities along with information and status. The module contains everything needed to run except for a sql file that will be pulled during installation and on cron runs.&lt;/p&gt;
&lt;h2&gt;Settings&lt;/h2&gt;
&lt;p&gt;This module allows you to set the top level map as well as some various colors.&lt;/p&gt;
&lt;h2&gt;Development&lt;/h2&gt;
&lt;p&gt;Development occurs on Launchpad. Support requests, bug reports, latest code, etc can be found at this project page.&lt;/p&gt;
&lt;p&gt;Development Page: &lt;a href="https://launchpad.net/ubuntu-drupal-locomap" title="https://launchpad.net/ubuntu-drupal-locomap" rel="nofollow"&gt;https://launchpad.net/ubuntu-drupal-locomap&lt;/a&gt;&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Fri, 17 Jul 2009 02:24:49 +0000</pubDate>
 <dc:creator>MTecknology</dc:creator>
 <guid isPermaLink="false">521928 at http://drupal.org</guid>
</item>
<item>
 <title>Ubuntu Drupal Header</title>
 <link>http://drupal.org/project/udheader</link>
 <description>&lt;div style="width: 300px" class="image-attach-teaser"&gt;&lt;a href="/project/udheader"&gt;&lt;img src="http://drupal.org/files/images/Untitled_2.thumbnail.png" alt="Header" title="Header"  class="image image-thumbnail " width="300" height="43" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;h2&gt;Description&lt;/h2&gt;
&lt;p&gt;This module will add a block that can be displayed in the header area. The Ubuntu Drupal Theme has a specific region for this. A different header can be specified for each content type.&lt;/p&gt;
&lt;p&gt;The biggest benefit to this module is the ability to display a specific banner for content types.&lt;/p&gt;
&lt;h2&gt;Settings&lt;/h2&gt;
&lt;p&gt;The block for this module must first be added to the header region. In the administrative section, you can add a Default module type for content types that have no other header set for it. Each content type can have a different left/right/middle image. The right and middle sections can also have custom text added.&lt;/p&gt;
&lt;h2&gt;Development&lt;/h2&gt;
&lt;p&gt;Development occurs on Launchpad. Support requests, bug reports, latest code, etc can be found at this project page.&lt;/p&gt;
&lt;p&gt;Development Page: &lt;a href="https://launchpad.net/ubuntu-drupal-header" title="https://launchpad.net/ubuntu-drupal-header" rel="nofollow"&gt;https://launchpad.net/ubuntu-drupal-header&lt;/a&gt;&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <enclosure url="http://drupal.org/image/view/521908/preview" length="50732" type="image/png" />
 <pubDate>Fri, 17 Jul 2009 02:08:34 +0000</pubDate>
 <dc:creator>MTecknology</dc:creator>
 <guid isPermaLink="false">521910 at http://drupal.org</guid>
</item>
<item>
 <title>Ubuntu Drupal Countdown</title>
 <link>http://drupal.org/project/udcountdown</link>
 <description>&lt;div style="width: 258px" class="image-attach-teaser"&gt;&lt;a href="/project/udcountdown"&gt;&lt;img src="http://drupal.org/files/images/Screenshot_9.thumbnail.png" alt="Countdown Above Navigation" title="Countdown Above Navigation"  class="image image-thumbnail " width="258" height="217" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;h2&gt;Description&lt;/h2&gt;
&lt;p&gt;This module will add a block that will display a countdown timer. This will countdown the days until the next version of Ubuntu is released. This automatically pulls the latest package of banners. The banner options can be viewed on &lt;a href="http://www.ubuntu.com/getubuntu/countdown" title="http://www.ubuntu.com/getubuntu/countdown" rel="nofollow"&gt;http://www.ubuntu.com/getubuntu/countdown&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;Settings&lt;/h2&gt;
&lt;p&gt;After much work, most of the settings have been removed. At this point, you can choose from any of the available banners or your own custom code.&lt;/p&gt;
&lt;h2&gt;Development&lt;/h2&gt;
&lt;p&gt;Development occurs on Launchpad. Support requests, bug reports, latest code, etc can be found at this project page.&lt;/p&gt;
&lt;p&gt;Development Page: &lt;a href="https://launchpad.net/ubuntu-drupal-countdown" title="https://launchpad.net/ubuntu-drupal-countdown" rel="nofollow"&gt;https://launchpad.net/ubuntu-drupal-countdown&lt;/a&gt;&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/56">Community</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <enclosure url="http://drupal.org/image/view/522616/preview" length="28949" type="image/png" />
 <pubDate>Fri, 17 Jul 2009 01:36:37 +0000</pubDate>
 <dc:creator>MTecknology</dc:creator>
 <guid isPermaLink="false">521870 at http://drupal.org</guid>
</item>
<item>
 <title>Ajax views refresh</title>
 <link>http://drupal.org/project/ajax_views_refresh</link>
 <description>&lt;p&gt;Ajax views refresh is a plugin module for &lt;a href="http://drupal.org/project/ajax" rel="nofollow"&gt;Ajax&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Allows views to be refreshed on Ajax forms submission.&lt;br /&gt;
The best use case is a node creation form and a view of nodes (or comments) below, which would be refreshed each time you add or edit a node.&lt;/p&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/101">Javascript Utilities</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Thu, 16 Jul 2009 16:50:51 +0000</pubDate>
 <dc:creator>jide</dc:creator>
 <guid isPermaLink="false">521390 at http://drupal.org</guid>
</item>
<item>
 <title>FeedAPI Data</title>
 <link>http://drupal.org/project/feedapi_data</link>
 <description>&lt;div style="width: 300px" class="image-attach-teaser"&gt;&lt;a href="/project/feedapi_data"&gt;&lt;img src="http://drupal.org/files/images/Untitled2-1.thumbnail.jpg" alt="Dynamically allocate storage for feed elements." title="Dynamically allocate storage for feed elements."  class="image image-thumbnail " width="300" height="191" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;FeedAPI Data is a &lt;a href="http://drupal.org/project/feedapi" rel="nofollow"&gt;FeedAPI&lt;/a&gt; processor plugin for storing feed items. You can use it as alternative to the default processor FeedAPI Node.&lt;/p&gt;
&lt;p&gt;It uses &lt;a href="http://drupal.org/project/data" rel="nofollow"&gt;Data&lt;/a&gt; module for storing feed items, and &lt;a href="http://drupal.org/project/feedapi_mapper" rel="nofollow"&gt;Feed Element Mapper 2&lt;/a&gt; for freely configuring which feed elements to store as what field type. &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Feed items are stored in single row records dynamically allocated by Data module.&lt;/li&gt;
&lt;li&gt;Which elements of feed items to store can be configured on UI.&lt;/li&gt;
&lt;li&gt;Data module generates Views integration.&lt;/li&gt;
&lt;/ul&gt;
</description>
 <category domain="http://drupal.org/taxonomy/term/70">Syndication</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <enclosure url="http://drupal.org/image/view/521206/preview" length="70168" type="image/jpeg" />
 <pubDate>Thu, 16 Jul 2009 14:04:04 +0000</pubDate>
 <dc:creator>alex_b</dc:creator>
 <guid isPermaLink="false">521198 at http://drupal.org</guid>
</item>
<item>
 <title>Data</title>
 <link>http://drupal.org/project/data</link>
 <description>&lt;p&gt;The Data module provides&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;an API for dynamically allocating tables for single-row records.&lt;/li&gt;
&lt;li&gt;an API for insert/update/delete operations and describing how tables join to each other.&lt;/li&gt;
&lt;li&gt;automatic views integration.&lt;/li&gt;
&lt;li&gt;export table definitions to code (planned).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Its companion Data UI (included) provides&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;UI to add new database tables.&lt;/li&gt;
&lt;li&gt;UI to add or alter columns to existing tables managed by Data module.&lt;/li&gt;
&lt;li&gt;default views for tables managed by Data module (planned).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You may want to&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;check out &lt;a href="http://drupal.org/project/feedapi_data" rel="nofollow"&gt;FeedAPI Data&lt;/a&gt; module for using Data as a storage engine for feed items.&lt;/li&gt;
&lt;li&gt;keep in mind that this module still needs to mature and a couple of thorough reviews - the API may be moving in this time.&lt;/li&gt;
&lt;li&gt;know that Data module is the successor of &lt;a href="http://paris2009.drupalcon.org/session/open-data-flatstore" rel="nofollow"&gt;Flatstore&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;API&lt;/h3&gt;
&lt;p&gt;(preliminary, not complete)&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;br /&gt;
// Get a table.&lt;br /&gt;
$table = data_get_table('my_table');&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;// If this table is not available create a table.&lt;br /&gt;
if (!$table) {&lt;br /&gt;
  $table = data_create_table('my_table', $schema).&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;// Save some data to it.&lt;br /&gt;
$table-&amp;gt;save($data);&lt;/p&gt;
&lt;p&gt;// Remove all data from the table.&lt;br /&gt;
$table-&amp;gt;truncate();&lt;/p&gt;
&lt;p&gt;// Destroy the table.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupal.org/project/data" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://drupal.org/taxonomy/term/57">Content</category>
 <category domain="http://drupal.org/taxonomy/term/89">Views</category>
 <category domain="http://drupal.org/taxonomy/term/14">Modules</category>
 <pubDate>Thu, 16 Jul 2009 13:35:39 +0000</pubDate>
 <dc:creator>alex_b</dc:creator>
 <guid isPermaLink="false">521178 at http://drupal.org</guid>
</item>
</channel>
</rss>
