Feed aggregator

This module is supposed to create a (really) simple marketplace for Drupal Commerce.
commerce_paypal_simple module is used to transfer money using PayPal Simple Adaptive Payment API.
The payment method should not be used with the regular product order payments, It is just a place holder so that I can create payment transactions.
Payment process: The buyer pays the website, website pays the seller.

It provides an interface that allows the sellers to confirm that they've shipped the product for the buyer and specify shipping data that can be seen by the buyer.
When the buyer confirms receiving the product, a rule event is triggered and an action creates a payback order for the seller, then another action takes this order as an argument and creates a transaction using PayPal Simple Adaptive Payment API which transfers the money from the paypal account defined in the "Transfer payback order total to seller paypal account" Rules action to the paypal account of the seller (field_paypal_email of user entity).
You can use the Rules action "Transfer payback order total to seller paypal account" in a Drupal commerce
marketplace to transfer money from sender account (defined as rules action parameter) to the seller paypal
account (field_paypal_email on user entity).

Installation guide:

1. Disable "User orders" view
2. Install commerce_paypal_simple and commerce_payback modules
3. Create a rule with "Buyer confirmed receiving the product" event and "Create payback order for the line item" and "Transfer payback order total to seller paypal account" actions.
   Sender email in "Transfer payback order total to seller paypal account" action must be identical to API_USERNAME of paypal configuration. Marketplace fee is a decimal number. 0.05 means that 5% of the order amount will be kept as marketplace fee and the remaining 95% will be transfered to the seller's paypal account.
4. Grant "View own sell reports" , "View own purchase reports" , "View own orders" , "Change own commerce order status" in commerce payback section of permissions page to authenticated users (or whatever role that you want).
5. commerce_paypal_simple module depends on PayPal Adaptive Payments NVP SDK.
   Download it from https://www.x.com/sites/default/files/PayPal_Platform_PHP_Nvp_SDK_0.zip
   extract it and copy php_nvp_sdk/Lib/ to sites/all/libraries/paypal .
   If you do this right, You'll find CallerService.php in sites/all/libraries/paypal/
   Now open sites/all/libraries/paypal/Config/Config.php and change the values of
   API_USERNAME
   API_PASSWORD
   API_SIGNATURE
   API_ENDPOINT (this is the server address, default value is sandbox, live server is https://svcs.paypal.com/)
   APPLICATION_ID (more info at http://www.wp-instantpay.com/application-id/ - no need to change this for sandbox server)
   DEVICE_IPADDRESS (no need to change for sandbox usage)

   according to your own config and save the file.

Twitter stream to get tweets on fly

This module provides an Drupal Commerce payment method for the Portuguese payment gateway easypay.

easypay allows payments with credit cards as well as through the portuguese ATM network - Multibanco by generating Multibanco References for each Commerce order.

Multibanco is an interbank network in Portugal owned and operated by Sociedade Interbancaria de Serviços S.A. (SIBS), that links the ATMs of all the banks in Portugal. The bank members of Multibanco control the SIBS. Multibanco is a fully-integrated interbank network and offers more services than the usually found in other countries, making that one of its most known characteristics. Multibanco in itself does not only encompass ATMs. It has a full-fledged EFTPOS network called Multibanco Automatic Payment, and is also a provider of mobile phone and Internet banking services through the TeleMultibanco and MBNet services respectively.

The Bot URL module integrates with the Bot module that simply responds with the title of any URL mentioned in IRC. For example:

Module also includes a hook that other modules can key into specific URLs being mentioned and change the response. For example, the Redmine module could respond to issues on a private Redmine install.

• Bot module

A experimental version of http://drupal.org/project/commerce_pagseguro, but fully functional. These issue #1396646: Update module with latest API changes to avoid errors drove me to create this sandbox project.

XtraForm is a powerful data entry form.
online demo http://demo.xtraform.org/index.html

An attempt to unify how we deal with all sorts of data through wrappers and metadata

Commerce Cart does not refresh views of fields for product displays that have attributes attached to them. It only works on node displays or full content display in a view. The origin of the problem is that the AJAX call back is looking for particular classes on DIV tags - in a view these are all altered.

This module will attempt to use a hook provided in Drupal Commerce to force a refresh of the fields in a view of an individual product that has attributes.

This initial commit does nothing more than show and AJAX alert for the product id's being switched. It's a start!

I welcome any and all assistance!

This module is co-sponsored by Fastglass LLC and Swing Surgeon Golf Management

A git demo for Drupalcamp. No code of value here

This is a simple module that lets you generate many images at once (like devel generate) and the images are created/fetched from the awesome image web service at lorempixel.com.

There are some todos/features that could be nice to have implemented before promote this to full project. Wanna help out?
/ bobodrone

Developer helper tool for GIT users.
Browser based GUI to administer the GIT hook actions with drush backend.

This Aegir extension allows you to automate fetching and merging logs from multiple servers part of the same cluster in a single logfile for later analysis with various analysis tools (awstats, webalizer, piwik, etc).

It is aimed to be a simple tool that does one thing well.

This project is released and sponsored by Koumbit.org.

Creates a block that displays a follower count from a social network and a follower goal as a sort of bar graph meter thingy.

Integrates Amazon CloudSearch with Drupal SearchAPI and FacetAPI.

Currently under development. It's about 80% done and will commit in the next 1-2 weeks.

Notes:

• Select which content types and fields should be synchronised with CloudSearch
• Integrates with FacetAPI
• Automatic synchronisation of Drupal data to CloudSearch
• Can have multiple CloudSearch domains for redundancy
• Administration screens for setting up CloudSearch domains, re-queuing content, selecting indexes and configuring FacetAPI fields

Removes the need for users to press the 'Upload' button for AJAX file uploads. After selecting a file, it will be uploaded automatically instead.

Provides a views style plugin to render an add to cart form with the view results.

Often one wants to display latest content of given content type for each user/author. And it needs to be only the latest node.
It is not possible to achieve using only Views module, well at least I didn't find an easy solution.

This module keeps record of the latest content for each content type and for each user/author. It easily integrates with Views 3.

To use it

- create View listing content of given content type
- add relationship to ALC table and you are good to go.

Please note that at present ALC module tracks nodes as they are created. It will not track nodes that have been created prior to enabling ALC module.

My development sandbox for Commerce product key.

The Description is TODO

FOR DEVELOPER USE! HANDLE WITH CARE! KEEP OUT OF REACH OF CHILDREN!

Drupal 7 has a nice and comfortable feature of looking for upgrades for all installed modules, warning about new releases. However, in some special cases (notably, for custom modules developed in-house) there is no place Drupal could visit to learn about upgrades and new versions, consequently, the upgrade report page will be cluttered with not available warnings.

The system has partly catered for this by introducing the project status url entry in the module .info file (see http://drupal.org/node/542202). However, unless you have something at the URL specified that can report the module status, you will continue to see error messages in the report page.

This very simple module offers a solution to this. By introducing a common URL for all similar modules on a site (http://www.example.com/projects/[module]/[core]), it is able to provide a kind of a fake report to Drupal for all these modules, always reporting back that they are completely up-to-date. Simply use this link in your .info file, eg:

project status url = http://www.example.com/projects

and the module will always report as up-to-date.

Only use this module to suppress upgrade warnings about other modules you have complete authority over and you can make sure they are really upgraded as needed. Never disable the upgrade status report of modules that should be duly monitored for bugfixes and other reports.