General Considerations

WordPress version

The version of WordPress which this service uses is the latest stable version available from There may be a time lag of up to 48 hours between a new release of the software being made available and the new release being deployed on this service, but we endeavor to keep the version of the software current at all times.

If the theme or plugins you choose or develop depend on parts of the WordPress API which have been deprecated in the latest stable version, they may cease to operate correctly as these patches are applied.

Coding Standards

All Themes and Plugins used in sites to be deployed in this service must be tested prior to deployment to ensure that basic coding errors are not present in them. Basic coding errors would include the generation of any PHP Notices or Warnings as well as any Javascript errors (whether benign or not). Any code developed by external suppliers must be fully documented to a sufficient level to allow it to be understood and supported by others.

The WordPress Coding Standards should be followed in all custom development work:

Data Storage

Storing data, either in theme options or in plugins, should be carried out using WordPress API wherever possible (storing options in the options table, using the WordPress Settings API, or using the postmeta table for posts and pages, for instance).

If additional database tables are required by a plugin or theme, this guidance in the wordpress codex must be followed to allow for the correct application of any updates, and the correct function of any activation and deactivation routines. Deactivation of a plugin or theme which adds tables to the wordpress database should always result in the additional tables being dropped. Additional tables must also be prefixed correctly so they are specific to a site within a multisite network (and not global for the whole network).