3,035
edits
Changes
→Blocklist syntax
* All versions of the <tt>item_4@domain</tt> Extension Manager item will be blocklisted if the current application version is between <tt>1.5</tt> and <tt>1.5.*</tt> (e.g. less than <tt>1.6</tt>).
* All versions of the <tt>item_5@domain</tt> Extension Manager item will be blocklisted for all versions of the current application.
* <tt>pluginItem</tt> is a blocklist entry for plugins, that do not have UUIDs that can be blocklisted. Since they do not have unique identifiers, they must be blocklisted with regular expressions used to pinpoint combinations of <tt>name</tt>, <tt>description</tt>, and <tt>filename</tt>. It makes the entry much simpler but a greedy regexp could spell doom for totally valid plugins so be careful, careful, careful. Keep in mind that plugin pluginItem entries don't have targetApplication ranges so you'll be blocklisting is application-agnostic matching plugins for uuid/version combinations as welldefined in the client URL.
As can be seen it is possible to blocklist all version of an extension for all versions of an application as well as any combination of application id's along with version ranges for both the extension id and application id. Also, by not specifying a value and instead using the default value it is possible to lessen the size of the blocklist xml file. This is possible by using the following defaults:
