This is similar to the simple content boxes provided by the Boxes module itself, except that this type of box displays different content depending on the language of the current page.

Development sponsored by Affinity Bridge

The review script at http://ventral.org/pareview/httpgitdrupalorgsandboxraphaelhuefner1748400git has the output of Drupal Code Sniffer:


FILE: .../all/modules/pareview_temp/test_candidate/plugins/simple_i18n_boxes.inc
--------------------------------------------------------------------------------
FOUND 5 ERROR(S) AND 1 WARNING(S) AFFECTING 5 LINE(S)
--------------------------------------------------------------------------------
11 | ERROR | Class name must begin with a capital letter
11 | ERROR | Class name must use UpperCamel naming without underscores
15 | ERROR | Public method name "simple_i18n_boxes::options_defaults" is not
| | in lowerCamel format, it must not contain underscores
31 | ERROR | Public method name "simple_i18n_boxes::options_form" is not in
| | lowerCamel format, it must not contain underscores
38 | WARNING | Line exceeds 80 characters; contains 92 characters
86 | ERROR | Public method name "simple_i18n_boxes::options_submit" is not

Route module enables the construction of wizard like journeys using Panels. It's mostly useful for developers that require high levels of configurability and flexibility for their multistep forms.

A Drupal 7 module that gives a user with permission a page [example.com/html-sample] for testing theme renders of elements common in most Drupal sites, including many basic drupal interface freatur

-- SUMMARY --

When logged in as a Drafter:
The user can create new articles, but the articles are put into an unpublished state.
When the unpublished node is saved, a new workflow node is created and can be accessed by clicking on the workflow tab where the edit tab used to be.
Drafters do not have access to the node edit pages on original nodes; only workflow nodes.
The drafter can then change the status of the workflow node (statuses include: draft, submitted, published).
Drafters can only change the status to submitted.
Upon saving the node with a submitted status, an email is sent to the approver and any updates are saved in the workflow log for the original node.
Existing nodes can begin the workflow process as well by clicking on the workflow tab and then clicking on a button "Begin Workflow".
Upon clicking "Begin Workflow" a new workflow node is created using the original nodes field contents.
The drafter can then make their changes, provide a note in the workflow log, and change the status to submitted.
When logged in as an Approver:
The approver has access to a workflow list (a list of nodes that are in workflow).
He/she can view the workflow node and proofread the content and change the status either to draft or published.
If they change it to draft, an email is generated to the editor along with any comments from the workflow log.

Remove "Promoted to Front Page" and "Sticky at top of lists" from node publishing options.

Wrap and style individual webform components. Allows an administrator to define available CSS classes for components, and then a webform content author can select from the list on an individual webform component.