[
https://issues.apache.org/jira/browse/OFBIZ-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240555#comment-17240555 ]
ASF subversion and git services commented on OFBIZ-12075:
---------------------------------------------------------
Commit 310764f82a918c308d861bd6cce6cb6be4518038 in ofbiz-framework's branch refs/heads/release18.12 from Nicolas Malin
[
https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=310764f ]
Fixed: Create a blog article failed to link each contents
(OFBIZ-12075)
When you create a blog article with screen
https://localhost:8443/content/control/EditBlogArticle?blogContentId=${blogId} by default you can create an article with a summary, an image and a long text.
After the creation all content related to this article was created by impossible to display this article correctly. The problem come from the contentAssoc of each relation where the mapKey isn't populate.
The root come from the conversion to entity-auto for the service createContent, where some seca are present and use some field to create some relation with attribute not present on a content (like the field mapKey)
To correct this I the simple way is to authorize these fields, and think for the future how do better.
> Create a blog article failed to link each contents
> --------------------------------------------------
>
> Key: OFBIZ-12075
> URL:
https://issues.apache.org/jira/browse/OFBIZ-12075> Project: OFBiz
> Issue Type: Bug
> Components: content
> Affects Versions: 18.12.01, Trunk
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
> Priority: Minor
> Fix For: Release Branch 18.12, Upcoming Branch
>
> Attachments: OFBIZ-12075.patch
>
>
> When you create a blog article with screen
https://localhost:8443/content/control/EditBlogArticle?blogContentId=${blogId} by default you can create an article with a summary, an image and a long text.
> After the creation all content related to this article was created by impossible to display this article correctly. The problem come from the contentAssoc of each realtion where the mapKey isn't populate.
> The root come from the conversion to entity-auto for the service createContent, where some seca are present and use some field to create some relation with attribute not present on a content (like the field mapKey)
> To correct this I the simple way is to authorize these fields, and think for the futur how do better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
