Extend and customize Drupal functionality with contributed modules. If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
This module is just a formatter (display) of textfield, text area and text format. The idea behind this is to provide a simple solution, easy to setup, with few dependencies to display text on website.
The trim function in this module is taken from Views module with a few modifications.
- Text (Drupal 7.x Core)
- Filter (Drupal 7.x Core)
Download the module and simply copy it into your contributed modules folder:
This module allows you to configure a menu management, publishing for the client or the publisher.
With this menu you can select the pages or page types that they can view or edit in a dashboard are custom shaped menu accesible by the customer no matter the place where it is located.
Adds a visibility setting to blocks, allowing to show or hide blocks based on the users user agent string.
Examples of use:
- Hide some blocks for IE6 but show others
- Show or hide blocks for Linux or Windows users
- Show or hide blocks for Windows XP
This module will allow you change the view mode of an entity via Context module. A reaction will also be available.
This module allows site administrators to override the Field Label on any field in the Manage Display settings page. This allows each field to have a different title in different view modes.
The field formatter label settings are found in the Manage display tab for content types, users, and other entities. A text box is available for each field's label, revealed by using the formatter settings edit button (Gear wheel icon) for that field. If no 'Label override' is specified then the default will be used.
- Field formatter settings: Provides the low-level API needed to alter formatter's settings forms.
This module is almost identical to the Field Display Label module, the sole difference being that the label can be overridden in the Manage Display UI (rather than on the field configuration screen).
This module should work just fine with the Field Display Label module in the way you expect. If it is enabled the following logic dictates what a field's label will be:
1. Use the Field Formatter Label override, if it is not specified then:
2. Use the Field Display Label override, if it is not specified then:
3. Use the Field label (as per Drupal core behaviour).
The Node Asset module provides the ability to add nodes of specified content types as assets to the body of another node. I am following the model of the Asset module but engineering it to use nodes instead of Media Asset entities. This will allow assets to stand alone and be embeded in the body of another node.
This module is currently in the early stages of development so there is no code available at this time.
This module provides a common space for managing commonly used site details, including the core Drupal site settings. It also provides a handful of blocks for simple display of site information.
This module allows customization of displayed field labels, including its HTML element and CSS classes.
The Link Widget module provides an elegant way for wrapping an link around a "image" or "text" field type output. This module is dependent upon the Field Widget Storage API, which provides a solution for saving extra widget configurations alongside a field.
What are the differences between Link Widget and related link modules?
The biggest difference is based on the modules architect; instead of creating another field type, I just created a field widget that extends the field configurations. You can make either an image or text field type linkable. This concept can be extended and can accommodate for other field types in future releases.
What are the advantages of the Link Widget module?
There are a couple advantages of the Link Widget module. First and foremost, there is less code to maintain. As I'm only defining a field widget, and don't have to worry about recreating the field component. Second, the Link Widget is flexible and making a text or image field linkable, is super easy and can be done by just selecting a field widget type "Link".
This module will add a jQuery slider to the page allowing end users to adjust the size of the type on the page. It can add the slider to the $node->content render array and also provides a ctools plugin for placement in panels.
Simple module for disabling add comment links.
In some case the primary menu want more than
- element. This module helped developer can customize display of sub-menu item, by using Views module to customize output of display, so you can easily style the element and also fully integrate with drupal's menu system.
*Use with Bootstrap: http://drupal.org/project/bootstrap
Provides a url-based tab solution.
Go to admin/structure/types, and click the "tabs" link for your content type.
You will then be able to add the desired tabs.
Each tab has a weight, and the listing is sorted by weight.
The tab with the smallest weight is taken as the default.
Tabs are exportable, and have a machine name (used in the url) and a translatable
label (shown in the tab itself).
You need to have the i18n_string module (part of the Internationalization module)
to be able to translate the labels.
The module is meant to be used with Panels.
Ideally, there would be a Panels page added to node/%node/%node_tab
with two contexts, Node: ID and Node Tab: Name attached to the arguments.
Each variant would then have appropriate selection rules, for instance,
Node: type - "page" and Node Tab: Tab Name - "overview" (or some other tab machine name).
A panels content_type provides a listing of blocks.
Note that if a node type has tabs, and a node of that type has an alias,
an additional alias will be created per tab.
So if you have tabs "Overview", "Documentation" and "Pricing", and a node
with the alias "my-product", the module will create:
my-product/overview, my-product/documentation and my-product/pricing.
This won't be done retroactively for existing nodes, you will need
This module supports the easy created of pages with content organized into vertical and horizontal tabs.
The module provides a pop-up announcement in the pretty colorbox overlay which will appear for the site visitor on the first, second and fifth visit to the site (customable).
If interval between http requests is more than one hour, these are two different visits.
The anoouncement may be with html.
The announcement will appear on the colorbox overlay.
On the configure page it is possible to define, on which visit the announcement will appear. By default on the first, second and fifth visit.
After 90 days records about visits become old and automatically are removed from the database.
Add button to erase all records about users - it will be useful if text of the announcemnt is changed and we need to show it for all users (even for those who have already seen it).
Add field on the configure page to define the time after which records about visits will be deleted.
Add field on the configure page to define the time after which next http request will be considered as a new visit.
This module sets out to provide a solution to complex date sorting of content that cannot be achieved with Views without query modification. It presents content, displayed in a sorted order based on date fields and their relationship to now.
For example, you may have two content types that you would like to display in the same content feed: News and Events. News has a date field called 'Publication Date' and Events have a date field called 'Start Date'. The problem is that Publication Dates are dates that have passed, whereas start dates have not yet arrived. By allowing you to choose the sort order of these fields at the content type level, we can create a feed of this content that logically sorts itself and presents the most Current content amongst the sorted content types.
Yandex.XML is a service that lets you send queries to the Yandex search engine and get responses in XML format.
To set up and start using Yandex.XML in Drupal site, follow these steps:
- Ensure your site is indexed by Yandex search engine
- Familiarize yourself with license agreements
- Register the IP address that you plan to send search requests from
- Install the module as usual
- Navigate to Administration » Configuration » Search and metadata » Yandex XML settings and setup service authorization
- Open yandex/search page and make sure that the search works well
Many comercial websites who sell age restricted content are required by local laws to display an "age-gate" before content can be displayed. This modules does just that. This is mostly needed by websites who's content promotes alcohol, drugs, gambling, adult content, etc.
When a user arrives at any page of the site, this module displays an HTML overly if a cookie is not present stating that they are of age.
Like a slideshow, except it takes over the entire page and the user scrolls down to advance to the next slide.
This module can display random rows through JS. It allows to display content through cache.
- Unformatted list
- Install this module
- Select '(JS Random)' style format
- Pager: 'Display all items'
Simple module to display revision notes at the top of the screen for content authors.
Swiper - is the free and ultra lightweight mobile touch slider with hardware accelerated transitions (where supported) and amazing native behavior. It is intended to use in mobile websites, mobile web apps, and mobile native apps. Designed mostly for iOS, but also works great on Android, Windows Phone 8 and modern Desktop browsers. Swiper plugin is created by iDangero.us
This project has been sponsored by:
At Ci&T, we range from building a private set of applications to engineering an entire IT portfolio. Services include the entire application development cycle, including service and project management, business analysis, defining requirements, design, code, testing, implementation and support.
Creates a Leaflet GeoJSON formatter for a (long) text field.
This project aims to improve development and long term maintenance of sites by providing an easy to use administrative section for displaying rendered entities by bundle, by view mode.
When working on large, complicated sites, it is common to create multiple view modes for entities. This problem is exacerbated since there is no simple way to view the final rendering of these view modes without creating some sort of display, or finding some sort of display on your site already rendering the view mode.
Layering Panels, Panelizer, and other rendering systems on top of the core entity rendering system makes viewing final rendered output extremely difficult.
This module provides an easy way to display view modes for entities in an admin area, suggestions and patches for its improvement are gladly welcomed.
Install the module and dependencies.
Enable the Access view mode displays permission from the permissions page for your role. Warning, give this permission to top level administrators only, as entity access permissions are bypassed.
Visit admin/structure/view-mode-displays on your site, accessible through Administration -> Structure -> View mode displays.
Click links to display rendering of entities by view mode.