Empower developers with tools that assist with developing and debugging the frontend or backend of the site.

Grammar Parser UI

This module provides a user interface to the Grammar Parser library. It allows you to specify individual source code files or entire directories of source code files to be parsed. In addition, source code may be entered directly in a text box. The output file options include the parser tokens, grammar structure, and the rewritten source file.

This module includes automated tests for itself as well as the Grammar Parser library.

The 7.x branch requires:

A Drush Make file is also included that will download the Grammar Parser Library dependency. (A Make file in the latter will download both the Libraries API and the Grammar Parser dependencies).

This project is sponsored by Boombatower Development.

Looking for 6.x support?

NodeBolt

nodebolt-icon.jpg

NodeBolt adds a simple layer of protection to remind admins / editors that for some reason, this node should be handled with a little more care when it comes to editing. For the node ids specified by the settings page, NodeBolt adds an extra step when editing.

WYSIWYG - GeSHi bridge

Important: Development of this module is halted until either:

  1. The WYSIWYG module no longer causes this major usability regression: #735624: Enabling one button removes default editor toolbar.
  2. Another WYSIWYG editor module provides an API that can be accessed by this module.

Please see comment #5 of #781846: Only for CKEeditor with WYSIWYG module? for more details. As of July 2011, neither standard has been met.

This module's intent is to allow users of the WYSIWYG module and the GeSHi Filter for syntax highlighting module to embed code through CKEditor without it being mangled. It is based on the original work of Peter Petrik.

Dependencies

GeSHi filter hack

You must hack a GeSHi filter file. I'm talking about the code you download separately form the Drupal GeSHi module.

Spanish LOPD

This module implements some aspects that helps your site to be compliant to the Spanish LOPD Law about personal data management.

File logger

File logger is a lightweight module that allows developers to configure a log file from within Drupal and dump variables to it from within a running Drupal app. Its primary function is to support debugging, and it avoids the awkwardness of dumping variables either to the console or to the watchdog table. Instead, using the unix tail command, a developer can easily view debugging output. This is particularly useful when dumping large data structures such as nodes, views, menus, etc.

Installation

  • Copy the module's directory to your modules directory and activate the module.
  • In Site configuration > File logging (admin/settings/flog on D6 or admin/config/development/flog on D7), specify the path
    to the log file(s) and the default log file name.
  • (Optionally) Configure the date string to be included with each logged variable.
  • Ensure that the user running the webserver has write permission on the file you specify.
    It may be simpler to create that file in advance using the unix command 'touch' as in
    'touch /var/log/drupal.log'. Then, set the permissions on the log file so it is writeable
    by the web server user, e.g. 'chmod 777 /var/log/drupal.log'.
  • Enable file logging. When disabled, no output is written. You'll probably want to disable
    file logging in a production environment.

Variable API

This module extends the Drupal core variable API that handles persistent variables. It implements a class that:

Just took over the module. Will be making stable releases for Drupal 7 and will support Drupal 6 for major issues.

  • allows finding the directory where a library has been installed (branch 2.x for Drupal 6 and 7),
  • forces Drupal to re-build the menus (branch 2.x for Drupal 6 and 7),
  • allows obtaining the value of a persistent variable without passing the default value to each function call,
  • deletes multiple persistent variables,
  • and implements functions to centralize static PHP variables. The functions are a back port of drupal_static(), and drupal_static_reset() implemented in Drupal 7.

Installation notes

Install the module only if you are instructed to do so, or you are a developer and want to use the module.

If you are installing Variable API because it is a dependency of another module, you need to first install (and enable) Variable API, and then install (and enable) the other module. If the modules are enabled at the same time, you will get the error message class Vars not found. The same problem is actually present if you install a module that depends from the Variable API using Drush; in the moment I am writing this note, Drush will not download the Variable API module, with the consequence that you will get the error message class Vars not found.

Pages

Subscribe with RSS Subscribe to RSS - Developer tools