Mobile Admin
Component type
Categories
Maintenance status
Development status
Component created
Component changed
A series of tweaks to make Drupal admin work on a mobile device
A series of tweaks to make Drupal admin work on a mobile device
This module records the node access history. Unlike {history} table in core which only stores the last viewing history of a node for each user. It stores all viewing history. It's useful for counting the hits of nodes in a certain period rather than a simple total count in the {node_counter} table of core. We can also find access history in {accesslog}, but we need to extract node ID in URL and it's much slower.
The module allows site admins to schedule most ctools exportable objects to either be enabled or disabled.
Dates can be entered as plain text or by using the date popup module that comes with date.
Please make certain cron is running correctly otherwise exportable items will not be scheduled correctly.
Build useful help for your users.
The Helpful module adds an additional layer to the Advanced Help module. The purpose of Helpful is to enable site developers to build a help system for their users, without giving them access to the entire advanced help system.
This module fixes an Admin menu css issue with the top bar in chrome (that have been bugging me for a really long time). I will post before and after screen shots soon.
This module creates a token "[user-logged-in]", which has the value "Yes" or "No". It can be used together with the Google Analytics module to track the number of logged in users. Which is done by using the token as a custom variable at session level in Google Analytics.
Servicelog is going to be a drop in amendment to or replacement of the core logging modules Database Logging (dblog) and Syslog (syslog) to integrate respective third-party offerings from Logging as a Service (LaaS) providers (e.g. Loggly, Papertrail).
Add parent role to users having a subrole
Context Export builds on the Context module to provide simplified exports. Contexts can be exported automatically (or manually via a single link at /admin/structure/context) and provided as "default" contexts, which makes Context changes easily transferrable between development environments via a version control system.
This module will provide context conditions to test and see if the current node belongs to a chosen nodequeue. Condition will return true if the current page is a node and if the node belongs to the specified nodequeue. Condition will return false if the page is not a node or if the node does not belong to the specified queue.