#security Scripts

A plugin developer that wants to support this convention needs to makes 3 changes to their plugins. Important note: plugins with the suggested changes will run exactly as before on servers that do not choose to install the change to getList.

Let's suppose that you wanted to modify a plugin called myplugin to work in this way. I'm assuming that you have named your table of scripts for this plugin myPluginSuite, if not change names in what follows appropriately. You would have to

• add a script called myPluginSuite.isVisible

  on isVisible (adrSite) {
     //return defined(config.manilaPlugins.myPlugin.[manilaSuite.getCanonicalSitename(adrSite)])    
     //bypass kernel bug  02/05/13, 13:50:36 by DAB
     local (nme = manilaSuite.getCanonicalSitename(adrSite))
     return defined(config.manilaPlugins.myPlugin.[nme]) 

• add a string #security to your initialConfig table, with a value of myPluginSuite.isVisible.
• To ensure that servers with myPlugin already installed get the benefits of this change, you need to make sure that the initialconfig - which Manila copies only the first time the install script is run - is modified so that it contains a #security value. I do this in the install scripts of my plugins, you can take a look at manilaFixer for an example.

There are four examples in bayly.root that use this convention - commentIt, manilaFixer, hierMenus and navigatorTicker.