Ubercart Conditional Attributes

Component type

module

Maintenance status

Development status

Downloads

2172

Component created

Component changed

What is Ubercart Conditional Attributes?

This module can be used to define dependency relationships between options and attributes for each product class. Once established, these dependencies will be applied to all products of that class. Dependent attributes will only be shown (for "enable"-type dependencies) or hidden (for "disable" type dependencies) once the option on the parent attribute is selected.

For example, say you run a pizza online store and you offer a free drink when the user orders a large pizza. Your pizza product class could have a 'Size' attribute with options Small/Medium/Large and a 'Drink' attribute with options for various popular soda brands. Conditional Attributes could be used to define 'Size' as a parent attribute with option 'Large' enabling 'Drink'. The drink selection would then remain hidden until the time when the user selects 'Large' as their choice for 'Size'.

Features

  • Dependency relationships are applied to all products within a given product class at once
  • Functions with several product classes
  • Has support for both 'enable' ("show only when") and 'disable' ("hide only when") relationship types
  • Hidden attributes are removed from the cart product entirely
    • Hidden attributes that are marked as required will not cause problems
    • Hidden attributes will not cause any product price alterations
  • Nested dependent attributes are supported (e.g. an option in A enables B and an option in B enables C)
  • Compatible with the uc_node_checkout and uc_aac modules (after patches - see #1425238: Compatibility with uc_aac module)

Drush Puppet Module

Component type

module

Maintenance status

Development status

Component created

Component changed

A Puppet module for Drush.

This Puppet module handles installing Drush, both from packages and from source using Git and Composer. It also defines a flexible drush::run resource that can be used to intelligently run any Drush command from Puppet. Building on this, it provides some common commands, such as 'dl', 'en' and 'make'.

Domain 301 Redirect

Component type

module

Categories

Maintenance status

Development status

Downloads

24391

Component created

Component changed

The Domain 301 Redirect module allows sites to 301 redirect to a domain that is marked as the main domain. This means you can have all subdomains and other domains pointing to the site 301 redirect to a domain that you choose as the main domain. This provides great SEO benefit.

Examples:

With the main domain set as http://www.example.com the following redirections
would take place:

Comment goodness

Component type

module

Maintenance status

Development status

Downloads

24150

Component created

Component changed

Provides comment sorting, comment form placement and comment form configuration settings.

Drupal 7.x does not support newest-to-oldest comment sorting. This module addresses this gap in functionality and provides content-type level configuration for comment sorting.

Entityform

Component type

module

Categories

Maintenance status

Development status

Downloads

189959

Component created

Component changed

Drupal 8

For Drupal 8 Entityform is now EForm

Overview

The Entityform module enables you to create front-end forms (fieldable entities), which contain fields that you define! These forms use the standard Drupal fields. This means that out of the box, you can use any standard Drupal node field! As of the time this article was written, there were over three hundred "field" modules. And since Entityforms are "Drupal entities", you will automatically be able to use future "field" modules!

The forms can be used to create custom surveys, petition, and personalized contact forms, and other customized form. (For those of you who have used Webforms, this module brings Webform's functionality into the "standard" Drupal field / entity world.)

As with everything in Drupal, there are Pros and Cons to using Entityform. All though Entityform is a powerful tool, it is not always the best solution. The article When to Use Entityform discusses the advantages and disadvantages that Entityform may have over other methods of creating user "submittable" forms. Do not use Entityform for forms that will contain 150+ form elements

Reccomended Versions

The Drupal 8 verision of Entityform has been renamed to EForm(to avoid name confusion).

For new users the 7. x-2. x alpha versions are recommended. These versions are also recommended for current 7.x-1.x users who are NOT using built in Rules integration. The only remaining issues with them is upgrading 7.x-1.x Rules integrations to use Entity Rules.

The Problem

While Webform is a great module with a huge following, it does not integrate with standard Drupal field or entity aware modules. And while Webform can be integrated into Rules and Views via additional modules, it does add complexity and overhead.

The Solution

To solve these issues, the Entityform module was created. It is a survey creation tool that allows integrates with standard Drupal field and entity aware modules out of the box.

Features

  • Ability to attach any Drupal Field to the Forms
  • Ability to use most field based and entity aware modules.
  • You can download submitted data to XML and / or CSV data files using View Data Export.
  • Rules based form submission notifications. Allows for complex notifications logic.
  • Rules based form access control. Allows for complex access logic.
  • Use Views to create to create an administrative listing of each Entityform type Submissions for fine grain control.