EMS Booking
Component type
Maintenance status
Development status
Component created
Component changed
Feature module that creates the EMS Booking content type and corresponding taxonomy. This module requires the EMS API module.
Feature module that creates the EMS Booking content type and corresponding taxonomy. This module requires the EMS API module.
This module provides an ability to use Bootstrap tooltip as a glossary term pop-up tips.
Here are some quick instructions how to use it:
Provides a filter that matches taxonomy terms from any taxonomies present on a node
-- SUMMARY --
Entity Delete module is for deleting content of any entity types in bulk.
-- INSTALLATION --
STEP 1: Download and extract module to /module directory (/module/contrib if
using separate for custom and contrib).
STEP 2: For enabling navigate to /admin/modules and select 'Entity Delete'
and click on install.
--WORKING --
For deleting content in a bulk need to navigate to
admin/config/entity-delete
Select the Entity type for which you need to delete all available content.
Provides a Taxonomy Vocabulary condition for block visibility.
This condition can be used when configuring visibility rules for blocks on the Blocks Layout page, or when configuring conditions with the Context module.
We have a contextual filter from core "Content:Has taxonomy term Id with Depth".
Looking for a way to filter a view with taxonomy term name ? This module, on installation adds a contextual Filter plugin that allows a view to be filtered based on the taxonomy term name.
This module provides a Tag Cloud based searching of content.
Term content is a simple administration UI to manage (sort/filter) Taxonomy term's content
Why Term Content ?
There is no any way to customize the term content's order in drupal, most of the times we are using nodequeue module to order the nodes. It is very hard to manage the content in both nodequeue and taxonomy, This module might solve the problem. we can easily customize the node's order based on the terms and also we could list the nodes in views based on the custom orders.
For more details Check README.txt file.
Generally when we are using i18n module for translation then we always want to associate every content with some language. If you notice while adding/editing any node or term by default Language Neutral option appears in Language dropdown.