[
https://issues.apache.org/jira/browse/OFBIZ-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283417#comment-17283417
]
Michael Brohl commented on OFBIZ-10476:
---------------------------------------
I had to rework the patch. There were changes in forms which should not be made
(parent content), probably because of a misleading uiLabel. The uiLabel was
renamed and the parent content Id fields were not removed in the forms.
The changes are now in a pull request linked to this issue. I'd appreciate if
someone could test if everything works as expected in the content component
after the changes are applied. Thanks!
> Remove Compdoc functionality from content manager
> -------------------------------------------------
>
> Key: OFBIZ-10476
> URL: https://issues.apache.org/jira/browse/OFBIZ-10476
> Project: OFBiz
> Issue Type: Improvement
> Components: content
> Affects Versions: Release Branch 18.12, Trunk
> Reporter: Dennis Balkir
> Assignee: Michael Brohl
> Priority: Major
>
> While creating a theme and looking for not correctly styled elements I came
> across "some" not functional links and buttons in Compdoc.
> This module seems not to be finished or working properly, because most of the
> times, the buttons inside the appbar produce errors or just empty pages.
> Even when searching for existing elements and then clicking on them to
> examine or edit them will mostly create an error (example: go to compdoc,
> search for template child, click edit on some random found element -> error).
> Sometimes the menu which is included inside the appbar, mostly the menu
> called "tree", need the contentId for the buttons to work.
> Including this menu while creating a new entry will result in every button
> not working and throwing an error, except the edit button, which will produce
> a completely empty page.
> Those things appear all over the module, trying some button or clicking some
> link resulted in an error screen more than it resulted in something actually
> working.
> This should either be fixed or removed, if this doesn't has a real purpose at
> all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
