Development tools for SilverStripe

Installs: 1 996

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 3

Forks: 0



2.0.0 2018-01-12 02:22 UTC

This package is not auto-updated.

Last update: 2024-05-11 20:59:30 UTC


Adds additional functionality to assist in developing SilverStripe websites.


  • SilverStripe 3.1+
  • Betterbuttons


  • Performance of page loads
  • Visualisation of current site state (DEV/TEST/LIVE)
  • Admins can emulate any other user
  • IconSelectField to use icon libraries within the CMS
  • Automatic redirection from development domains, when in LIVE mode
  • LogJam logging to append system error log
  • BugHerd integration


  1. Add to your composer requirements composer require jaedb/dev-tools
  2. Edit your theme's templates/ template and add $DebugTools immediately before the </body> tag
  3. Run /dev/build?flush=1
  4. Toggle debug tools by turning your site to DEV or TEST modes (disabled on LIVE sites for obvious reasons)
  5. Set the site's BugHerd project key in config.yml. See config/dev-tools.yml for an example.


Primary domain redirection

When you set your SS_PRIMARY_DOMAIN property on a live website, we automatically redirect to this primary domain. This avoids the need for bloated .htaccess redirections and allows control at the environment level.

Debug Tools

Debug tools

  • Manage the visibility of the Debug Tools from within the CMS, under Settings
  • Manage ability to Emulate users, also under Settings



  • Set your $db field to type Icon (eg 'PageIcon' => 'Icon')
  • IconSelectField::create($name, $title, $iconFolder)
  • $name is the database field as defined in your class
  • $title is the label for this field
  • $iconFolder (optional) defines the directory where your icons can be found. Defaults to /site/icons.
  • Use your icon in templates as you would any other property (eg $PageIcon). If your icon is an SVG, the SVG image data will be injected into the template. To prevent this, you can call $PageIcon.IMG instead to enforce use of <img> tags.


  • LogJam::Log($message, $environment)
  • $message a string that you'd like to log
  • $environment (optional) the type of environment that should log this message (ie test, dev, live). Defaults to dev.
  1. Enable LogJam in _config.php by adding LogJam::EnableLog();
  2. Check your log file location. Set this in _ss_environment.php with the following: