Maintenance fixes only

Based off of jwilson3's Twitter Field Widget http://drupal.org/sandbox/jwilson3/1180622

Current situation

Drupal (6.x, 7.x) core module node provides a view which shows a list of all the published nodes:

http://www.example.com/node

Nowadays most Drupal installations use Views, Panels, etc, which are more configurable making this feature useless.

Description

This module adds an administration settings panel to handle /node page access.

Once it is activated there are three posible configurations:

• Core - Drupal core will handle node page access as usual: all users with 'access content' permission
• Disabled - Nobody will be able to access /node. It will return 'Page not found' (404).
• By permission - Access will be handled by a new permission: 'access node page'

Problems that resolves

In some well known projects this path has not been themed:

• http://postfun.washingtonpost.com/node
• http://community.harvard.edu/node
• http://www.mtv.co.uk/node
• http://nation.foxnews.com/node

so using this module will improve user experience and branding.

Drupal 8 issues related

• #1066830: Change /node path to /latest and allow admins to disable.
• #545758: Make q=node behavior optional/configurable
• #1210366: Per-bundle node listing pages, blocks, feeds.

Sponsor

Regular text based and hosted Captcha, better Captcha experience.

This is a simple proof-of-concept module that provides 2 functions:

• An filter handler that extends string filter types and allows you to configure an autocomplete path (e.g. user/autocomplete) for an exposed filter. The exposed filter textbox will then autocomplete from that path. Note that the current implementation will replace all string filter handlers with this, but you should consider replacing only the specific ones you need, or building your own filters on top of this instead.
• A style plugin that extends views_json (part of the Views Datasource project) to allow you to produce your own autocomplete paths for any views query. The first field is used as the autocomplete "key", and the subsequent fields will be used as the "value" (comma separated if there is more than one). If there is only one field it will be used as both the "key" and "value". Note that for autocomplete to function you will need to ensure that the view results are filtered by the first view argument - you can do this by writing your own argument handler, or by using something like views argument filters (which will hopefully possible in native views at some point). Note that this path can be used with the autocomplete filter, or separately by your own Form API code.

"Maximize your main navigation by adding text, images, videos, slideshow, tabs, menu blocks, user info ..."

WordPress offers a handy "Press This" bookmarklet that streamlines the process of writing a blog post about an article on another site. When reading something you'd like to link to, you click the bookmarklet, and a New Post window opens up with the title filled and a link in the body. If you select text on the page before clicking the bookmarklet, the selected text will be included in a blockquote in the body.

Similar functionality can be achieved with the Prepopulate module alone. QuickPost Bookmarklet adds an admin frontend to this that allows you to customize how your bookmarklet will work.