[
https://issues.apache.org/jira/browse/OFBIZ-12233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346037#comment-17346037
]
ASF subversion and git services commented on OFBIZ-12233:
---------------------------------------------------------
Commit fb0701b7bdf0e5c0e75f51237e2ee85689413b51 in ofbiz-framework's branch
refs/heads/trunk from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=fb0701b ]
Fixed: Plugin not showing in menu due to permission (OFBIZ-12233)
When creating a plugin via gradle :
./gradlew createPlugin -PpluginId=plugin-test -PpluginResourceName=PluginTest
-PwebappName=plugin-test -PbasePermission=PLUGIN_TEST
and loading all the required data and permissions, the plugin doesn't appear
in the menu.
It comes from the ComponentConfig.java file, L1229, when the permissions gets
trimmed and modified. I tried removing it locally and it fixed the problem.
Thanks: Gaetan Chaboussie
> Plugin not showing in menu due to permission
> ---------------------------------------------
>
> Key: OFBIZ-12233
> URL: https://issues.apache.org/jira/browse/OFBIZ-12233
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Release Branch 18.12, Release Branch 17.12, Upcoming
> Branch
> Environment: openjdk 11.0.11 2021-04-20
> OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)
> OpenJDK 64-Bit Server VM (build 11.0.11+9-Ubuntu-0ubuntu2.20.04, mixed mode,
> sharing)
> Ubuntu 20.04.2 LTS
> Reporter: Gaetan Chaboussie
> Priority: Minor
> Attachments: OFBIZ-12233.patch
>
>
> When creating a plugin via gradle :
> {code}
> ./gradlew createPlugin -PpluginId=plugin-test -PpluginResourceName=PluginTest
> -PwebappName=plugin-test -PbasePermission=PLUGIN_TEST
> {code}
> and loading all the required data and permissions, the plugin doesn"t appear
> in the menu.
> I think it comes from the ComponentConfig.java file, L1229, when the
> permissions gets trimmed and modified. Are those lines still useful ?
> I tried removing it locally and it fixed the problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
