Changes between Version 1 and Version 2 of Ticket #465, comment 2
- Timestamp:
- 27.05.2013 01:11:17 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #465, comment 2
v1 v2 1 1 Yes, I can reproduce the problem you described with a 4.1 binary distribution and your Twitter plugin. 2 2 3 Indeed, when the plugin is installed on an existing DM installation the plugin's types do not appear in the Create menu. This is due to missing Access Control information. This in turn is due to the type instruction mechanism (IntroduceTopicTypeListener) as utilized by the Access Control plugin. The plugin activation order matters.3 Indeed, when the plugin is installed subsequently on an existing DM installation the plugin's types do not appear in the Create menu. This is due to missing Access Control information. This in turn is due to the type instruction mechanism (IntroduceTopicTypeListener) as utilized by the Access Control plugin. The finding is: the plugin activation order matters. 4 4 5 5 To solve the problem the installation of the Twitter plugin must wait for the Access Control plugin to be ready. Otherwise your plugin's types get no Access Control information assigned. … … 14 14 page. You could add this ticket's issue there. 15 15 16 Bottom line: when your plugin provides its own types you should add `de.deepamehta.accesscontrol` to your `importModels` plugin property. Otherwise your types could lack access information. As a consequence types supposed to appear in the Create menu will not do so. This is particularly an issue when the plugin is installed subsequently on an existing DM installation.16 Bottom line: when your plugin provides its own types you should add `de.deepamehta.accesscontrol` to your `importModels` plugin property. Otherwise your types could lack access control information. As a consequence types supposed to appear in the Create menu will not do so. This is particularly an issue when the plugin is installed subsequently on an existing DM installation. 17 17 18 18 Thank you very much, Malte, for reporting this crucial issue!
