Entity Registration. Entity Registration is a simple, flexible module for allowing and tracking user registrations for events, or just about anything you want people to sign up for. Entity Registration can be integrated with Drupal Commerce to allow fee-based registrations: sell tickets to your stuff! This module is also handy if you want to collect information along with registrations: like shoe-size for a bowling event. Entity Registration does lots of things you are expecting from a registration system (like allowing you to restrict the number of total registrations for a given event), and other stuff you are crossing your fingers and hoping for (like building in automated reminder messages for your registrants).
A quick outline of how it works: There are additional settings, but that is the basic outline: just create a registration type or two, give your entity a registration field, and point it at one of your registration types. For more detailed instructions, check out the README. Details Related projects. Commerce Registration. Overview Provides Drupal Commerce with the ability to sell registrations via the Entity Registrations module. Dependencies Entity Registrations (at least 7.x-1.1)Drupal Commerce Disclaimer This module, along with Entity Registrations, is still in beta. That means there can be substantial code changes, although the schema is relatively stable. However, this does not completely remove the possibility of any major changes that will affect interaction between the two modules.
Set Up Use Drupal Commerce as usual. If you don't already have a product display set up, create one with a product reference field. Add a Registration field to the commerce product type you want. Create a product and set the Registration type (or create one if you haven't already), add a new product display with that reference, and add the settings to the DB as above. Add the product to your cart, go through checkout process and after the User Information checkout page/pane, you get to the Registration Information page/pane. Commerce No Payment. This payment module adds a "No payment required" payment method (for free stuff). This module has been replaced by the Basic payment method from Payment. Creating a "no payment required" payment method Migrating from Commerce No Payment to Payment Commerce No Payment 2 was designed to migrate existing sites to Payment.
Download Commerce No Payment 7.x-2.x, Payment 7.x-1.x, and Payment for Drupal Commerce 7.x-1.xRun update.php. A Basic payment method will be created, and all Commerce Payment transactions that previously used Commerce No Payment will be reconfigured to use the Basic payment method instead.Uninstall Commerce No Payment 2 Keep using Commerce No Payment Commerce No Payment will no longer receive updates. Payment. Commerce Extra. Commerce Extra module allows site builders to enable extra features or improvements which are missing from Drupal Commerce core. The module is a collection of minimal submodules which some of developer might not consider worth of a full project and therefore are added into this module. New features are welcome! Please post your feature requests into issue queue! If you're developer and don't want to create a full project for small tweak, this is the right place. The module is work in progress and should not be installed into any production site.
See video screencast about this module made by Pedro Cambra from Commerce Guys. Feature/improvement overview Improve checkout by pre-populating customer profile information's addressfield. Installation & configuration The module itself obviously requires Commerce and submodules determine their dependencies. Just enable the module and enable features from admin/commerce/config/commerce_extra. Commerce Extra Address Populate Commerce Extra Login Page. Commerce Registry. Commerce Tickets. Commerce Tickets allows the site admin to create a Ticket purchase system, it creates a new Product type named Commerce Ticket, and a new Field named Commerce Ticket Field. The admin needs to create some ticket types, then add the Commerce Ticket Field to the required content type. The Commerce Ticket Field then needs to be configured to allow a specific number of ticket types to be purchased on the content, and whether the customer needs to enter his/her name along with the ticket, and the text of the "Buy Now" button.
The admin then creates a new content and fills in the ticket types from the tickets he previously created. When the user views the content, he can see a select with the number of tickets that is required, for every number the Total Cost is updated automatically via ajax. If the admin chooses to require the customer to enter his name, 2 new fields for First name and Last name appear for each ticket and the user is required to fill them before proceeding to checkout. Commerce Contributions. Commerce Contributions provides a way where users can contribute/invest/support a specific Project/Organization/Cause, It works by adding a Commerce Contributions Field that can be added to any content type, and when users view the content page they can see the Contributions Meter and Contribute.
The Commerce Contributions Field can be customized to include a custom button text like "Contribute Now", "Invest Now", "Donate" ...etc The Commerce Contributions Field also allows to customize the name of the product that gets added dynamically to the cart on checkout in the form of Contribute [amount], for example: Contribute $100, Invest $100, Donate $100 ....etc The Commerce Contributions Field allows the users to enter a Target amount, and to choose between 2 different displays one with the Meter and one without the Meter.
The Commerce Contributions module provides a Contributions tab in the user page, where the user can see all the contributions he made on the site. Commerce Custom Order Status. Commerce Express Checkout. This module integrates with the Product reference field and adds a new widget that allows the user to put an Express Checkout button. The Express Checkout button redirects to the Checkout page directly, without going to the Cart first, It also removes the Review page and adds the Payment checkout pane to the Checkout page, so the whole checkout process is done on one page.
The Commerce Express Checkout module also provides a very cool functionality, It gives the user the ability to generate Express Checkout buttons for any Commerce Product on the site, these checkout buttons can be used on any part of the site, without the need to add a product reference field, this functionality can be found under admin/commerce/products/express-checkout-links. It's not just that! This module was developed and sponsored by JesoX. Commerce order confirm. This module provides a confirmation process to the order. It is suitable when your commerce based shop does not contain payment and you do not want to create Drupal accounts for all orders. Using the confirmation method of this module you can be sure the order that was made is valid. Initial development sponsored by Calivita.de. Overview This module creates a random confirmation code for all created order. After the checkout the customer gets an email with this confirmation code and an url to confirm his order.
The url contains the confirmation code already, so the customer only needs to click on it. After a successful confirmation the order status changes so you can start process the confirmed orders. Customization/settings At the admin/commerce/config/order/confirm-settings you can set up the initial and the confirmation statuses. You can set there the redirection url where the customer will redirected after the confirmation. E-mail tokens This module provides two tokens for emails. Commerce File Bundle. This module integrates the commerce_file module with the commerce_product_bundle module. Currently you can add products containing commerce_file fields into bundles, but when a customer purchases the bundle the files will not be made available. Similarly, any issued file licences will not be revoked if the order is canceled. This module adds that functionality by exposing the files to the bundle line items and exposing rules and actions that issue/revoke file licences for bundled files.
Module Dependencies: How to use: Install and enable commerce_file_bundle in the usual way.Check that any commerce_file and commece_product_bundle configurations are set. 7.x-1.0-beta1: This release was tested by the maintainer and during PAR review. Sponsored by: IdeaDen. Commerce Rules Extra. Commerce Profile2. Commerce Product Add-on.
Commerce Product Add-On allows users to attach products as options to the add to cart form of another product. This is particularly useful for things like event sponsorship, optional accessories, and other up-sells. It works by adding settings to the entityreference field if the field is attached to a product type, then modifying the Add to Cart form. It also adds a new view mode for product entities, so you can change how a product is displayed when it is functioning as an "add-on. " Adding the extra products to the cart are done with rules, so you can add conditions if required, so this can be compatible with modules like Commerce Stock. You'll just need to tweak the rule yourself.
Dependencies Configuration Add an entityreference field to a product type. Possibly coming in the future This was developed for the MemberDrop distribution, and is sponsored by LwebG. Commerce Invoice Print. Purpose This module fills a gap between Commerce Invoice and Print modules. It allows developers to create in their theme a template file to be used for and only for Drupal Commerce order invoice print pages. How-to After configuring both Print and Commerce Invoice modules, copy the print.tpl.php template file from print module's folder to your custom theme's folder, and rename it following patterns (by ascending preference order): print--invoice.tpl.php will apply to all invoice print pagesprint--invoice-[order-id].tpl.php will apply to invoice print pages for order of id [order-id]print--html--invoice.tpl.php will apply to all invoice print pages using HTML format (only format supported right now by this module)print--html--invoice-[order-id].tpl.php will apply to invoice print pages using HTML format for order of id [order-id] The order variable is passed to the template and available under $commerce_order.
Dependencies About. Commerce Pickup. This module provides a "Pickup" shipping method for Drupal Commerce. It allows the store administrator to select an existing entity+bundle in their site to use as a "pickup location". Shipping services are automatically generated and linked to these entities as you create them. The easiest way to start is to create a "Pickup Location" nodetype, and configure Commerce Pickup to use it.
Views and Token integration is also provided, so that the selected pickup locations can be displayed in Views, emails, etc. Installation Download and install the module and dependencies.Go to /admin/commerce/config/shipping/methods/pickup/edit and select the entity+bundle to use for pickup locations.Create pickup location entities. Dependencies: Note on Multi-Language Sites Enable the Entity Translation module to fix duplicated pickup location options in checkout. Commerce Wishlist. This module provides a Wishlist to use with Drupal Commerce. It comes with a wishlist page featuring a similar interface to Commerce’s Shopping Cart and a block – both can be fully and easily customized as they’re backed by the Views module (great for Themers). Features Provides an “Add to Wishlist” button on the display product node;Creates a customizable list with Views to display all products on the Wishlist – both as a page and as a block;Recognizes and stores product variations;Makes it possible for users to easily delete or switch products in their Wishlist to their Shopping Cart with the click of a button; Installation It should be pretty straightforward.
Just install the module, configure the predefined Wishlist Views to meet your needs (if necessary) and you’re good to go. Sponsors This project is sponsored by Openquest and Wunderkraut. Openquest provides custom-tailored solutions based in Drupal to meet the needs of our clients.