configuration

If you want to configure who can administer asset, create new asset types and etc, you should configure permissions. Permissions are applied to Roles. If you aren't already familiar with Drupal's Role based permissions, please read Users, roles and permissions.

Asset module provides following permissions:

• Administer asset types (Create, edit and delete types of assets)
• Administer assets (Create, edit and delete asset entities)
• Access the assets overview page
• Access assets search widget (available only when asset widget module enabled)

Besides that Asset API uses 3 types of permission for each asset type:

1. Create asset
2. Edit asset
3. Delete asset

You can assign permissions to roles on permissions page (People > Permissions > Roles):

As a result, when user tries to do some action (for example, delete asset with certain type) which isn't allowed to his role, he will see Access denied (error 403) page:

Asset widget module is included into Asset module package and is aimed to simplify Asset contribution and management.

All you need is to enable "Asset widget" module.

Module supported seven and rubik theme. Widget is not intended to work in front theme.

Widget will appear on content create/edit page if you have an appropriate permission and one of two next cases are true:

• Entity (node, taxonomy, etc) create/edit form contains Entity reference field with "Media Asset" target type and is set to autocomplete.
• Entity create/edit form contains CKEditor with enabled asset plugin for at least one of the input formats.

The detailed contributor instructions are available here.

Currently module fully supports integration only with CKEditor (v3). Next roadmap steps will be performed around integration with in-place editing option (Edit module) in terms of Spark project.

Evaluation of integration with TinyMCE and Aloha editor is in progress, feel free to request this integration in Issue tracker or post you code snippets that would introduce this integration.

Configure CKEditor

Follow instruction provided here to install and configure CKEditor module.

As soon as configuration was accomplished, navigate to Administration > Configuration > Content authoring > CKEditor and for each Profile, that should support Asset input (for example, Full and Advanced), in Editor appearance configuration activate Asset plugin and appropriate buttons.

By default set of Asset plugin buttons includes:

• one button per activated Asset type
• button to access Search interface

The Filter core module allows you to configure formats for text input for your site (read more about Text formats and Filters).
"Convert asset tags to markup" filter should be activated to allow Asset's markup being rendered correctly in WYSIWYG and on front-end.

Navigate to Administration > Configuration > Content authoring > Text formats and for each text format that should support Asset input (for example, Full HTML and Filtered HTML) activate "Convert asset tags to markup" filter.

In the Filter processing order group, you need to ensure the correct processing order. Normally, Asset module should proceed with conversion of the markup after the Limit allowed HTML tags filter. So the simplest configuration looks like this:

Asset module installation

The Asset module can be downloaded and installed via the standard Drupal installation process.

The Asset module activated itself provides an API for Media Asset entities creation. Submodules can be enabled to receive additional features:

• Predefined Asset types:
  • Image: asset_image
  • Image: asset_image
  • Video: asset_video
  • Audio: asset_audio
  • Document: asset_document
  • Gallery: asset_gallery
  • Free HTML: asset_freehtml
• Advanced UI and contribution

  widget: asset_widget

• Feeds integration: asset_feeds

Requirements

Contributed modules:

• Entity API

Predefined asset type submodules require:

• asset_image depends on Drupal core Image module.
• asset_audio requires jPlayer.
• asset_video requires Emvideo module, which is submodule of asset project. Any of emvideo providers submodules should be enabled

Follow our step by step installation guide to enable / configure and profit from the module and related functionalities.