[jira] [Commented] (OFBIZ-12328) Some online help links don't get where they should
[ https://issues.apache.org/jira/browse/OFBIZ-12328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17421616#comment-17421616 ] Olivier Heintz commented on OFBIZ-12328: I have made the corrections for content link and change the link for accounting AR & AP to go to accounting glossary. Now I will do # a short file for "No existing documentation for this component" # include the file at the end of plugin-user-manual # change the link for all plugin without doc # Create a workeffort.adoc (with just an overview) # change the link for workeffort > Some online help links don't get where they should > -- > > Key: OFBIZ-12328 > URL: https://issues.apache.org/jira/browse/OFBIZ-12328 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > Here is a list where the results are wrong. It's only from applications main > pages. > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_content_management_overview > https://demo-trunk.ofbiz.apache.org/ismgr/control/main > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins > https://demo-trunk.ofbiz.apache.org/ar > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_accounting > https://demo-trunk.ofbiz.apache.org/ap > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_accounting > These should better go to > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_accounting_glossary > https://demo-trunk.ofbiz.apache.org/firstdata > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html > https://demo-trunk.ofbiz.apache.org/webpos > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins > https://demo-trunk.ofbiz.apache.org/bi > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins > https://demo-trunk.ofbiz.apache.org/solr > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html > https://demo-trunk.ofbiz.apache.org/workeffort > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_core_business_applications > Should not get there > I tried from Catalog sub-pages. Only Image Management went where it's > expected. It's less important but still. Order seems better from this POV but > only when the help page is already opened. So a lot more to say but not much > time for that... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12328) Most online help links don't get where they should
[ https://issues.apache.org/jira/browse/OFBIZ-12328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17421195#comment-17421195 ] Olivier Heintz commented on OFBIZ-12328: is it possible to give me a detail process example, because all seem works for me, so, I'm clearly not understanding in which case link is not correct. When I go to Accounting AR main page and I click to help, Help page is open on Accounting chapter, like it's parametrized in screen helpAnchor field = "_accounting" (currently there is no accounting AR sub-chapter in help, so I have chosen the main accounting help page). > Most online help links don't get where they should > -- > > Key: OFBIZ-12328 > URL: https://issues.apache.org/jira/browse/OFBIZ-12328 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > > Here is a list where the results are wrong. It's only from applications main > pages. > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_content_management_overview > https://demo-trunk.ofbiz.apache.org/ismgr/control/main > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins > https://demo-trunk.ofbiz.apache.org/ar > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_accounting > https://demo-trunk.ofbiz.apache.org/ap > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_accounting > These should better go to > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_accounting_glossary > https://demo-trunk.ofbiz.apache.org/firstdata > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html > https://demo-trunk.ofbiz.apache.org/webpos > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins > https://demo-trunk.ofbiz.apache.org/bi > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins > https://demo-trunk.ofbiz.apache.org/solr > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html > https://demo-trunk.ofbiz.apache.org/ebay > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_ebay_appl_introduction > It exists but you don't get there at 1st time, weird > https://demo-trunk.ofbiz.apache.org/workeffort > https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_core_business_applications > Should not get there > I tried from Catalog sub-pages. Only Image Management went where it's > expected. It's less important but still. Order seems better from this POV but > only when the help page is already opened. So a lot more to say but not much > time for that... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-11810) Element link can update partial area
[
https://issues.apache.org/jira/browse/OFBIZ-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355673#comment-17355673
]
Olivier Heintz edited comment on OFBIZ-11810 at 6/2/21, 12:22 PM:
--
This commit generate a bug, currently I don't understand why, I'm just able to
describe it.
Description: RequestSubTabBar in OrderMenus.xml, => button "Create Quote >From
Request"
Button appear only for request with type "Request For Quote" in View Request
Before this patch, it works, now not
+Before, the generate link is+ :
javascript:document.RequestSubTabBar_createQuoteFromRequest_LF_7_.submit()
+After, the generate link is :+
javascript:ajaxSubmitFormUpdateAreas('RequestSubTabBar_createQuoteFromRequest_LF_6_',
'/ordermgr/control/createQuoteFromCustRequest?custRequestId=1')
was (Author: holivier):
This commit generate a bug, currently I don't understand why, I'm just able to
describe it.
Description: RequestSubTabBar in OrderMenus.xml, => button "Create Quote >From
Request"
Before this patch, it works, now not
+Before, the generate link is+ :
javascript:document.RequestSubTabBar_createQuoteFromRequest_LF_7_.submit()
+After, the generate link is :+
javascript:ajaxSubmitFormUpdateAreas('RequestSubTabBar_createQuoteFromRequest_LF_6_',
'/ordermgr/control/createQuoteFromCustRequest?custRequestId=1')
> Element link can update partial area
>
>
> Key: OFBIZ-11810
> URL: https://issues.apache.org/jira/browse/OFBIZ-11810
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework/widget
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Major
> Labels: screen, widget
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-11808-OFBIZ-11810.patch
>
>
> Currently when you want to display an information easily on sub-screen
> dynamically (example as related element) is currently not possible without
> write specific js code. A easy step would be add a new link type:
> update-area, to indicate to the theme that we want to refresh after the call
> only a local area.
> {code:xml}
> target-window="detail">
> from-field="productCategory.productCategoryId"/>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (OFBIZ-11810) Element link can update partial area
[
https://issues.apache.org/jira/browse/OFBIZ-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz reopened OFBIZ-11810:
> Element link can update partial area
>
>
> Key: OFBIZ-11810
> URL: https://issues.apache.org/jira/browse/OFBIZ-11810
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework/widget
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Major
> Labels: screen, widget
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-11808-OFBIZ-11810.patch
>
>
> Currently when you want to display an information easily on sub-screen
> dynamically (example as related element) is currently not possible without
> write specific js code. A easy step would be add a new link type:
> update-area, to indicate to the theme that we want to refresh after the call
> only a local area.
> {code:xml}
> target-window="detail">
> from-field="productCategory.productCategoryId"/>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11810) Element link can update partial area
[
https://issues.apache.org/jira/browse/OFBIZ-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355673#comment-17355673
]
Olivier Heintz commented on OFBIZ-11810:
This commit generate a bug, currently I don't understand why, I'm just able to
describe it.
Description: RequestSubTabBar in OrderMenus.xml, => button "Create Quote >From
Request"
Before this patch, it works, now not
+Before, the generate link is+ :
javascript:document.RequestSubTabBar_createQuoteFromRequest_LF_7_.submit()
+After, the generate link is :+
javascript:ajaxSubmitFormUpdateAreas('RequestSubTabBar_createQuoteFromRequest_LF_6_',
'/ordermgr/control/createQuoteFromCustRequest?custRequestId=1')
> Element link can update partial area
>
>
> Key: OFBIZ-11810
> URL: https://issues.apache.org/jira/browse/OFBIZ-11810
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework/widget
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Major
> Labels: screen, widget
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-11808-OFBIZ-11810.patch
>
>
> Currently when you want to display an information easily on sub-screen
> dynamically (example as related element) is currently not possible without
> write specific js code. A easy step would be add a new link type:
> update-area, to indicate to the theme that we want to refresh after the call
> only a local area.
> {code:xml}
> target-window="detail">
> from-field="productCategory.productCategoryId"/>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347040#comment-17347040 ] Olivier Heintz commented on OFBIZ-12224: Add Order-Request documentation, as there are no diagram, I have add a CustRequest data-model to have image too ;) [^D_OFBIZ-12224-Documented-Order-Request-online-Documentation.patch] [~jleroux] : Yes, I try to update ofbizextra site with the patch before loading it on Jira. It's my final control for screen help link. > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > C_OFBIZ-12224-Documented-Order-Return-online-Documentation.patch, > D_OFBIZ-12224-Documented-Order-Request-online-Documentation.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12224: --- Attachment: D_OFBIZ-12224-Documented-Order-Request-online-Documentation.patch > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > C_OFBIZ-12224-Documented-Order-Return-online-Documentation.patch, > D_OFBIZ-12224-Documented-Order-Request-online-Documentation.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12224: --- Attachment: C_OFBIZ-12224-Documented-Order-Return-online-Documentation.patch > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > C_OFBIZ-12224-Documented-Order-Return-online-Documentation.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343146#comment-17343146 ] Olivier Heintz commented on OFBIZ-12224: Add Order-Return diagram and doc [^C_OFBIZ-12224-Documented-Order-Return-online-Documentation.patch] > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > C_OFBIZ-12224-Documented-Order-Return-online-Documentation.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12224: --- Attachment: (was: OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch) > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > C_OFBIZ-12224-Documented-Order-Return-online-Documentation.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343144#comment-17343144 ] Olivier Heintz commented on OFBIZ-12224: Add payment term diagram and help about order-bill-setting, and order update diagrams in the patch [^B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch] > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12224: --- Attachment: B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > B_OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335207#comment-17335207 ] Olivier Heintz commented on OFBIZ-12224: Hi Jacques, Thanks for the remarks, Yes it's a completing/replacing patch, but I will do one patch per sub-component (even if there are multiple releases for each), first one is order, next will be quote. Last changes are link to between screen to help, so nothing visible on user-manual. I will test to update the ofbizextra ofbiz demo server to have help link to ofbizextra ofbiz-user-manual > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333283#comment-17333283 ] Olivier Heintz commented on OFBIZ-12224: First step is done, new patch contain link from order screen to UI-help [^OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch] ^will be committed next week^ > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12224: --- Attachment: OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch, > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12224) Order online Documentation and help
[ https://issues.apache.org/jira/browse/OFBIZ-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12224: --- Attachment: OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > Order online Documentation and help > --- > > Key: OFBIZ-12224 > URL: https://issues.apache.org/jira/browse/OFBIZ-12224 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk > Environment: All associated patch are on git-format-patch (apply it > with git am) > but to help review each patch is applied to ofbizextra environment and so is > directly readable at > https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Attachments: > OFBIZ-12224-Documented-Order-online-Documentation-and-help.patch > > > Use ofbiz wiki content to create asciidoc files in order components. > # Migrate > [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] > pages, that is use the content of screen explanation to create help for > order screen (without screen copy) > # migrate > [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] > pages, that is use the content to add overview or general process > explanation, with the activity diagram > # Add some link between general explanation to help screen > # update screen to add correct help link > Start with order entry process, and will iterate on same steps for other > order sub-components. > Order component documentation organization will evolve at each iteration or > when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12224) Order online Documentation and help
Olivier Heintz created OFBIZ-12224: -- Summary: Order online Documentation and help Key: OFBIZ-12224 URL: https://issues.apache.org/jira/browse/OFBIZ-12224 Project: OFBiz Issue Type: Sub-task Components: order Affects Versions: Trunk Environment: All associated patch are on git-format-patch (apply it with git am) but to help review each patch is applied to ofbizextra environment and so is directly readable at https://ofbizextra.org/ofbiz_adocs/docs/asciidoc/user-manual.html#_order Reporter: Olivier Heintz Assignee: Olivier Heintz Use ofbiz wiki content to create asciidoc files in order components. # Migrate [https://cwiki.apache.org/confluence/display/OFBENDUSER/Sales+Order+End-to-End+Process] pages, that is use the content of screen explanation to create help for order screen (without screen copy) # migrate [https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management+Process+Overview] pages, that is use the content to add overview or general process explanation, with the activity diagram # Add some link between general explanation to help screen # update screen to add correct help link Start with order entry process, and will iterate on same steps for other order sub-components. Order component documentation organization will evolve at each iteration or when there are too many items in a specifics level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-9599) Documentation: Sales Order Management Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-9599: -- Labels: BPRB Documentation Management OBPRB Order (was: BPRB Management OBPRB Order) > Documentation: Sales Order Management Process Overview > -- > > Key: OFBIZ-9599 > URL: https://issues.apache.org/jira/browse/OFBIZ-9599 > Project: OFBiz > Issue Type: Sub-task >Reporter: Shivangi Tanwar >Assignee: Shivangi Tanwar >Priority: Major > Labels: BPRB, Documentation, Management, OBPRB, Order > > Sales Order Management process overview to be documented. > *Doc Content* > Every Sales Order Management business activity to be covered with below-given > headings- > - Process Overview > - Business Purpose (significance of having efficient Sales Order Management > capabilities in real world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-9599) Documentation: Sales Order Management Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317239#comment-17317239 ] Olivier Heintz commented on OFBIZ-9599: --- In the global Documentation tasks, I have started to migrated what it is possible from OFbiz wiki to the asciidoc user documentation (beginning by the oldest pages). For Order Management, I start to migrate [Sales Orders end-to-end Process/3.1 Entry|https://cwiki.apache.org/confluence/display/OFBENDUSER/3.1+Order+Entry] but without screen copy, and with the idea to use it as order process sub-chapter (which will be done as a automatics UI test too). When I finish the first step (wiki content migration (and review) to asciidoc ) I will try to merge it with your Wiki document (the Order part) in the asciidoc file. I will ask you to do a review after that. > Documentation: Sales Order Management Process Overview > -- > > Key: OFBIZ-9599 > URL: https://issues.apache.org/jira/browse/OFBIZ-9599 > Project: OFBiz > Issue Type: Sub-task >Reporter: Shivangi Tanwar >Assignee: Shivangi Tanwar >Priority: Major > Labels: BPRB, Management, OBPRB, Order > > Sales Order Management process overview to be documented. > *Doc Content* > Every Sales Order Management business activity to be covered with below-given > headings- > - Process Overview > - Business Purpose (significance of having efficient Sales Order Management > capabilities in real world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12166) Default ordering of webapps titles in main menu
[ https://issues.apache.org/jira/browse/OFBIZ-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299661#comment-17299661 ] Olivier Heintz commented on OFBIZ-12166: in R18 the help files are not migrated to asciidoc, so not ;) > Default ordering of webapps titles in main menu > --- > > Key: OFBIZ-12166 > URL: https://issues.apache.org/jira/browse/OFBIZ-12166 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 18.12.01, Upcoming Branch > > > This follows https://markmail.org/message/ftgfpwztflty7klb, excerpt: > bq. [...] having more important apps in 1st places would be better [...] the > feature should be easily changed by custom projects [...] documentation for > that would be enough. > I propose this order: > 1. partymgr(because you need parties to do anything) > 2. catalog (because you need products to do anything) > 3. facility (because you need to store products to do anything) > 4. order (because it's there that things begin to "move") > 5. accounting (because it's there that things "end"; ar & ap should > disappear) > 6. content (because you need to associate contents to make things better) > 7. manufacturing (because OFBiz is also an ERP) > 8. sfa (because people are often looking for a CRM, BTW most them don't know > what SFA is) > 9. workeffort (this one could be above, but it's not obvious for most people) > 10. humanres (more important than below IMO) > 11. marketing (not sure about the place of this one) > 12. webtools (maybe higher?) > - (plugins start below) > 1. rest (could be named api soon) > 2. projectmgr > 3. webpos > 4. bi > 5. birt > 6. myportal > 7. assetmaint > 8. ismgr > 9. scrum > 10. solr > 11. ebay > 12. firstdata > 13. - (those are special, maybe above?) > 14. example > 15. exampleext > - (those plugins don't show atm but exist, maybe need more info > from backend menu?) > 1. ecommerce > 2. ecomseo > 3. multiflex > 4. cmssite > 5. ebaystore > 6. ldap > 7. lucene > 8. passport > 9. pricat > 10. msggateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12166) Default ordering of webapps titles in main menu
[ https://issues.apache.org/jira/browse/OFBIZ-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297938#comment-17297938 ] Olivier Heintz commented on OFBIZ-12166: I propose to put the help of the different components in the same order as the menus. Only change order of the include in the user-manual > Default ordering of webapps titles in main menu > --- > > Key: OFBIZ-12166 > URL: https://issues.apache.org/jira/browse/OFBIZ-12166 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 18.12.01, Upcoming Branch > > > This follows https://markmail.org/message/ftgfpwztflty7klb, excerpt: > bq. [...] having more important apps in 1st places would be better [...] the > feature should be easily changed by custom projects [...] documentation for > that would be enough. > I propose this order: > 1. partymgr(because you need parties to do anything) > 2. catalog (because you need products to do anything) > 3. facility (because you need to store products to do anything) > 4. order (because it's there that things begin to "move") > 5. accounting (because it's there that things "end"; ar & ap should > disappear) > 6. content (because you need to associate contents to make things better) > 7. manufacturing (because OFBiz is also an ERP) > 8. sfa (because people are often looking for a CRM, BTW most them don't know > what SFA is) > 9. workeffort (this one could be above, but it's not obvious for most people) > 10. humanres (more important than below IMO) > 11. marketing (not sure about the place of this one) > 12. webtools (maybe higher?) > - (plugins start below) > 1. rest (could be named api soon) > 2. projectmgr > 3. webpos > 4. bi > 5. birt > 6. myportal > 7. assetmaint > 8. ismgr > 9. scrum > 10. solr > 11. ebay > 12. firstdata > 13. - (those are special, maybe above?) > 14. example > 15. exampleext > - (those plugins don't show atm but exist, maybe need more info > from backend menu?) > 1. ecommerce > 2. ecomseo > 3. multiflex > 4. cmssite > 5. ebaystore > 6. ldap > 7. lucene > 8. passport > 9. pricat > 10. msggateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12030) Help system can be on user language (help using asciidoc files)
[ https://issues.apache.org/jira/browse/OFBIZ-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289773#comment-17289773 ] Olivier Heintz commented on OFBIZ-12030: Excuse me, I don't understand the question. About which Google group do you speak about ? > Help system can be on user language (help using asciidoc files) > --- > > Key: OFBIZ-12030 > URL: https://issues.apache.org/jira/browse/OFBIZ-12030 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Major > Labels: Documentation, asciidoc > > Previous help system, using docbook and content component was able to be on > multiple language. > The goal of this Jira is to propose a solution for the help system using > asciidoc files. > Currently there are not a lot of files which are not in English (less than > 10) but it's necessary to have a solution for users / customers which use > ofbiz documentation system as the internal process documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[ https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17283718#comment-17283718 ] Olivier Heintz commented on OFBIZ-12047: Why not, new patch, [^RequestHandler.java.patch] > Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages > --- > > Key: OFBIZ-12047 > URL: https://issues.apache.org/jira/browse/OFBIZ-12047 > Project: OFBiz > Issue Type: Bug > Components: framework/webapp >Affects Versions: Release Branch 18.12, Trunk >Reporter: Ingo Könemann >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 18.12.01, Upcoming Branch > > Attachments: RequestHandler.java.patch, RequestHandler.java.patch, > RequestHandler.java.patch > > > There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and > execute the previous request after a login occurs. This attribute is not > removed properly when navigating away from a page without logging in. > When navigating to a page that requires authentication the > "_PREVIOUS_REQUEST_" attribute is saved in the session from within the > LoginWorker to be called again when the login was successful through the > RequestHandler. Currently, the attribute is only removed when a login occurs > resulting in the previous request being stored in the session until some form > of login is successfully executed. > This behavior potentially results in navigation problems since a user is able > to navigate to a page requiring authentication without logging in. An old > request will be pulled from the session when a similar event occurs and the > user logs in. > > I propose to have the RequestHandler remove the session attribute > "_PREVIOUS_REQUEST_" after calling a request that does not require > authentication. We also have to restructure the sequence of request handling > to have the "targetRequestUri" handled after the security check and a > possible removal of the session attribute. > > One problem arises with this solution, however, which should be less of an > issue than the current state: > If the login page includes a request call that is handled after the request > showing the login page (for example an ajax call rendering a screen), the > "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To > my knowledge such a case does not exist within the OFBiz environment and > seems to be an edge case far less problematic than the above mentioned > problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[ https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12047: --- Attachment: RequestHandler.java.patch > Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages > --- > > Key: OFBIZ-12047 > URL: https://issues.apache.org/jira/browse/OFBIZ-12047 > Project: OFBiz > Issue Type: Bug > Components: framework/webapp >Affects Versions: Release Branch 18.12, Trunk >Reporter: Ingo Könemann >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 18.12.01, Upcoming Branch > > Attachments: RequestHandler.java.patch, RequestHandler.java.patch, > RequestHandler.java.patch > > > There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and > execute the previous request after a login occurs. This attribute is not > removed properly when navigating away from a page without logging in. > When navigating to a page that requires authentication the > "_PREVIOUS_REQUEST_" attribute is saved in the session from within the > LoginWorker to be called again when the login was successful through the > RequestHandler. Currently, the attribute is only removed when a login occurs > resulting in the previous request being stored in the session until some form > of login is successfully executed. > This behavior potentially results in navigation problems since a user is able > to navigate to a page requiring authentication without logging in. An old > request will be pulled from the session when a similar event occurs and the > user logs in. > > I propose to have the RequestHandler remove the session attribute > "_PREVIOUS_REQUEST_" after calling a request that does not require > authentication. We also have to restructure the sequence of request handling > to have the "targetRequestUri" handled after the security check and a > possible removal of the session attribute. > > One problem arises with this solution, however, which should be less of an > issue than the current state: > If the login page includes a request call that is handled after the request > showing the login page (for example an ajax call rendering a screen), the > "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To > my knowledge such a case does not exist within the OFBiz environment and > seems to be an edge case far less problematic than the above mentioned > problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[
https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17283636#comment-17283636
]
Olivier Heintz commented on OFBIZ-12047:
After a strange behavior in vueJs components I have checked a little more.
In my point of view (but clearly I have not an understanding of RequestHandler
and login java process) there are already a lot of hardcoded request name
("checkLogin" ,"ajaxCheckLogin", ...) and it's possible to test with
equals("login") not contain, it seems more secure.
If we want to manage all case, it will be necessary to add not
equals("SetTimeZoneFromBrowser") too but it's necessary in a very specifics
case, so I prefer to forget this case.
so in the new patch, the only modification is change from path.contain("login")
to requestUri.equal("login")
[^RequestHandler.java.patch]
> Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
> ---
>
> Key: OFBIZ-12047
> URL: https://issues.apache.org/jira/browse/OFBIZ-12047
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webapp
>Affects Versions: Release Branch 18.12, Trunk
>Reporter: Ingo Könemann
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 18.12.01, Upcoming Branch
>
> Attachments: RequestHandler.java.patch, RequestHandler.java.patch
>
>
> There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and
> execute the previous request after a login occurs. This attribute is not
> removed properly when navigating away from a page without logging in.
> When navigating to a page that requires authentication the
> "_PREVIOUS_REQUEST_" attribute is saved in the session from within the
> LoginWorker to be called again when the login was successful through the
> RequestHandler. Currently, the attribute is only removed when a login occurs
> resulting in the previous request being stored in the session until some form
> of login is successfully executed.
> This behavior potentially results in navigation problems since a user is able
> to navigate to a page requiring authentication without logging in. An old
> request will be pulled from the session when a similar event occurs and the
> user logs in.
>
> I propose to have the RequestHandler remove the session attribute
> "_PREVIOUS_REQUEST_" after calling a request that does not require
> authentication. We also have to restructure the sequence of request handling
> to have the "targetRequestUri" handled after the security check and a
> possible removal of the session attribute.
>
> One problem arises with this solution, however, which should be less of an
> issue than the current state:
> If the login page includes a request call that is handled after the request
> showing the login page (for example an ajax call rendering a screen), the
> "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To
> my knowledge such a case does not exist within the OFBiz environment and
> seems to be an edge case far less problematic than the above mentioned
> problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[ https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12047: --- Attachment: RequestHandler.java.patch > Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages > --- > > Key: OFBIZ-12047 > URL: https://issues.apache.org/jira/browse/OFBIZ-12047 > Project: OFBiz > Issue Type: Bug > Components: framework/webapp >Affects Versions: Release Branch 18.12, Trunk >Reporter: Ingo Könemann >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 18.12.01, Upcoming Branch > > Attachments: RequestHandler.java.patch, RequestHandler.java.patch > > > There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and > execute the previous request after a login occurs. This attribute is not > removed properly when navigating away from a page without logging in. > When navigating to a page that requires authentication the > "_PREVIOUS_REQUEST_" attribute is saved in the session from within the > LoginWorker to be called again when the login was successful through the > RequestHandler. Currently, the attribute is only removed when a login occurs > resulting in the previous request being stored in the session until some form > of login is successfully executed. > This behavior potentially results in navigation problems since a user is able > to navigate to a page requiring authentication without logging in. An old > request will be pulled from the session when a similar event occurs and the > user logs in. > > I propose to have the RequestHandler remove the session attribute > "_PREVIOUS_REQUEST_" after calling a request that does not require > authentication. We also have to restructure the sequence of request handling > to have the "targetRequestUri" handled after the security check and a > possible removal of the session attribute. > > One problem arises with this solution, however, which should be less of an > issue than the current state: > If the login page includes a request call that is handled after the request > showing the login page (for example an ajax call rendering a screen), the > "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To > my knowledge such a case does not exist within the OFBiz environment and > seems to be an edge case far less problematic than the above mentioned > problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[ https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17283025#comment-17283025 ] Olivier Heintz commented on OFBIZ-12047: yes the patch is already available in the jira > Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages > --- > > Key: OFBIZ-12047 > URL: https://issues.apache.org/jira/browse/OFBIZ-12047 > Project: OFBiz > Issue Type: Bug > Components: framework/webapp >Affects Versions: Release Branch 18.12, Trunk >Reporter: Ingo Könemann >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 18.12.01, Upcoming Branch > > Attachments: RequestHandler.java.patch > > > There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and > execute the previous request after a login occurs. This attribute is not > removed properly when navigating away from a page without logging in. > When navigating to a page that requires authentication the > "_PREVIOUS_REQUEST_" attribute is saved in the session from within the > LoginWorker to be called again when the login was successful through the > RequestHandler. Currently, the attribute is only removed when a login occurs > resulting in the previous request being stored in the session until some form > of login is successfully executed. > This behavior potentially results in navigation problems since a user is able > to navigate to a page requiring authentication without logging in. An old > request will be pulled from the session when a similar event occurs and the > user logs in. > > I propose to have the RequestHandler remove the session attribute > "_PREVIOUS_REQUEST_" after calling a request that does not require > authentication. We also have to restructure the sequence of request handling > to have the "targetRequestUri" handled after the security check and a > possible removal of the session attribute. > > One problem arises with this solution, however, which should be less of an > issue than the current state: > If the login page includes a request call that is handled after the request > showing the login page (for example an ajax call rendering a screen), the > "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To > my knowledge such a case does not exist within the OFBiz environment and > seems to be an edge case far less problematic than the above mentioned > problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[ https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281698#comment-17281698 ] Olivier Heintz commented on OFBIZ-12047: After some small study, it seem there is a problem because login request not require authentication :) I have tried to add a test to check if current request is login and only if it's not to remove _PREVIOUS_REQUEST_ Session Attribute, it seem better with this modification. I have put the patch to the jira, just to be more clear on modification I have tested, but I suppose there is a better way to do it. > Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages > --- > > Key: OFBIZ-12047 > URL: https://issues.apache.org/jira/browse/OFBIZ-12047 > Project: OFBiz > Issue Type: Bug > Components: framework/webapp >Affects Versions: Release Branch 18.12, Trunk >Reporter: Ingo Könemann >Assignee: Michael Brohl >Priority: Minor > Fix For: 18.12.01, Upcoming Branch > > Attachments: RequestHandler.java.patch > > > There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and > execute the previous request after a login occurs. This attribute is not > removed properly when navigating away from a page without logging in. > When navigating to a page that requires authentication the > "_PREVIOUS_REQUEST_" attribute is saved in the session from within the > LoginWorker to be called again when the login was successful through the > RequestHandler. Currently, the attribute is only removed when a login occurs > resulting in the previous request being stored in the session until some form > of login is successfully executed. > This behavior potentially results in navigation problems since a user is able > to navigate to a page requiring authentication without logging in. An old > request will be pulled from the session when a similar event occurs and the > user logs in. > > I propose to have the RequestHandler remove the session attribute > "_PREVIOUS_REQUEST_" after calling a request that does not require > authentication. We also have to restructure the sequence of request handling > to have the "targetRequestUri" handled after the security check and a > possible removal of the session attribute. > > One problem arises with this solution, however, which should be less of an > issue than the current state: > If the login page includes a request call that is handled after the request > showing the login page (for example an ajax call rendering a screen), the > "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To > my knowledge such a case does not exist within the OFBiz environment and > seems to be an edge case far less problematic than the above mentioned > problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[ https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-12047: --- Attachment: RequestHandler.java.patch > Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages > --- > > Key: OFBIZ-12047 > URL: https://issues.apache.org/jira/browse/OFBIZ-12047 > Project: OFBiz > Issue Type: Bug > Components: framework/webapp >Affects Versions: Release Branch 18.12, Trunk >Reporter: Ingo Könemann >Assignee: Michael Brohl >Priority: Minor > Fix For: 18.12.01, Upcoming Branch > > Attachments: RequestHandler.java.patch > > > There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and > execute the previous request after a login occurs. This attribute is not > removed properly when navigating away from a page without logging in. > When navigating to a page that requires authentication the > "_PREVIOUS_REQUEST_" attribute is saved in the session from within the > LoginWorker to be called again when the login was successful through the > RequestHandler. Currently, the attribute is only removed when a login occurs > resulting in the previous request being stored in the session until some form > of login is successfully executed. > This behavior potentially results in navigation problems since a user is able > to navigate to a page requiring authentication without logging in. An old > request will be pulled from the session when a similar event occurs and the > user logs in. > > I propose to have the RequestHandler remove the session attribute > "_PREVIOUS_REQUEST_" after calling a request that does not require > authentication. We also have to restructure the sequence of request handling > to have the "targetRequestUri" handled after the security check and a > possible removal of the session attribute. > > One problem arises with this solution, however, which should be less of an > issue than the current state: > If the login page includes a request call that is handled after the request > showing the login page (for example an ajax call rendering a screen), the > "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To > my knowledge such a case does not exist within the OFBiz environment and > seems to be an edge case far less problematic than the above mentioned > problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12047) Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages
[ https://issues.apache.org/jira/browse/OFBIZ-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281670#comment-17281670 ] Olivier Heintz commented on OFBIZ-12047: Good morning, With this modification, when I'm in a back-end application like party, if I call a uri like partymgr/control/FindCommunicationEvents without being connected (after more than 1 hour of inactivity) the login is called, but i'm redirected on main not to findCommunicationEvents result Is it what it is expected ? I understood (after reading description) that this should be only the case for request that does not require authentication. > Remove _PREVIOUS_REQUEST_ Session Attribute on non-authentication pages > --- > > Key: OFBIZ-12047 > URL: https://issues.apache.org/jira/browse/OFBIZ-12047 > Project: OFBiz > Issue Type: Bug > Components: framework/webapp >Affects Versions: Release Branch 18.12, Trunk >Reporter: Ingo Könemann >Assignee: Michael Brohl >Priority: Minor > Fix For: 18.12.01, Upcoming Branch > > > There is a session attribute called "_PREVIOUS_REQUEST_" used to remember and > execute the previous request after a login occurs. This attribute is not > removed properly when navigating away from a page without logging in. > When navigating to a page that requires authentication the > "_PREVIOUS_REQUEST_" attribute is saved in the session from within the > LoginWorker to be called again when the login was successful through the > RequestHandler. Currently, the attribute is only removed when a login occurs > resulting in the previous request being stored in the session until some form > of login is successfully executed. > This behavior potentially results in navigation problems since a user is able > to navigate to a page requiring authentication without logging in. An old > request will be pulled from the session when a similar event occurs and the > user logs in. > > I propose to have the RequestHandler remove the session attribute > "_PREVIOUS_REQUEST_" after calling a request that does not require > authentication. We also have to restructure the sequence of request handling > to have the "targetRequestUri" handled after the security check and a > possible removal of the session attribute. > > One problem arises with this solution, however, which should be less of an > issue than the current state: > If the login page includes a request call that is handled after the request > showing the login page (for example an ajax call rendering a screen), the > "_PREVIOUS_REQUEST_" attribute will be lost before the login is processed. To > my knowledge such a case does not exist within the OFBiz environment and > seems to be an edge case far less problematic than the above mentioned > problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11587) Migration all docbook file to asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267168#comment-17267168 ] Olivier Heintz commented on OFBIZ-11587: done, Thank you very much for your notice, it's really better when all is clear > Migration all docbook file to asciidoc > -- > > Key: OFBIZ-11587 > URL: https://issues.apache.org/jira/browse/OFBIZ-11587 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS, ALL PLUGINS >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: documentation > Time Spent: 40m > Remaining Estimate: 0h > > Umbrella task, for all components migration tasks. > Idea is to have only one branch/PR for all tasks, with one commit per > component / sub-component migration, it will be more easy to merge it when it > will be finish -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11587) Migration all docbook file to asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267112#comment-17267112 ] Olivier Heintz commented on OFBIZ-11587: Thank you Eugen for the reminder Thank you Jacques for the checking, I've just deleted the branch and thus closed the PR (65 & 66), I have forgot this step when I have done the last commit. Thanks > Migration all docbook file to asciidoc > -- > > Key: OFBIZ-11587 > URL: https://issues.apache.org/jira/browse/OFBIZ-11587 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS, ALL PLUGINS >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: documentation > Time Spent: 40m > Remaining Estimate: 0h > > Umbrella task, for all components migration tasks. > Idea is to have only one branch/PR for all tasks, with one commit per > component / sub-component migration, it will be more easy to merge it when it > will be finish -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-12065) migrated Wiki How to Create the main Company in Party Manager to user-manual
[ https://issues.apache.org/jira/browse/OFBIZ-12065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-12065. -- Fix Version/s: Trunk Resolution: Fixed > migrated Wiki How to Create the main Company in Party Manager to user-manual > > > Key: OFBIZ-12065 > URL: https://issues.apache.org/jira/browse/OFBIZ-12065 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > Fix For: Trunk > > > Add a first "process" in Party user-manual chapter with the > How to Create the main Company in Party Manager > coming from the > [https://cwiki.apache.org/confluence/display/OFBENDUSER/How+to+Create+the+main+Company+in+Party+Manager] > page > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12065) migrated Wiki How to Create the main Company in Party Manager to user-manual
Olivier Heintz created OFBIZ-12065: -- Summary: migrated Wiki How to Create the main Company in Party Manager to user-manual Key: OFBIZ-12065 URL: https://issues.apache.org/jira/browse/OFBIZ-12065 Project: OFBiz Issue Type: Improvement Components: party Affects Versions: Trunk Reporter: Olivier Heintz Assignee: Olivier Heintz Add a first "process" in Party user-manual chapter with the How to Create the main Company in Party Manager coming from the [https://cwiki.apache.org/confluence/display/OFBENDUSER/How+to+Create+the+main+Company+in+Party+Manager] page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11036) User Manual : change the level of from 2 to 1
[
https://issues.apache.org/jira/browse/OFBIZ-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz closed OFBIZ-11036.
--
Resolution: Fixed
> User Manual : change the level of from 2 to 1
> --
>
> Key: OFBIZ-11036
> URL: https://issues.apache.org/jira/browse/OFBIZ-11036
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Kaustubh Choudhary
>Priority: Minor
> Labels: Documentation
> Attachments:
> 0001-Documented-User-Manual-change-the-level-of-Core-Busi.patch
>
>
> If is on level 1, it become a main separator in
> TOC not a chapter
> TOC become
> {code:java}
> ...
> 2. Quick start
> Core Business Applications
> 3. Accounting
> 4. Human Resources
> {code}
> and so we have one more level (in TOC) for each application
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (OFBIZ-12060) migrated Wiki Glossary to glossary asciidoc files
[ https://issues.apache.org/jira/browse/OFBIZ-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-12060. -- Resolution: Fixed > migrated Wiki Glossary to glossary asciidoc files > - > > Key: OFBIZ-12060 > URL: https://issues.apache.org/jira/browse/OFBIZ-12060 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > Labels: Documentation > > Put in Glossary asciidoc files, GeneralGlossary or glossary per component all > wiki glossary entries. > Each time a entry is put in a asciidoc file, update wiki to replace text by a > link to the glossary entry (in html generated manual) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12060) migrated Wiki Glossary to glossary asciidoc files
Olivier Heintz created OFBIZ-12060: -- Summary: migrated Wiki Glossary to glossary asciidoc files Key: OFBIZ-12060 URL: https://issues.apache.org/jira/browse/OFBIZ-12060 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Olivier Heintz Assignee: Olivier Heintz Put in Glossary asciidoc files, GeneralGlossary or glossary per component all wiki glossary entries. Each time a entry is put in a asciidoc file, update wiki to replace text by a link to the glossary entry (in html generated manual) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12059) Synchronize wiki page End User Documentation
[ https://issues.apache.org/jira/browse/OFBIZ-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17233562#comment-17233562 ] Olivier Heintz commented on OFBIZ-12059: Thank you very much Jacques. > Synchronize wiki page End User Documentation > > > Key: OFBIZ-12059 > URL: https://issues.apache.org/jira/browse/OFBIZ-12059 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > > Synchronize this page with User-manual (in asciidoc format) > check that all informations in this page are in a asciidoc file > If necessary update asciidoc files > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-12059) Synchronize wiki page End User Documentation
[ https://issues.apache.org/jira/browse/OFBIZ-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-12059. -- Resolution: Fixed > Synchronize wiki page End User Documentation > > > Key: OFBIZ-12059 > URL: https://issues.apache.org/jira/browse/OFBIZ-12059 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > > Synchronize this page with User-manual (in asciidoc format) > check that all informations in this page are in a asciidoc file > If necessary update asciidoc files > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-12059) Synchronize wiki page End User Documentation
[ https://issues.apache.org/jira/browse/OFBIZ-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz reassigned OFBIZ-12059: -- Assignee: Olivier Heintz > Synchronize wiki page End User Documentation > > > Key: OFBIZ-12059 > URL: https://issues.apache.org/jira/browse/OFBIZ-12059 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Major > > Synchronize this page with User-manual (in asciidoc format) > check that all informations in this page are in a asciidoc file > If necessary update asciidoc files > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12059) Synchronize wiki page End User Documentation
Olivier Heintz created OFBIZ-12059: -- Summary: Synchronize wiki page End User Documentation Key: OFBIZ-12059 URL: https://issues.apache.org/jira/browse/OFBIZ-12059 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Olivier Heintz Synchronize this page with User-manual (in asciidoc format) check that all informations in this page are in a asciidoc file If necessary update asciidoc files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12058) Migration/synchronization wiki - asciidoc for user-manual
Olivier Heintz created OFBIZ-12058: -- Summary: Migration/synchronization wiki - asciidoc for user-manual Key: OFBIZ-12058 URL: https://issues.apache.org/jira/browse/OFBIZ-12058 Project: OFBiz Issue Type: Improvement Affects Versions: Trunk Reporter: Olivier Heintz Umbrella task for All tasks which will check for a wiki page if its content exist in a asciidoc file or if its content is no longer relevant. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10390) New documentation for EntitySync
[ https://issues.apache.org/jira/browse/OFBIZ-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10390: --- Labels: Documentation (was: ) > New documentation for EntitySync > > > Key: OFBIZ-10390 > URL: https://issues.apache.org/jira/browse/OFBIZ-10390 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Labels: Documentation > Fix For: Upcoming Branch > > > The [current EntitySync documentation in > wiki|https://cwiki.apache.org/confluence/display/OFBIZ/Sync+Setup+Notes+and+Example] > is POS oriented so somehow deprecated. > I have recently worked on a project with EntitySync and collected as much > possible information. I also got David E. Jones's agreement to reuse the part > on EntitySync in his 2006 "Apache OFBiz Advanced Framework - Training Video > Transcription" document. > So I'll create an Asciidoc file: > framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc and will fill it > with all the available information I have. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-10303. -- Assignee: Olivier Heintz Resolution: Fixed > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: Documentation > Attachments: > OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11364) OFBizDocumentationSystem migration to Asciidoc and Review
[ https://issues.apache.org/jira/browse/OFBIZ-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-11364. -- Resolution: Fixed > OFBizDocumentationSystem migration to Asciidoc and Review > - > > Key: OFBIZ-11364 > URL: https://issues.apache.org/jira/browse/OFBIZ-11364 > Project: OFBiz > Issue Type: Sub-task > Components: commonext >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: Documentation > Attachments: OFBizDocumentationSystem.adoc, > OFBizDocumentationSystem_FR.adoc > > > # Migrate Docbook format to Asciidoc format > # complete review of content > Review should be done when "application user Help" will be rebuild -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12030) Help system can be on user language (help using asciidoc files)
[ https://issues.apache.org/jira/browse/OFBIZ-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231352#comment-17231352 ] Olivier Heintz commented on OFBIZ-12030: Currently entry point for documentation and/or help is two mains files: user-manual and developer-manual, so the easy way to have multi language documentation is to have these files available for other languages. Currently, help uri is given by a general property "userDocUri", one idea is to dedicate a property file (which could be internationalize), so reading the property with the user local give the correct entry point. > Help system can be on user language (help using asciidoc files) > --- > > Key: OFBIZ-12030 > URL: https://issues.apache.org/jira/browse/OFBIZ-12030 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Major > Labels: Documentation, asciidoc > > Previous help system, using docbook and content component was able to be on > multiple language. > The goal of this Jira is to propose a solution for the help system using > asciidoc files. > Currently there are not a lot of files which are not in English (less than > 10) but it's necessary to have a solution for users / customers which use > ofbiz documentation system as the internal process documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11036) User Manual : change the level of from 2 to 1
[
https://issues.apache.org/jira/browse/OFBIZ-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-11036:
---
Labels: Documentation (was: )
> User Manual : change the level of from 2 to 1
> --
>
> Key: OFBIZ-11036
> URL: https://issues.apache.org/jira/browse/OFBIZ-11036
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Kaustubh Choudhary
>Priority: Minor
> Labels: Documentation
> Attachments:
> 0001-Documented-User-Manual-change-the-level-of-Core-Busi.patch
>
>
> If is on level 1, it become a main separator in
> TOC not a chapter
> TOC become
> {code:java}
> ...
> 2. Quick start
> Core Business Applications
> 3. Accounting
> 4. Human Resources
> {code}
> and so we have one more level (in TOC) for each application
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10303: --- Labels: Documentation (was: ) > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Labels: Documentation > Attachments: > OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11587) Migration all docbook file to asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-11587. -- Assignee: Olivier Heintz Resolution: Fixed > Migration all docbook file to asciidoc > -- > > Key: OFBIZ-11587 > URL: https://issues.apache.org/jira/browse/OFBIZ-11587 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS, ALL PLUGINS >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: documentation > Time Spent: 40m > Remaining Estimate: 0h > > Umbrella task, for all components migration tasks. > Idea is to have only one branch/PR for all tasks, with one commit per > component / sub-component migration, it will be more easy to merge it when it > will be finish -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-9597) Documentation: Customer Relationship Management (CRM) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-9597: -- Labels: BPRB CRM Documentation OBPRB (was: BPRB CRM OBPRB) > Documentation: Customer Relationship Management (CRM) Process Overview > --- > > Key: OFBIZ-9597 > URL: https://issues.apache.org/jira/browse/OFBIZ-9597 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pranay Pandey >Assignee: Shivangi Tanwar >Priority: Major > Labels: BPRB, CRM, Documentation, OBPRB > > CRM process overview to be documented. > *Doc Content:* > Every CRM business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient CRM capabilities in real > world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10255) Add Document Content: humanres.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10255: --- Labels: Documentation (was: ) > Add Document Content: humanres.adoc > --- > > Key: OFBIZ-10255 > URL: https://issues.apache.org/jira/browse/OFBIZ-10255 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sharan Foga >Assignee: Sharan Foga >Priority: Minor > Labels: Documentation > Attachments: OFBIZ-10255.patch, humanres.adoc, humanres.adoc.patch > > > Using details from the OFBiz wiki workspaces and the Human Resources Guide > and other human resources asciidoc file, write or organise the content for > the humanres.adoc file. > An copy of the existing file will be attached. > Please update the template and re-attach it. > NOTE: This document might not be able to be completed until other sections > for Human Resources are done. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz closed OFBIZ-12035.
--
Fix Version/s: Trunk
Resolution: Fixed
All seem to works correctly, on *nix directory in doc/images is created at the
beginning and removed at the end.
There are still warning message when pdf is generated, but these are wrong
because all images are present in html and pdf. I will post an issue in
ascidoctor project for that.
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Fix For: Trunk
>
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (OFBIZ-11893) Error messages when generating HTML and PDF file from AsciiDoc files
[
https://issues.apache.org/jira/browse/OFBIZ-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz closed OFBIZ-11893.
--
Fix Version/s: Trunk
Release Branch 17.12
Release Branch 18.12
Assignee: Olivier Heintz
Resolution: Fixed
> Error messages when generating HTML and PDF file from AsciiDoc files
>
>
> Key: OFBIZ-11893
> URL: https://issues.apache.org/jira/browse/OFBIZ-11893
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Olivier Heintz
>Priority: Minor
> Labels: Documentation
> Fix For: Release Branch 18.12, Release Branch 17.12, Trunk
>
>
> {noformat}
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> juil. 10, 2020 2:24:54 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:24:57 PM
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:26:01 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> juil. 10, 2020 2:26:19 PM
> uri:classloader:/gems/asciidoctor-pdf-1.5.3/lib/asciidoctor/pdf/converter.rb
> convert_inline_icon
> {noformat}
> There are also warnings and infos:
> {noformat}
> AVERTISSEMENT: sy-CSRF-defense.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-CSRF-defense.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs
> /asciidoc/_include/sy-CSRF-defense.adoc:31
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:31
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 36: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:36
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 53: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:53
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-password-and-JWT.adoc: line 31: section title out of
>
[jira] [Commented] (OFBIZ-11893) Error messages when generating HTML and PDF file from AsciiDoc files
[
https://issues.apache.org/jira/browse/OFBIZ-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208050#comment-17208050
]
Olivier Heintz commented on OFBIZ-11893:
I close this Jira because last Warning message are wrong (images are correct in
html and pdf)
I suppose it's a asciidoctorPdf bug, I will open an issue on the asciidoctor
project
> Error messages when generating HTML and PDF file from AsciiDoc files
>
>
> Key: OFBIZ-11893
> URL: https://issues.apache.org/jira/browse/OFBIZ-11893
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
> Labels: Documentation
>
> {noformat}
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> juil. 10, 2020 2:24:54 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:24:57 PM
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:26:01 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> juil. 10, 2020 2:26:19 PM
> uri:classloader:/gems/asciidoctor-pdf-1.5.3/lib/asciidoctor/pdf/converter.rb
> convert_inline_icon
> {noformat}
> There are also warnings and infos:
> {noformat}
> AVERTISSEMENT: sy-CSRF-defense.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-CSRF-defense.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs
> /asciidoc/_include/sy-CSRF-defense.adoc:31
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:31
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 36: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:36
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 53: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:53
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-password-and-JWT.adoc: line 31: section title out of
> sequence: expected levels 0 or 1, got level 2
> section
[jira] [Updated] (OFBIZ-11976) svg files not removed on clean
[ https://issues.apache.org/jira/browse/OFBIZ-11976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-11976: --- Labels: documentation (was: ) > svg files not removed on clean > -- > > Key: OFBIZ-11976 > URL: https://issues.apache.org/jira/browse/OFBIZ-11976 > Project: OFBiz > Issue Type: Bug > Components: ALL PLUGINS >Affects Versions: Release Branch 17.12, Trunk >Reporter: Alex Bodnaru >Assignee: Jacques Le Roux >Priority: Major > Labels: documentation > Fix For: 18.12.01, 17.12.05 > > > files like birt/src/docs/asciidoc/images/OFBiz-Logo.svg, > in many plugins, don't get removed on clean. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11976) svg files not removed on clean
[
https://issues.apache.org/jira/browse/OFBIZ-11976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206343#comment-17206343
]
Olivier Heintz commented on OFBIZ-11976:
Jacques, to test the correction done in OFBIZ-12035, start by running
generateOFBizDocumentation (or an other gradle task) and no OFBiz-Logo.svg
should by copied (and so remain :) )
if the first test is ok, run {{g generateAllPluginsDocumentation}} and no
OFBiz-Logo.svg files should remains after.
I backport the correction
> svg files not removed on clean
> --
>
> Key: OFBIZ-11976
> URL: https://issues.apache.org/jira/browse/OFBIZ-11976
> Project: OFBiz
> Issue Type: Bug
> Components: ALL PLUGINS
>Affects Versions: Release Branch 17.12, Trunk
>Reporter: Alex Bodnaru
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 18.12.01, 17.12.05
>
>
> files like birt/src/docs/asciidoc/images/OFBiz-Logo.svg,
> in many plugins, don't get removed on clean.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206251#comment-17206251
]
Olivier Heintz commented on OFBIZ-12035:
Jacques, thank you for your review and remarks,
I have replace tab by space before commit (and change my local config to avoid
this in future)
I will check if a part of the patch is necessary in release branch
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11893) Error messages when generating HTML and PDF file from AsciiDoc files
[
https://issues.apache.org/jira/browse/OFBIZ-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206246#comment-17206246
]
Olivier Heintz commented on OFBIZ-11893:
Jacques, Thank you very much for your remarks
I will test in the release branch to see which corrections are possible to
backport
For the warning, I dont't think it's necessary to open a Jira as I suppose it's
a asciidoctorPdf bug
After checking buildbot log I will close the jira
PS: about commit message, I have corrected my local configuration to avoid to
split commit message. I will check if it's correct now
> Error messages when generating HTML and PDF file from AsciiDoc files
>
>
> Key: OFBIZ-11893
> URL: https://issues.apache.org/jira/browse/OFBIZ-11893
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> {noformat}
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> juil. 10, 2020 2:24:54 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:24:57 PM
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:26:01 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> juil. 10, 2020 2:26:19 PM
> uri:classloader:/gems/asciidoctor-pdf-1.5.3/lib/asciidoctor/pdf/converter.rb
> convert_inline_icon
> {noformat}
> There are also warnings and infos:
> {noformat}
> AVERTISSEMENT: sy-CSRF-defense.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-CSRF-defense.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs
> /asciidoc/_include/sy-CSRF-defense.adoc:31
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:31
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 36: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:36
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 53: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
>
[jira] [Updated] (OFBIZ-11893) Error messages when generating HTML and PDF file from AsciiDoc files
[
https://issues.apache.org/jira/browse/OFBIZ-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-11893:
---
Labels: Documentation (was: )
> Error messages when generating HTML and PDF file from AsciiDoc files
>
>
> Key: OFBIZ-11893
> URL: https://issues.apache.org/jira/browse/OFBIZ-11893
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
> Labels: Documentation
>
> {noformat}
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> juil. 10, 2020 2:24:54 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:24:57 PM
> ERROR: hr-employments.adoc: line 58: invalid part, must have at least one
> section (e.g., chapter, appendix, etc.)
> invalid part, must have at least one section (e.g., chapter, appendix, etc.)
> :: hr-employments.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/humanres/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/applications/hu
> manres/src/docs/asciidoc/_include/hr-employments.adoc:58
> include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> :: manufacturing_NL.adoc ::
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/C:
> /projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/manufacturing_NL.adoc:29
> juil. 10, 2020 2:26:01 PM
> ERROR: manufacturing_NL.adoc: line 29: include file not found:
> C:/projectsASF/Git/ofbiz-framework/applications/manufacturing/src/docs/asciidoc/_include/hr-intro.adoc
> juil. 10, 2020 2:26:19 PM
> uri:classloader:/gems/asciidoctor-pdf-1.5.3/lib/asciidoctor/pdf/converter.rb
> convert_inline_icon
> {noformat}
> There are also warnings and infos:
> {noformat}
> AVERTISSEMENT: sy-CSRF-defense.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-CSRF-defense.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs
> /asciidoc/_include/sy-CSRF-defense.adoc:31
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:31
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 31: section title out of sequence:
> expected levels 0 or 1, got level 2
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 36: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:36
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-impersonation.adoc: line 53: section title out of sequence:
> expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-impersonation.adoc ::
> C:/projectsASF/Git/ofbiz-framework/framework/security/src/docs/asciidoc/_include/C:/projectsASF/Git/ofbiz-framework/framework/security/src/doc
> s/asciidoc/_include/sy-impersonation.adoc:53
> juil. 10, 2020 2:24:57 PM
> AVERTISSEMENT: sy-password-and-JWT.adoc: line 31: section title out of
> sequence: expected levels 0 or 1, got level 2
> section title out of sequence: expected levels 0 or 1, got level 2 ::
> sy-password-and-JWT.adoc ::
>
[jira] [Assigned] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz reassigned OFBIZ-12035:
--
Assignee: Olivier Heintz
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206081#comment-17206081
]
Olivier Heintz commented on OFBIZ-12035:
With these modifications, all documents are generated correctly with
* generateOfbizDocumentation
* generateAllPluginsDocumentation
but there are still WARNING for pdf generation about image not found
I have not found why there are these messages, it seem to be a bug on pdf
generation because error message give a incorrect patch (ex:
plugins/birt/src/docs/asciidoc/_include/Report-Builder.png)
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206079#comment-17206079
]
Olivier Heintz commented on OFBIZ-12035:
Add a correction in gradle modification, to avoid to have OFBiz-Logo copied in
the gradle "Configure project" step.
[^framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch]
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-12035:
---
Attachment:
framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205534#comment-17205534
]
Olivier Heintz edited comment on OFBIZ-12035 at 10/1/20, 1:55 PM:
--
Two patch generated by git format-patch, one for ofbiz-framework and one for
ofbiz-plugins
To apply it use git am \{patchName} in each environment
[^framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch]
^[^plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch]^
was (Author: holivier):
Two patch generated by git format-patch, one for ofbiz-framework and one for
ofbiz-plugins
To apply it use git am \{patchName} in each environment
[^0001-Improved-change-asciidoc-Image-directory-convention-.patch]
[^framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch]
^[^plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch]^
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz reassigned OFBIZ-12035:
--
Assignee: (was: Olivier Heintz)
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205534#comment-17205534
]
Olivier Heintz commented on OFBIZ-12035:
Two patch generated by git format-patch, one for ofbiz-framework and one for
ofbiz-plugins
To apply it use git am \{patchName} in each environment
[^0001-Improved-change-asciidoc-Image-directory-convention-.patch]
[^framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch]
^[^plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch]^
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> 0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-12035:
---
Attachment:
plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-12035:
---
Attachment: (was:
0001-Improved-change-asciidoc-Image-directory-convention-.patch)
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> plugins_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-12035:
---
Attachment:
framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> 0001-Improved-change-asciidoc-Image-directory-convention-.patch,
> framework_0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
[
https://issues.apache.org/jira/browse/OFBIZ-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-12035:
---
Attachment: 0001-Improved-change-asciidoc-Image-directory-convention-.patch
> asciidoc Image directory convention for plugins and components
> --
>
> Key: OFBIZ-12035
> URL: https://issues.apache.org/jira/browse/OFBIZ-12035
> Project: OFBiz
> Issue Type: Improvement
> Components: birt
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Olivier Heintz
>Priority: Major
> Labels: Documentation
> Attachments:
> 0001-Improved-change-asciidoc-Image-directory-convention-.patch
>
>
> Plugins documentation (in asciidoc) can be generated with one document per
> plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
> directory) or include in the general
> [user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
> or
> [developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
> Currently, image usage not works in the two case, because image path is
> relative to the root document.
> To solve the problem, I propose to put image(s) relative to a component in
> the src/docs/asciidoc/images/${component.name} of the component and modifying
> gradle generateDocumentation task to copy the subdirectory in the general
> docs/asciidoc/images/ directory before generation and remove it after.
> Currently only birt is concern but it's better to have schema and other image
> in documentation, so in future all components should be concerned.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OFBIZ-12035) asciidoc Image directory convention for plugins and components
Olivier Heintz created OFBIZ-12035:
--
Summary: asciidoc Image directory convention for plugins and
components
Key: OFBIZ-12035
URL: https://issues.apache.org/jira/browse/OFBIZ-12035
Project: OFBiz
Issue Type: Improvement
Components: birt
Affects Versions: Trunk
Reporter: Olivier Heintz
Assignee: Olivier Heintz
Plugins documentation (in asciidoc) can be generated with one document per
plugins (in [https://ci.apache.org/projects/ofbiz/site/trunk/pluginsdoc/]
directory) or include in the general
[user-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/user-manual.html#_apache_ofbiz_plugins]
or
[developer-manual|https://ci.apache.org/projects/ofbiz/site/trunk/ofbizdoc/html5/developer-manual.html#_apache_ofbiz_plugins_for_developer]
Currently, image usage not works in the two case, because image path is
relative to the root document.
To solve the problem, I propose to put image(s) relative to a component in the
src/docs/asciidoc/images/${component.name} of the component and modifying
gradle generateDocumentation task to copy the subdirectory in the general
docs/asciidoc/images/ directory before generation and remove it after.
Currently only birt is concern but it's better to have schema and other image
in documentation, so in future all components should be concerned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OFBIZ-12030) Help system can be on user language (help using asciidoc files)
Olivier Heintz created OFBIZ-12030: -- Summary: Help system can be on user language (help using asciidoc files) Key: OFBIZ-12030 URL: https://issues.apache.org/jira/browse/OFBIZ-12030 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Olivier Heintz Previous help system, using docbook and content component was able to be on multiple language. The goal of this Jira is to propose a solution for the help system using asciidoc files. Currently there are not a lot of files which are not in English (less than 10) but it's necessary to have a solution for users / customers which use ofbiz documentation system as the internal process documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12002) Show border and file name for content rendered from ftl
[ https://issues.apache.org/jira/browse/OFBIZ-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17198995#comment-17198995 ] Olivier Heintz commented on OFBIZ-12002: Hi James, It seems, these patch create a bug in hr, on main screen (the tree company organization) # open the tree # with right click do "add internal organization" # the EditInternalOrg.ftl opens but it is not usable (it's not possible to click to open the drop-down ) and the div class="info-overlay"> not disappear > Show border and file name for content rendered from ftl > --- > > Key: OFBIZ-12002 > URL: https://issues.apache.org/jira/browse/OFBIZ-12002 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Upcoming Branch >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12002.patch > > > Currently there are before and after comments in the page source to mark the > begin and end of FTL template. Easier for development to display FTL file > name and boundary on screen for a short time. > Only works for FTL files outside of theme folders, and when > 1) print.verbose=true and > 2) widget.verbose=true -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10251) Move Human Resources Guide into OFBiz Asciidoc Framework
[ https://issues.apache.org/jira/browse/OFBIZ-10251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196181#comment-17196181 ] Olivier Heintz commented on OFBIZ-10251: Thank you very mush for the review, You are right, currently there are still some points to discuss. I think, it's necessary to have a ready to read place for the different tasks, it's why I update the patch after the main part of docbook migration to asciidoc. I propose to finish first, the docbook migration to asccidoc (only 2-3 commit, one or two week), before starting the discussion. > Move Human Resources Guide into OFBiz Asciidoc Framework > > > Key: OFBIZ-10251 > URL: https://issues.apache.org/jira/browse/OFBIZ-10251 > Project: OFBiz > Issue Type: Task >Reporter: Sharan Foga >Assignee: Michael Brohl >Priority: Minor > Labels: asciidoc, documentation, humanres > Attachments: introduction.patch > > Time Spent: 20m > Remaining Estimate: 0h > > This is a general umbrella issue for managing the creation and migration of > all OFBiz related Human Resources documentation into the OFBiz code base. > Subtasks will be created for each of the documents that need to be created. > Also created as a sub task will the task to create empty documents for each > of the sub-files in the list > An initial list is as follows: > # human-resources.adoc > # human-resources-intro.adoc > # employee-evaluations.adoc > # human-resources-glossary.adoc > # employee-positions.adoc > # employees.adoc > # employments.adoc > # performance-review.adoc > # positions.adoc > # qualifications.adoc > # recruitment.adoc > # skiils.adoc > # resumes.adoc > # training.adoc > # leave.adoc > # human-resources-security.adoc > # human-resources-global-settings.adoc > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11036) User Manual : change the level of from 2 to 1
[
https://issues.apache.org/jira/browse/OFBIZ-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196175#comment-17196175
]
Olivier Heintz commented on OFBIZ-11036:
to apply patch generated by git format-patch, you have just to do (after
downloading the patch file)
git am
this apply the patch by adding a commit in your environment so it's better to
do it on a local test branch
it's very similar to a PR with only one commit
> User Manual : change the level of from 2 to 1
> --
>
> Key: OFBIZ-11036
> URL: https://issues.apache.org/jira/browse/OFBIZ-11036
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Kaustubh Choudhary
>Priority: Minor
> Attachments:
> 0001-Documented-User-Manual-change-the-level-of-Core-Busi.patch
>
>
> If is on level 1, it become a main separator in
> TOC not a chapter
> TOC become
> {code:java}
> ...
> 2. Quick start
> Core Business Applications
> 3. Accounting
> 4. Human Resources
> {code}
> and so we have one more level (in TOC) for each application
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10303: --- Attachment: (was: OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch) > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Attachments: > OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10303: --- Attachment: OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Attachments: > OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196165#comment-17196165 ] Olivier Heintz commented on OFBIZ-10303: Thanks you very much for the review, I have made some corrections, and some other later ;) I should finish the docbook to asciidoc before, and the previous patch update was only to be able to have an environment with all my pending modifications on documentation to publish them on ofbizextra documentation websitewebsite Some component are not yet link to corresponding chapter because when I have created this first release, asciidoc for these components not exist + at the end of line are same as > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Attachments: > OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11039) add a chapter "About this documentation"
[ https://issues.apache.org/jira/browse/OFBIZ-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-11039: --- Attachment: OFBIZ-11039_Documented-add-a-chapter-About-this-documentation-in.patch > add a chapter "About this documentation" > > > Key: OFBIZ-11039 > URL: https://issues.apache.org/jira/browse/OFBIZ-11039 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Major > Fix For: Trunk > > Attachments: Employee_Main_Screen.png, > HR-Employee_Submenu_Rainbow_Stone.png, HR-Employee_Submenu_Tomahawk.png, > HR_Application_Submenu_Rainbow_Stone.png, > HR_Application_Submenu_Tomahawk.png, > OFBIZ-11039_Documented-add-a-chapter-About-this-documentation-in.patch, > hr-about-doc.adoc > > > This chapter present the main OFBiz GUI rules with some screenshot and link > between tutorial and video of "Scenario GUI Test" > Currently it's in HR, but when other application will be done it can be > generalize and go to User Manual introduction. > The file hr-about-doc.adoc associated with this task is included via a > include:: line in the humanres.adoc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11039) add a chapter "About this documentation"
[ https://issues.apache.org/jira/browse/OFBIZ-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195538#comment-17195538 ] Olivier Heintz commented on OFBIZ-11039: create a new patch (with git format-patch so applicable with git am) which replace all the previous patch this patch is applicable after OFBIZ-11026 one because it update humanres.adoc too (add one line to include the new file). [^OFBIZ-11039_Documented-add-a-chapter-About-this-documentation-in.patch] > add a chapter "About this documentation" > > > Key: OFBIZ-11039 > URL: https://issues.apache.org/jira/browse/OFBIZ-11039 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Major > Fix For: Trunk > > Attachments: Employee_Main_Screen.png, > HR-Employee_Submenu_Rainbow_Stone.png, HR-Employee_Submenu_Tomahawk.png, > HR_Application_Submenu_Rainbow_Stone.png, > HR_Application_Submenu_Tomahawk.png, > OFBIZ-11039_Documented-add-a-chapter-About-this-documentation-in.patch, > hr-about-doc.adoc > > > This chapter present the main OFBiz GUI rules with some screenshot and link > between tutorial and video of "Scenario GUI Test" > Currently it's in HR, but when other application will be done it can be > generalize and go to User Manual introduction. > The file hr-about-doc.adoc associated with this task is included via a > include:: line in the humanres.adoc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11027) HR Doc, Associated a scenario UI test for each process
[ https://issues.apache.org/jira/browse/OFBIZ-11027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-11027: --- Attachment: OFBIZ-11027_Documented-HR-Doc-Associated-a-scenario-UI-test-for-.patch > HR Doc, Associated a scenario UI test for each process > -- > > Key: OFBIZ-11027 > URL: https://issues.apache.org/jira/browse/OFBIZ-11027 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Major > Labels: Documentation, humanres, tutorial > Attachments: > OFBIZ-11027_Documented-HR-Doc-Associated-a-scenario-UI-test-for-.patch, > OFBIZ-11027_hr-intro.adoc.patch, hr-tuto-define-company-organization.adoc, > hr-tuto-employment-and-salary.adoc > > > I propose that in HR documentation, each process is described via a scenario > explained like a tutorial. > To realize the tutorial, and to have more quality, I propose to create a UI > Test for each process. > In these tests, some user messages are added and a video recording is in > place when it run, so result is usable as a tutorial > With this method to create tutorial we are sure it are up to date and it > works ! > Currently a tutorial / test exist for process "Organization, Job Position and > Definition" and it run ona daily base on Apache OFBiz trunk demo. > A second one exist for process "Employee Salary and Benefits Administration" > but for runing some modification /enhancement are needed, so currenlty it not > run on Apache OFBiz trunk demo. > Result video are readeable > https://video.ploud.fr/video-channels/ofbizextra_tutorial/videos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11027) HR Doc, Associated a scenario UI test for each process
[ https://issues.apache.org/jira/browse/OFBIZ-11027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195530#comment-17195530 ] Olivier Heintz commented on OFBIZ-11027: create a new patch (with git format-patch so applicable with git am) this patch is applicable after OFBIZ-11026 one because it update hr-intro.adoc In this patch there are two scenario UI, one per documented HR process [^OFBIZ-11027_Documented-HR-Doc-Associated-a-scenario-UI-test-for-.patch] > HR Doc, Associated a scenario UI test for each process > -- > > Key: OFBIZ-11027 > URL: https://issues.apache.org/jira/browse/OFBIZ-11027 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Major > Labels: Documentation, humanres, tutorial > Attachments: OFBIZ-11027_hr-intro.adoc.patch, > hr-tuto-define-company-organization.adoc, hr-tuto-employment-and-salary.adoc > > > I propose that in HR documentation, each process is described via a scenario > explained like a tutorial. > To realize the tutorial, and to have more quality, I propose to create a UI > Test for each process. > In these tests, some user messages are added and a video recording is in > place when it run, so result is usable as a tutorial > With this method to create tutorial we are sure it are up to date and it > works ! > Currently a tutorial / test exist for process "Organization, Job Position and > Definition" and it run ona daily base on Apache OFBiz trunk demo. > A second one exist for process "Employee Salary and Benefits Administration" > but for runing some modification /enhancement are needed, so currenlty it not > run on Apache OFBiz trunk demo. > Result video are readeable > https://video.ploud.fr/video-channels/ofbizextra_tutorial/videos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11026) HR Doc drive by process
[ https://issues.apache.org/jira/browse/OFBIZ-11026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-11026: --- Attachment: OFBIZ-11026_Documented-HR-Doc-drive-by-process-OFBIZ-11026.patch > HR Doc drive by process > --- > > Key: OFBIZ-11026 > URL: https://issues.apache.org/jira/browse/OFBIZ-11026 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Michael Brohl >Priority: Major > Labels: Documentation, humanres > Attachments: > OFBIZ-11026_Documented-HR-Doc-drive-by-process-OFBIZ-11026.patch, > OFBIZ-11026_hr-intro.adoc.patch, OFBIZ-11026_humanres.adoc.patch, > OFBIZ-11026_humanres.adoc_with_hr-about-doc.patch > > > Currently HR doc main chapters are on core HR object, I propose to group them > in a chapter and having a chapter by process in the same level bot group in > the HR Process. > Each process is described via a scenario explained like a tutorial, and each > time a core object is used, a link is done to its chapter. > To help review : doc with these modifications are available at > [https://ofbizadoc.ofbizextra.org/html5/user-manual.html#_human_resources] > and Apache OFBiz standard (without modifications) is available too at > https://ofbizadoc.ofbizextra.org/html5/user-manual-std.html#_human_resources > current HR TOC > -- > 3.2. Human Resources > 3.2.1. About Human Resources > 3.2.2. Human Resources Processes > 3.2.3. Employee Positions > 3.2.4. Employees > 3.2.5. Employments > 3.2.6. Performance Review > 3.2.7. Qualifications > 3.2.8. Recruitment > 3.2.9. Skills > 3.2.10. Resumes > 3.2.11. Training > 3.2.12. Leave > 3.2.13. Security > 3.2.14. Global HR Settings > 3.2.15. Glossary > Proposed HR TOC > > 4. Human Resources > 4.1. About this documentation > 4.2. About Human Resources > 4.3. HR Processes > 4.3.1. Organization, Job Position and Definition > 4.3.2. Recruitment, Candidate Selection and Hiring > 4.3.3. Employee Training and Development > 4.3.4. Performance Management and Employee Evaluation > 4.3.5. Employee Salary and Benefits Administration > 4.4. HR core object > 4.4.1. Employee Positions > 4.4.2. Employees > 4.4.3. Employments > 4.4.4. Performance Review > 4.4.5. Qualifications > 4.4.6. Recruitment > 4.4.7. Skills > 4.4.8. Resumes > 4.4.9. Training > 4.4.10. Leave > 4.4.11. Security > 4.5. Global HR Settings > 4.5.1. Skills Types > 4.6. HR Data model > 4.6.1. Employee Position > 4.6.2. Employment > 4.6.3. Qualification, Skill, Review > 4.6.4. HR App intra-application integration > 4.7. Glossary -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11026) HR Doc drive by process
[ https://issues.apache.org/jira/browse/OFBIZ-11026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195523#comment-17195523 ] Olivier Heintz commented on OFBIZ-11026: create a new patch (with git format-patch so applicable with git am) including the new sub-chapter hr-data-model and hr-appendix [^OFBIZ-11026_Documented-HR-Doc-drive-by-process-OFBIZ-11026.patch] > HR Doc drive by process > --- > > Key: OFBIZ-11026 > URL: https://issues.apache.org/jira/browse/OFBIZ-11026 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Michael Brohl >Priority: Major > Labels: Documentation, humanres > Attachments: OFBIZ-11026_hr-intro.adoc.patch, > OFBIZ-11026_humanres.adoc.patch, > OFBIZ-11026_humanres.adoc_with_hr-about-doc.patch > > > Currently HR doc main chapters are on core HR object, I propose to group them > in a chapter and having a chapter by process in the same level bot group in > the HR Process. > Each process is described via a scenario explained like a tutorial, and each > time a core object is used, a link is done to its chapter. > To help review : doc with these modifications are available at > [https://ofbizadoc.ofbizextra.org/html5/user-manual.html#_human_resources] > and Apache OFBiz standard (without modifications) is available too at > https://ofbizadoc.ofbizextra.org/html5/user-manual-std.html#_human_resources > current HR TOC > -- > 3.2. Human Resources > 3.2.1. About Human Resources > 3.2.2. Human Resources Processes > 3.2.3. Employee Positions > 3.2.4. Employees > 3.2.5. Employments > 3.2.6. Performance Review > 3.2.7. Qualifications > 3.2.8. Recruitment > 3.2.9. Skills > 3.2.10. Resumes > 3.2.11. Training > 3.2.12. Leave > 3.2.13. Security > 3.2.14. Global HR Settings > 3.2.15. Glossary > Proposed HR TOC > > 4. Human Resources > 4.1. About this documentation > 4.2. About Human Resources > 4.3. HR Processes > 4.3.1. Organization, Job Position and Definition > 4.3.2. Recruitment, Candidate Selection and Hiring > 4.3.3. Employee Training and Development > 4.3.4. Performance Management and Employee Evaluation > 4.3.5. Employee Salary and Benefits Administration > 4.4. HR core object > 4.4.1. Employee Positions > 4.4.2. Employees > 4.4.3. Employments > 4.4.4. Performance Review > 4.4.5. Qualifications > 4.4.6. Recruitment > 4.4.7. Skills > 4.4.8. Resumes > 4.4.9. Training > 4.4.10. Leave > 4.4.11. Security > 4.5. Global HR Settings > 4.5.1. Skills Types > 4.6. HR Data model > 4.6.1. Employee Position > 4.6.2. Employment > 4.6.3. Qualification, Skill, Review > 4.6.4. HR App intra-application integration > 4.7. Glossary -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-4687) Add attributes value and type for script tag in screen, form. Default type is groovy and value can be a little script.
[ https://issues.apache.org/jira/browse/OFBIZ-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-4687. - Resolution: Abandoned > Add attributes value and type for script tag in screen, form. Default type is > groovy and value can be a little script. > -- > > Key: OFBIZ-4687 > URL: https://issues.apache.org/jira/browse/OFBIZ-4687 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Attachments: OFBIZ-4687.patch, OFBIZ-4687_withExpression.patch > > > this enhancement can be usefull for branch 20120209RemoveBsh > and for trunk, to avoid very small groovy file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10303: --- Attachment: (was: OFBIZ-10303-Documented-Add-a-Global-Glossary-for-user-documentat.patch) > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Attachments: > OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10303: --- Attachment: OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Attachments: > OFBIZ-10303_Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195448#comment-17195448 ] Olivier Heintz commented on OFBIZ-10303: New patch is done with git format-patch (apply it with git am) [^OFBIZ-10303-Documented-Add-a-Global-Glossary-for-user-documentat.patch] Add the global-glossary and use it in two place. > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Attachments: > OFBIZ-10303-Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10303) Add a Global Glossary for Documentation Guides
[ https://issues.apache.org/jira/browse/OFBIZ-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-10303: --- Attachment: OFBIZ-10303-Documented-Add-a-Global-Glossary-for-user-documentat.patch > Add a Global Glossary for Documentation Guides > -- > > Key: OFBIZ-10303 > URL: https://issues.apache.org/jira/browse/OFBIZ-10303 > Project: OFBiz > Issue Type: Task >Reporter: Olivier Heintz >Priority: Minor > Attachments: > OFBIZ-10303-Documented-Add-a-Global-Glossary-for-user-documentat.patch, > humanres.adoc.patch, ofbiz-glossary.adoc, ofbiz-glossary.adoc, > ofbiz-glossary.adoc, user-manual.adoc.patch > > > Create a ofbiz-glossary.adoc in _include directory at the top level (near > user-manual.adoc and developer-manual.adoc) > This file will be used for all terms which are global to ofbiz (not link to a > component). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11036) User Manual : change the level of from 2 to 1
[
https://issues.apache.org/jira/browse/OFBIZ-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17194651#comment-17194651
]
Olivier Heintz commented on OFBIZ-11036:
patch is done with git format-patch (apply it with git am)
[^0001-Documented-User-Manual-change-the-level-of-Core-Busi.patch]
I will give a link to the html result in a few days, so that you can see the
result
> User Manual : change the level of from 2 to 1
> --
>
> Key: OFBIZ-11036
> URL: https://issues.apache.org/jira/browse/OFBIZ-11036
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Kaustubh Choudhary
>Priority: Minor
> Attachments:
> 0001-Documented-User-Manual-change-the-level-of-Core-Busi.patch
>
>
> If is on level 1, it become a main separator in
> TOC not a chapter
> TOC become
> {code:java}
> ...
> 2. Quick start
> Core Business Applications
> 3. Accounting
> 4. Human Resources
> {code}
> and so we have one more level (in TOC) for each application
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-11036) User Manual : change the level of from 2 to 1
[
https://issues.apache.org/jira/browse/OFBIZ-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz updated OFBIZ-11036:
---
Attachment: 0001-Documented-User-Manual-change-the-level-of-Core-Busi.patch
> User Manual : change the level of from 2 to 1
> --
>
> Key: OFBIZ-11036
> URL: https://issues.apache.org/jira/browse/OFBIZ-11036
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Assignee: Kaustubh Choudhary
>Priority: Minor
> Attachments:
> 0001-Documented-User-Manual-change-the-level-of-Core-Busi.patch
>
>
> If is on level 1, it become a main separator in
> TOC not a chapter
> TOC become
> {code:java}
> ...
> 2. Quick start
> Core Business Applications
> 3. Accounting
> 4. Human Resources
> {code}
> and so we have one more level (in TOC) for each application
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11587) Migration all docbook file to asciidoc
[ https://issues.apache.org/jira/browse/OFBIZ-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193626#comment-17193626 ] Olivier Heintz commented on OFBIZ-11587: Jacques, I think it's corrected with the last commit, the problem was the comment characters use in the tag line (in asciidoctor file it is // not #) This tag is used in unit-test.adoc, and I have corrected it too because I had forgot the leveloffset to have correct paragraph level in developer.adoc Thank you for your remark > Migration all docbook file to asciidoc > -- > > Key: OFBIZ-11587 > URL: https://issues.apache.org/jira/browse/OFBIZ-11587 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS, ALL PLUGINS >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Labels: documentation > Time Spent: 40m > Remaining Estimate: 0h > > Umbrella task, for all components migration tasks. > Idea is to have only one branch/PR for all tasks, with one commit per > component / sub-component migration, it will be more easy to merge it when it > will be finish -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11581) Party Docbook help file migration to asciidoc format
[ https://issues.apache.org/jira/browse/OFBIZ-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-11581. -- Resolution: Fixed > Party Docbook help file migration to asciidoc format > > > Key: OFBIZ-11581 > URL: https://issues.apache.org/jira/browse/OFBIZ-11581 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: documentation > Time Spent: 20m > Remaining Estimate: 0h > > Migrate all Help files in docbook format to asciidoc format and include them > in a global party.adoc document. > party.adoc follow the template describe in Example structure for adoc files > in the wiki > [https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11580) Order Docbook help file migration to asciidoc format
[ https://issues.apache.org/jira/browse/OFBIZ-11580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-11580. -- Resolution: Fixed > Order Docbook help file migration to asciidoc format > > > Key: OFBIZ-11580 > URL: https://issues.apache.org/jira/browse/OFBIZ-11580 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: documentation > > Migrate all Help files in docbook format to asciidoc format and include them > in a global order.adoc document. > order.adoc follow the template describe in Example structure for adoc files > in the wiki > [https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11577) Marketink Docbook help file migration to asciidoc format
[ https://issues.apache.org/jira/browse/OFBIZ-11577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-11577. -- Resolution: Fixed > Marketink Docbook help file migration to asciidoc format > > > Key: OFBIZ-11577 > URL: https://issues.apache.org/jira/browse/OFBIZ-11577 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: documentation > Time Spent: 10m > Remaining Estimate: 0h > > Migrate all Help files in docbook format to asciidoc format and include them > in a global marketing.adoc document. > marketing.adoc follow the template describe in Example structure for adoc > files in the wiki > [https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11416) Manufacturing Docbook help file migration to asciidoc format
[ https://issues.apache.org/jira/browse/OFBIZ-11416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-11416. -- Resolution: Fixed > Manufacturing Docbook help file migration to asciidoc format > > > Key: OFBIZ-11416 > URL: https://issues.apache.org/jira/browse/OFBIZ-11416 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Olivier Heintz >Assignee: Olivier Heintz >Priority: Minor > Labels: documentation > > Migrate all Help files in docbook format to asciidoc format and include them > in a global manufacturing.adoc document. > manufacturing.adoc follow the template describe in Example structure for > adoc files in the wiki > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11803) showHelp not working
[ https://issues.apache.org/jira/browse/OFBIZ-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz closed OFBIZ-11803. -- Resolution: Fixed Thank you James, it works it help me to continue migration to new help system > showHelp not working > > > Key: OFBIZ-11803 > URL: https://issues.apache.org/jira/browse/OFBIZ-11803 > Project: OFBiz > Issue Type: Bug > Components: framework/common >Affects Versions: Upcoming Branch >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > > Navigation tree is not displayed in showHelp -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11803) showHelp not working
[ https://issues.apache.org/jira/browse/OFBIZ-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139427#comment-17139427 ] Olivier Heintz commented on OFBIZ-11803: # on https://demo-trunk.ofbiz.apache.org/humanres/control/main # click on help button # help window open # click on index button (top left of the window) # Navigate content is empty and in browser dev-tools in console there is the error message hoping it's clear I have tested after your last commit (for this Jira) and it was working > showHelp not working > > > Key: OFBIZ-11803 > URL: https://issues.apache.org/jira/browse/OFBIZ-11803 > Project: OFBiz > Issue Type: Bug > Components: framework/common >Affects Versions: Upcoming Branch >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > > Navigation tree is not displayed in showHelp -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-11803) showHelp not working
[
https://issues.apache.org/jira/browse/OFBIZ-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139209#comment-17139209
]
Olivier Heintz edited comment on OFBIZ-11803 at 6/18/20, 8:23 AM:
--
Hi,
Index Tree is not working/displayed.
There is an js error
{quote}TypeError: jQuery(...).jstree is not a function
createTree
[https://demo-trunk.ofbiz.apache.org/humanres/control/getJs?name=DisplayContentNav:746]
jQuery 2
{quote}
I have trying to find why, by comparing with other working usage of tree, but
without success
was (Author: holivier):
Hi,
Index Tree is not working/show.
There is an js error
{quote}TypeError: jQuery(...).jstree is not a function
createTree
https://demo-trunk.ofbiz.apache.org/humanres/control/getJs?name=DisplayContentNav:746
jQuery 2
{quote}
I have trying to find why, by comparing with other working usage of tree, but
without success
> showHelp not working
>
>
> Key: OFBIZ-11803
> URL: https://issues.apache.org/jira/browse/OFBIZ-11803
> Project: OFBiz
> Issue Type: Bug
> Components: framework/common
>Affects Versions: Upcoming Branch
>Reporter: James Yong
>Assignee: James Yong
>Priority: Minor
> Fix For: Trunk
>
>
> Navigation tree is not displayed in showHelp
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (OFBIZ-11803) showHelp not working
[
https://issues.apache.org/jira/browse/OFBIZ-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Heintz reopened OFBIZ-11803:
Hi,
Index Tree is not working/show.
There is an js error
{quote}TypeError: jQuery(...).jstree is not a function
createTree
https://demo-trunk.ofbiz.apache.org/humanres/control/getJs?name=DisplayContentNav:746
jQuery 2
{quote}
I have trying to find why, by comparing with other working usage of tree, but
without success
> showHelp not working
>
>
> Key: OFBIZ-11803
> URL: https://issues.apache.org/jira/browse/OFBIZ-11803
> Project: OFBiz
> Issue Type: Bug
> Components: framework/common
>Affects Versions: Upcoming Branch
>Reporter: James Yong
>Assignee: James Yong
>Priority: Minor
> Fix For: Trunk
>
>
> Navigation tree is not displayed in showHelp
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
