Add a new plugin in only one NRO site

If you are considering installing a 3rdparty plugin on your NRO website, first read our relevant guide around Plugins, especially the part about the Security review. Please get in touch with the Planet 4 team, as we can help with the process.


If you are adding a plugin you developed then make sure you have read our guide on how to add it to Packagist.

pagePackage Registry

The most important requirement in order to install a new plugin in your website is to assess that you have the development capacity to maintain it (monitoring future releases, doing security upgrades, fixing conflicts with planet 4, etc).


To add a plugin for only one NRO website, you need to do the following steps:

  1. Have access to that nro site controlling repository (eg. GP Netherlands)

  2. On the main branch, on the file composer-local.json, in the require block, add a line that will reference your plugin from packagist (for own developed plugins) or wpackagist (for 3rd party wordpress plugins).

  3. For own developed plugins, please note that the version can be one of the following:

    1. A tagged release (for example: v1.0). Mandatory for production releases.

    2. A branch name.

    3. Commit. This will trigger your development site to be rebuild including the new plugin.

Packagist prepends the string dev- before the branch name. So, if your branch name is my-nice-feature, in composer you have to reference it as dev-my-nice-feature. This is only possible on develop and release sites, not on production sites.

Last updated