This module is to Integrate OAuth open source protocol to Services API to make it more secure.
Integration of OAuth 1.0 core with Drupal's Service API provide users/administrators a pluggable authentication system such that they can choose between the current system of API keys, or OAuth token system to access desired web services. The method OAuth uses is to provide “tokens” to users instead of keys. Now for each kind of web service, OAuth issues a different kind of token to user. Also, these tokens are time bound an amount of access time to another service and then it expires automatically (could be a two hour access time).
Discussion Link : http://groups.drupal.org/node/10268
GSoC wiki page link : http://groups.drupal.org/node/10910
WYSIWYG editor as textarea replacement based on HtmlBox original code by Remiya Solutions released under MIT license.
The editor is based on jQuery the official JavaScript library of Drupal.
Code coming soon!
This module was sponsored by NowPublic.com.
Selling Online with Drupal e-Commerce is Packt's new book, written by Michael Peacock, aimed at users wishing to create an online store, and uses Drupal and its e-Commerce modules to achieve this. With more and more websites aiming to integrate all of their components to give a more slick and streamlined effect for users - by using Drupal e-Commerce, the site and the store are already integrated providing both a powerful website and a powerful online store.
Xapian integration module
Provides ability to replace core search with Xapian based search. Includes sample code for views as well.
This project uses Nodequeue's Smartqueue API to provide a nodequeue for each user of one or more specified roles. This project is part of the 2008 Google Summer of Code and when completed should provide the following functionality:
1) Administrators can specify which user roles automatically receive nodequeues
2) When a user of a specified role is created, a nodequeue corresponding to that user will be created.
3) When a user is deleted, the corresponding nodequeue will be deleted.
- a) The module should prompt and warn the administrator before deleting the nodequeues.
4) Administrators can specify which node types should be available in user nodequeues.
a) Administrators could potentially be able to specify on a per-role basis which content types can be enabled in user-nodequeues. If this is the case, available node types for each user-nodequeue will consist of an aggregate of node types specified for nodequeus of that user's role.
5) An 'edit own user nodequeue' permission will be defined to allow for use cases where users cannot edit their own node queues, such as a list of selected content by a particular user that is maintained internally by website administrators\moderators.
6)The content of the user-nodequeue will display on the user's profile page
- a) The module will define a default view that is utilized on the user profile page
This project uses Nodequeue's Smartqueue API to provide a nodequeue for each organic group, editable by members of that group or the group's administrators. This project is part of the 2008 Google Summer of Code and when completed should provide the following functionality:
1) When an OG homepage node is created, a nodequeue that corresponds to that OG homepage node will be created.
2) When an OG homepage node is deleted, the corresponding nodequeue will be deleted
3) Two possibilities:
- a) Members of the Organic Group and site administrators will be able to edit the nodequeue for that Organic Group.
- b) Administrators of the Organic Group and site administrators will be able to edit that OG's nodequeue.
4) The content of the Organic Group's nodequeue will display in a block defined by a view, provided by this module
- a) Administrators can specify an alternate view that will control the display of OG nodequeues
5) Administrators can specify which node types should be available in OG nodequeues
6) When an administrator changes sitewide settings for OG Nodequeues, these changes should affect all og-nodequeues, to the extent that this is programatically practical.
For the complete project proposal, visit http://groups.drupal.org/node/10067 .
This project will provide a simple but extensible API for aggregation that ships in a configuration that covers the most common use case of aggregating feeds as nodes on a web site.
The planned architecture layout can be found here: http://feedapi.novaak.net/design.png
The result of my work will be a patch against the actual Drupal 7 which is ready-to-use and ready to be committed.
PluginManager is designed to retrieve a list of all modules and themes available and then allowing the user to choose which ones they would like to install. After they make their selections it will download the appropriate files (from drupal.org) and install them, all transparently to the user.
Mobile Codes generates Datamatrix or QR Codes that can be read by many mobile phones.
Mobile Codes module provides a filter to generate the codes, with the following format:
[mobilecodes type="type" data="data type" size="size" name="name" tinyurl="tinyurl"]content[/mobilecode]
In the future the module will provide a CCK Field.
This is an API that takes care of general booking functionality, with arbitrary time granularity. Bookable resources can have default availability times set, and bookings with time conflicts are not permitted.
AHAH Fragment is a module which returns a specified fragment from the requested page. This allows users to create callbacks for AHAH functionality with little or no code.
When the module is enabled, any HTML fragment of a page can be extracted by simply adding a get parameter to the url describing the fragment desired. Fragments can be described using standard css selectors like 'div.node' or 'div > span.class + #someid'
The module also integrates with thickbox to provide developers and themers a way to create a callback for thickbox windows without having to write any PHP.
Instructions for use are in the README.txt
File Defer is a module which searches for missing files at a remote location.
The primary use is for stage or development versions of a website. If you have a development version and a live version of the same drupal site, you can set up the dev site to look for missing files on the live sever negating the need to hand transfer those files while testing.
There are better systems for doing XMLRPC calls, e.g. look at http://drupal.org/project/services
The XMLRPC API exposes two functions - in most cases you will only want to use one.
<?php
xmlrpc_api_query($xmlrpcuri, $method, $arguments)
?>
xmlrpcuri supports this format:
[http/ssl]://[Basic:Digest][user:pass]@[name|address]:[port]/[path]
Note two things:
It's a very simple library in a way. The UI allows you to generate xmlrpcuris. These you can store wherever you want - maybe in a protected node field. Then you could put XMLRPC calls into workflow/ng actions.
Included is a sample server implementation that tells you the server time if called correctly!
Don't forget to enable the UI module so you can easily run tests.
Let me know if you have any questions.
Hi,
I was wondering, what is the best way to host multiple drupal sites on the one server using different themes, different databases and different directories. At the moment, I have multiple Drupal installations running with separate databases, in separate directory locations. They run off the same domain name from a folder that is appended to the domain name.
Any help would be great.
Thanks,
Sarah
This project is apart of 2008 Google Summer of Code. The module is focused on increasing efficiency in form validating in Drupal.
Jado permits to use the Ext JavaScript library with Drupal 5.x.
This is a first version that simply loads all the files necessary to run Ext JS at every page requests, but for the next versions I will add more functionalities so that other modules will be able to use this module to create dynamic HTML pages.
Implements a DAV API backend that exports File Framework nodes as DAV resources and Drupal's taxonomy terms as DAV collections.
Shows node vocabularies and terms in a ordered table, only in full node view.
Main features are:
Module was designed by Eduardo Mercovich at Inspiro, developed by Lisandro Cardoso at Openware, and released as a contribution for Drupal's community. More references can be found at OpenDev group's page.