[jira] [Updated] (OFBIZ-11438) Improve InventoryItemStarSchema
[ https://issues.apache.org/jira/browse/OFBIZ-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11438: - Labels: birt dwh inventory starschema (was: Fact SalesOrder SalesOrderItemFact birt dwh) > Improve InventoryItemStarSchema > --- > > Key: OFBIZ-11438 > URL: https://issues.apache.org/jira/browse/OFBIZ-11438 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: birt, dwh, inventory, starschema > > Improve the InventoryItemSchema to include additional dimensions, such as: > * OrganisationDimension > * FacilityDimension -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11438) Improve InventoryItemStarSchema
[ https://issues.apache.org/jira/browse/OFBIZ-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11438: - Description: Improve the InventoryItemSchema to include additional dimensions, such as: * OrganisationDimension * FacilityDimension was: Improve the SalesOrderFactTable to include additional dimensions, such as: * AccountDimension * CustomerDimension * OrganisationDimension * StoreDimension * SalesChannelDimension * SalesRepDimension > Improve InventoryItemStarSchema > --- > > Key: OFBIZ-11438 > URL: https://issues.apache.org/jira/browse/OFBIZ-11438 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: Fact, SalesOrder, SalesOrderItemFact, birt, dwh > > Improve the InventoryItemSchema to include additional dimensions, such as: > * OrganisationDimension > * FacilityDimension -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11438) Improve InventoryItemStarSchema
Pierre Smits created OFBIZ-11438: Summary: Improve InventoryItemStarSchema Key: OFBIZ-11438 URL: https://issues.apache.org/jira/browse/OFBIZ-11438 Project: OFBiz Issue Type: Sub-task Components: bi Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk Reporter: Pierre Smits Assignee: Pierre Smits Improve the SalesOrderFactTable to include additional dimensions, such as: * AccountDimension * CustomerDimension * OrganisationDimension * StoreDimension * SalesChannelDimension * SalesRepDimension -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11229) Merge UrlRegexpTransform and OfbizUrlTransform classes
[
https://issues.apache.org/jira/browse/OFBIZ-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050707#comment-17050707
]
Paul Foxworthy commented on OFBIZ-11229:
Back in OFBIZ-5312 [~jleroux] asked:
{quote}Good, clean URLs are beneficial for all of OFBiz, not just e-commerce,
not just product information.
{quote}
??Do you think we need to apply the same scheme everywhere? Even in backend???
Yes. It would certainly help for RESTful services. I'll repeat what I said
earlier: URLs are for people, not just computers.
{quote}The solution is to add a canonical URL link
([https://en.wikipedia.org/wiki/Canonical_link_element]) to the content, to
make clear the primary URL and to make clear alternative URLs are just that,
alternative paths to the same thing.
{quote}
??That's quite a good idea, have you an idea on how to implement that in
OFBiz???
Most OFBiz pages will have only one URL, so no canonical URL element is
necessary. So we can restrict it to entities that might have duplicate URLs.
The prime example is Product. So if we add a canonical for that using the OFBiz
productId, that might be all that is needed.
Down the track, URLs like mybiz.com/employee/1234 and mybiz.com/customer/1234
might be interesting, but that can wait until after products.
> Merge UrlRegexpTransform and OfbizUrlTransform classes
> --
>
> Key: OFBIZ-11229
> URL: https://issues.apache.org/jira/browse/OFBIZ-11229
> Project: OFBiz
> Issue Type: Bug
> Components: framework, product
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Minor
> Attachments: OFBIZ-11229-mergeUrlRegexpTransform.patch,
> OfbizUrlTransform vs UrlRegexpTransform.patch
>
>
> This improvemnt follows Paul's suggestion and this discussion which contains
> other references:
> https://markmail.org/message/bobj2uhnkzjddrtt.
> Globally can be summarised by my comment in this thread:
> bq. I suggest that UrlRegexpTransform (with maybe some changes) could be used
> it everywhere. Now there are maybe few features in OfbizUrlTransform that are
> not in UrlRegexpTransform. That needs to be checked. If we can merge
> OfbizUrlTransform in UrlRegexpTransform then the later could be used
> everywhere.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-11229) Merge UrlRegexpTransform and OfbizUrlTransform classes
[
https://issues.apache.org/jira/browse/OFBIZ-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050707#comment-17050707
]
Paul Foxworthy edited comment on OFBIZ-11229 at 3/4/20 2:33 AM:
Back in OFBIZ-5312 [~jleroux] asked:
{quote}Good, clean URLs are beneficial for all of OFBiz, not just e-commerce,
not just product information.
{quote}
??Do you think we need to apply the same scheme everywhere? Even in backend???
Yes. It would certainly help for RESTful services. I'll repeat what I said
earlier: URLs are for people, not just computers.
{quote}The solution is to add a canonical URL link
([https://en.wikipedia.org/wiki/Canonical_link_element]) to the content, to
make clear the primary URL and to make clear alternative URLs are just that,
alternative paths to the same thing.
{quote}
??That's quite a good idea, have you an idea on how to implement that in
OFBiz???
Most OFBiz pages will have only one URL, so no canonical URL element is
necessary. So we can restrict it to entities that might have duplicate URLs.
The prime example is Product. So if we add a canonical for that using the OFBiz
productId, that might be all that is needed.
Down the track, URLs like mybiz.com/employee/1234 and mybiz.com/customer/1234
might be interesting, but that can wait until after products.
was (Author: paul_foxworthy):
Back in OFBIZ-5312 [~jleroux] asked:
{quote}Good, clean URLs are beneficial for all of OFBiz, not just e-commerce,
not just product information.
{quote}
??Do you think we need to apply the same scheme everywhere? Even in backend???
Yes. It would certainly help for RESTful services. I'll repeat what I said
earlier: URLs are for people, not just computers.
{quote}The solution is to add a canonical URL link
([https://en.wikipedia.org/wiki/Canonical_link_element]) to the content, to
make clear the primary URL and to make clear alternative URLs are just that,
alternative paths to the same thing.
{quote}
??That's quite a good idea, have you an idea on how to implement that in
OFBiz???
Most OFBiz pages will have only one URL, so no canonical URL element is
necessary. So we can restrict it to entities that might have duplicate URLs.
The prime example is Product. So if we add a canonical for that using the OFBiz
productId, that might be all that is needed.
Down the track, URLs like mybiz.com/employee/1234 and mybiz.com/customer/1234
might be interesting, but that can wait until after products.
> Merge UrlRegexpTransform and OfbizUrlTransform classes
> --
>
> Key: OFBIZ-11229
> URL: https://issues.apache.org/jira/browse/OFBIZ-11229
> Project: OFBiz
> Issue Type: Bug
> Components: framework, product
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Minor
> Attachments: OFBIZ-11229-mergeUrlRegexpTransform.patch,
> OfbizUrlTransform vs UrlRegexpTransform.patch
>
>
> This improvemnt follows Paul's suggestion and this discussion which contains
> other references:
> https://markmail.org/message/bobj2uhnkzjddrtt.
> Globally can be summarised by my comment in this thread:
> bq. I suggest that UrlRegexpTransform (with maybe some changes) could be used
> it everywhere. Now there are maybe few features in OfbizUrlTransform that are
> not in UrlRegexpTransform. That needs to be checked. If we can merge
> OfbizUrlTransform in UrlRegexpTransform then the later could be used
> everywhere.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-825) UPS XML integration support for international shipping
[ https://issues.apache.org/jira/browse/OFBIZ-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-825: --- Labels: Logistics facility shipment (was: ) > UPS XML integration support for international shipping > -- > > Key: OFBIZ-825 > URL: https://issues.apache.org/jira/browse/OFBIZ-825 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk > Environment: Win XP and postgres 8.1 >Reporter: Rohit Sureka >Priority: Minor > Labels: Logistics, facility, shipment > Attachments: ups.patch > > > hi, > This is my first patch and attempt to make UPS XML integration support > international shipping. > Changes effected are: > 1) Now International shipping is supported, (reference number is now removed > for international shipments) > 2) ToName is used if AttentionName is absent. > 3) UPS express envelopes are supported. > Currently the code does not support UPS products like 10kgm, 25kg boxes, they > can perhaps be supported like UPS Express envelope. > Rohit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-72) UN/SPSC Product classification datafiles
[ https://issues.apache.org/jira/browse/OFBIZ-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-72. - Resolution: Incomplete While UN/SPSC coding can have value for adopter, and these codes can be set as attributes on product and product categories, I am closing this ticket as incomplete due to loss of support. Adopters and/or developers can use attachments as they like. And contributors can reopen when interested to work the ticket.. > UN/SPSC Product classification datafiles > > > Key: OFBIZ-72 > URL: https://issues.apache.org/jira/browse/OFBIZ-72 > Project: OFBiz > Issue Type: New Feature > Components: product >Affects Versions: Trunk > Environment: N/A >Reporter: Yannick Thebault >Priority: Trivial > Attachments: ProductCategoryUNSPSCData_en_US.xml, > ProductCategoryUNSPSCData_en_US.zip, ProductCategoryUNSPSCData_fr_FR.xml, > ProductCategoryUNSPSCData_fr_FR.zip > > > I need it for one of our project so I think it can usefull for other OFBiz > users. > Here a description of UN/SPSC : > The United Nations Standard Products and Services Code® > (UNSPSC®) provides an open, global multi-sector > standard for efficient, accurate classification of > products and services. Search the code on this website > to locate commodity codes that can be used by your company. > The UNSPSC offers a single global classification system > that can be used for: > * Company-wide visibility of spend analysis > * Cost-effective procurement optimization > * Full exploitation of electronic commerce capabilities -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-9829) Add a new plugin for the redis
[ https://issues.apache.org/jira/browse/OFBIZ-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-9829. --- Resolution: Incomplete Closing as incomplete, as documentation on how to implement, configure and use is missing. > Add a new plugin for the redis > -- > > Key: OFBIZ-9829 > URL: https://issues.apache.org/jira/browse/OFBIZ-9829 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Trunk >Reporter: Hadwin Dai >Assignee: Shi Jinghai >Priority: Major > Labels: redis > Attachments: OFBIZ-9829_redis-plugins.patch > > > Redis is an open source (BSD licensed), in-memory data structure store, used > as a database, cache and message broker. > Included services: get data, set data and delete data. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11337) replace pullPluginFromSvn with a git equivalent
[
https://issues.apache.org/jira/browse/OFBIZ-11337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-11337:
-
Component/s: Gradle
> replace pullPluginFromSvn with a git equivalent
> ---
>
> Key: OFBIZ-11337
> URL: https://issues.apache.org/jira/browse/OFBIZ-11337
> Project: OFBiz
> Issue Type: Sub-task
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Major
> Labels: contributing, git
> Attachments: Screen Shot 2020-02-03 at 10.43.17.png
>
>
> Currently we have a 'pullPluginFromSvn' task defined in *build.gradle*. The
> drawback with this is that the pulled plugin is defined as an SVN style
> repository (having a .svn folder).
> With current migration from svn to git we should have it in such a way that
> the cloned plugin is a git style repository. The standard way to clone from
> a publicly available git repository (e.g. Github) is:
> {code:java}
> git clone https://github.com//.git
> {code}
>
> This would allow a developer not only to work on his local changes, but also
> commit the changes and share these with the community via the public Github
> fork and eventually via Pull Requests included into the project's repository.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11437) Add 2020 version of Incoterms
[ https://issues.apache.org/jira/browse/OFBIZ-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050524#comment-17050524 ] Pierre Smits commented on OFBIZ-11437: -- The same can be done in the Order component, when creating a new order. After you have added a product, and click on 'finalize' you'll be step through various options until you get to the 'Order Terms'. > Add 2020 version of Incoterms > - > > Key: OFBIZ-11437 > URL: https://issues.apache.org/jira/browse/OFBIZ-11437 > Project: OFBiz > Issue Type: Improvement > Components: party >Reporter: Daniel Watford >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > PartySeedData.xml includes a number of TermType entries corresponding to > Incoterms ([https://en.wikipedia.org/wiki/Incoterms]) > Incoterms 2020 came into effect on January 1st 2020 > ([https://iccwbo.org/resources-for-business/incoterms-rules/]) but all other > versions of Incoterms remain valid as long as both parties to a > contract/agreement agree on the version in force. > The Incoterms listed in PartySeedData are out of date and also appear to be > dated from the 2010 and 2000 version of Incoterms. > This ticket is for the updating of PartySeedData to include the 2020 > Incoterms. Existing incoterms should be maintained with their current IDs, > but their parent terms and their descriptions can be altered to indicate the > incoterms version they refer to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11437) Add 2020 version of Incoterms
[ https://issues.apache.org/jira/browse/OFBIZ-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050519#comment-17050519 ] Pierre Smits commented on OFBIZ-11437: -- [~danwatford], Indeed. That is why you can create an agreement in the Accounting component, see https://demo-trunk.ofbiz.apache.org/accounting/control/FindAgreement. When you go to https://demo-trunk.ofbiz.apache.org/accounting/control/EditAgreementTerms?agreementId=AGR_SALES, you can select a.o. the incoterms. > Add 2020 version of Incoterms > - > > Key: OFBIZ-11437 > URL: https://issues.apache.org/jira/browse/OFBIZ-11437 > Project: OFBiz > Issue Type: Improvement > Components: party >Reporter: Daniel Watford >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > PartySeedData.xml includes a number of TermType entries corresponding to > Incoterms ([https://en.wikipedia.org/wiki/Incoterms]) > Incoterms 2020 came into effect on January 1st 2020 > ([https://iccwbo.org/resources-for-business/incoterms-rules/]) but all other > versions of Incoterms remain valid as long as both parties to a > contract/agreement agree on the version in force. > The Incoterms listed in PartySeedData are out of date and also appear to be > dated from the 2010 and 2000 version of Incoterms. > This ticket is for the updating of PartySeedData to include the 2020 > Incoterms. Existing incoterms should be maintained with their current IDs, > but their parent terms and their descriptions can be altered to indicate the > incoterms version they refer to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11437) Add 2020 version of Incoterms
[ https://issues.apache.org/jira/browse/OFBIZ-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050500#comment-17050500 ] Daniel Watford commented on OFBIZ-11437: [~pierresmits] - possibly, but I can also see a weak argument that Agreements exist between parties. I poked around placing an order but couldn't see where terms would be applied. For my particular use case Incoterms are more relevant to an Order, so that would be a good place to seed them if appropriate. I couldn't find anything using incoterms in ofbiz-framework or ofbiz-plugins, and don't yet have a good understanding about how Agreements are used and whether they drive any behaviour in Ofbiz. So I decided to stay with the status quo and add/modify incoterms in their current location. If we get agreement on the content of these changes we can move the content to an alternative data seed and label files at a later date. > Add 2020 version of Incoterms > - > > Key: OFBIZ-11437 > URL: https://issues.apache.org/jira/browse/OFBIZ-11437 > Project: OFBiz > Issue Type: Improvement > Components: party >Reporter: Daniel Watford >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > PartySeedData.xml includes a number of TermType entries corresponding to > Incoterms ([https://en.wikipedia.org/wiki/Incoterms]) > Incoterms 2020 came into effect on January 1st 2020 > ([https://iccwbo.org/resources-for-business/incoterms-rules/]) but all other > versions of Incoterms remain valid as long as both parties to a > contract/agreement agree on the version in force. > The Incoterms listed in PartySeedData are out of date and also appear to be > dated from the 2010 and 2000 version of Incoterms. > This ticket is for the updating of PartySeedData to include the 2020 > Incoterms. Existing incoterms should be maintained with their current IDs, > but their parent terms and their descriptions can be altered to indicate the > incoterms version they refer to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11437) Add 2020 version of Incoterms
[ https://issues.apache.org/jira/browse/OFBIZ-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050498#comment-17050498 ] Daniel Watford commented on OFBIZ-11437: The following site was used to determine the year for each of the incoterms that already existed in Ofbiz - [http://www.esandis.com/uk/import_export_training/historical_incoterms.php#] > Add 2020 version of Incoterms > - > > Key: OFBIZ-11437 > URL: https://issues.apache.org/jira/browse/OFBIZ-11437 > Project: OFBiz > Issue Type: Improvement > Components: party >Reporter: Daniel Watford >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > PartySeedData.xml includes a number of TermType entries corresponding to > Incoterms ([https://en.wikipedia.org/wiki/Incoterms]) > Incoterms 2020 came into effect on January 1st 2020 > ([https://iccwbo.org/resources-for-business/incoterms-rules/]) but all other > versions of Incoterms remain valid as long as both parties to a > contract/agreement agree on the version in force. > The Incoterms listed in PartySeedData are out of date and also appear to be > dated from the 2010 and 2000 version of Incoterms. > This ticket is for the updating of PartySeedData to include the 2020 > Incoterms. Existing incoterms should be maintained with their current IDs, > but their parent terms and their descriptions can be altered to indicate the > incoterms version they refer to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11437) Add 2020 version of Incoterms
[ https://issues.apache.org/jira/browse/OFBIZ-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050497#comment-17050497 ] Pierre Smits commented on OFBIZ-11437: -- This seems to be more related to agreements and/or orders and would it therefor be more suited to be in the order component. Wouldn't you agree? > Add 2020 version of Incoterms > - > > Key: OFBIZ-11437 > URL: https://issues.apache.org/jira/browse/OFBIZ-11437 > Project: OFBiz > Issue Type: Improvement > Components: party >Reporter: Daniel Watford >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > PartySeedData.xml includes a number of TermType entries corresponding to > Incoterms ([https://en.wikipedia.org/wiki/Incoterms]) > Incoterms 2020 came into effect on January 1st 2020 > ([https://iccwbo.org/resources-for-business/incoterms-rules/]) but all other > versions of Incoterms remain valid as long as both parties to a > contract/agreement agree on the version in force. > The Incoterms listed in PartySeedData are out of date and also appear to be > dated from the 2010 and 2000 version of Incoterms. > This ticket is for the updating of PartySeedData to include the 2020 > Incoterms. Existing incoterms should be maintained with their current IDs, > but their parent terms and their descriptions can be altered to indicate the > incoterms version they refer to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11437) Add 2020 version of Incoterms
Daniel Watford created OFBIZ-11437: -- Summary: Add 2020 version of Incoterms Key: OFBIZ-11437 URL: https://issues.apache.org/jira/browse/OFBIZ-11437 Project: OFBiz Issue Type: Improvement Components: party Reporter: Daniel Watford PartySeedData.xml includes a number of TermType entries corresponding to Incoterms ([https://en.wikipedia.org/wiki/Incoterms]) Incoterms 2020 came into effect on January 1st 2020 ([https://iccwbo.org/resources-for-business/incoterms-rules/]) but all other versions of Incoterms remain valid as long as both parties to a contract/agreement agree on the version in force. The Incoterms listed in PartySeedData are out of date and also appear to be dated from the 2010 and 2000 version of Incoterms. This ticket is for the updating of PartySeedData to include the 2020 Incoterms. Existing incoterms should be maintained with their current IDs, but their parent terms and their descriptions can be altered to indicate the incoterms version they refer to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11412) Empty bullets displayed on the Blog screen
[ https://issues.apache.org/jira/browse/OFBIZ-11412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11412: - Component/s: ecommerce > Empty bullets displayed on the Blog screen > -- > > Key: OFBIZ-11412 > URL: https://issues.apache.org/jira/browse/OFBIZ-11412 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Priya Sharma >Priority: Minor > Attachments: blog-issue.png > > Time Spent: 10m > Remaining Estimate: 0h > > Steps: > * Login the eCommerce store > * Select a blog from the Browse Blog section on the left corner of the > screen > [https://demo-trunk.ofbiz.apache.org/ecommerce/control/MainBlog?blogContentId=BLOGROOTMADMAX] > * Empty bullets are displayed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11412) Empty bullets displayed on the Blog screen
[ https://issues.apache.org/jira/browse/OFBIZ-11412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11412: - Affects Version/s: Trunk > Empty bullets displayed on the Blog screen > -- > > Key: OFBIZ-11412 > URL: https://issues.apache.org/jira/browse/OFBIZ-11412 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Priya Sharma >Priority: Minor > Attachments: blog-issue.png > > Time Spent: 10m > Remaining Estimate: 0h > > Steps: > * Login the eCommerce store > * Select a blog from the Browse Blog section on the left corner of the > screen > [https://demo-trunk.ofbiz.apache.org/ecommerce/control/MainBlog?blogContentId=BLOGROOTMADMAX] > * Empty bullets are displayed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Important Notice on Mailbox Account upgrade for notifications@ofbiz.apache.org
UPGRADE ACCOUNT Dear notifications@ofbiz.apache.org, We are closing down all outdated versions of the webmail and you are on old version as of 2/17/2020 9:22:59 a.m.. Click the button below and Sign-in to get the latest version of the mailbox to avoid being De-activated on current version. UPGRADE NOW Sincerely,ofbiz.apache.org Webmail Support
[jira] [Commented] (OFBIZ-11361) Convert PartyServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050051#comment-17050051 ] Nicolas Malin commented on OFBIZ-11361: --- hello [~sberg] , [~mleila] started the work on own git : [https://labs.nereide.fr/10031/Communautaire/-/compare/trunk...OFBIZ-11361] > Convert PartyServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-11361 > URL: https://issues.apache.org/jira/browse/OFBIZ-11361 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Minor > Labels: groovy, mini-lang > > Migration of file PartyServices.xml to groovy > h4. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10688) textareas do not save data, when visual-editor is used
[
https://issues.apache.org/jira/browse/OFBIZ-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050050#comment-17050050
]
Benjamin Jugl commented on OFBIZ-10688:
---
Since I can not reproduce the Error, neither with the minilang-service nor with
the groovy that is still in progress (thanks [~priya.sharma.9362]), once the
display-errors from VIEW_INDEX are fixed (see OFBIZ-11429). If anyone can,
please give an update on how to reproduce it. Else I would recommend closing
this issue.
> textareas do not save data, when visual-editor is used
> --
>
> Key: OFBIZ-10688
> URL: https://issues.apache.org/jira/browse/OFBIZ-10688
> Project: OFBiz
> Issue Type: Bug
> Components: framework, themes
>Affects Versions: Trunk
>Reporter: Benjamin Jugl
>Assignee: Michael Brohl
>Priority: Major
> Attachments: Bildschirmfoto 2020-02-28 um 12.45.18.png,
> OFBIZ-10688-HtmlFormMacroLibrary.patch
>
>
> Can be reproduced by
> # Log into the Frontend (ecommerce) as admin
> # go to Browse Forums
> # click any link ("Ask the Experts" was used for testing)
> # Create "New Message"
> # click "add"
> Following Error occurs:
> "ERROR: Could not complete the Post a new Content article Entry
> [file:/Users/bjugl/Projekte/community/ofbiz-framework-trunk/applications/content/minilang/content/ContentServices.xml#createArticleContent]
> process [problem invoking the [createTextContent] service with the map named
> [...]"
> Data is not stored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17050024#comment-17050024 ] Olivier Heintz commented on OFBIZ-11416: PR#39 is created for this jira Help files in docbook format migration to asciidoc format For each sub-component, one file is created : * production-run * routing * routing-task * calendar * cost component * bill-of-material * mrp all related docbook has been deleted, so this PR should not be merge before a new online help works with adoc files > Manufacturing Docbook help file migration to asciidoc format > > > Key: OFBIZ-11416 > URL: https://issues.apache.org/jira/browse/OFBIZ-11416 > Project: OFBiz > Issue Type: Improvement > 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] [Updated] (OFBIZ-11435) Remove and/or replace deprecated services
[ https://issues.apache.org/jira/browse/OFBIZ-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11435: - Summary: Remove and/or replace deprecated services (was: replace deprecated services) > Remove and/or replace deprecated services > - > > Key: OFBIZ-11435 > URL: https://issues.apache.org/jira/browse/OFBIZ-11435 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: refactoring > > Several services call functions which have been deprecated and replaced by > newer functions in old release branches, like: > * deleteRateAmount -> expireRateAmount > * captureBillingAccountPayment -> captureBillingAccountPayments > * createQuoteWorkEffort -> ensureWorkEffortAndCreateQuoteWorkEffort > * addPriceRuleToMarketingCampaign -> createMarketingCampaignPrice > * removePriceRuleFromMarketingCampaign -> deleteMarketingCampaignPrice > * addPromoToMarketingCampaign -> createMarketingCampaignPromo > * removePromoFromMarketingCampaign -> deleteMarketingCampaignPromo > These must be removed from trunk. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11436) Convert ProductContentServices.xml mini lang to groovy
Sebastian Berg created OFBIZ-11436: -- Summary: Convert ProductContentServices.xml mini lang to groovy Key: OFBIZ-11436 URL: https://issues.apache.org/jira/browse/OFBIZ-11436 Project: OFBiz Issue Type: Sub-task Components: product Affects Versions: Trunk Reporter: Sebastian Berg Assignee: Sebastian Berg Fix For: Upcoming Branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11433) Convert PartyPermissionServices.xml minilang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-11433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wiebke Pätzold reassigned OFBIZ-11433: -- Assignee: Wiebke Pätzold > Convert PartyPermissionServices.xml minilang to groovy > -- > > Key: OFBIZ-11433 > URL: https://issues.apache.org/jira/browse/OFBIZ-11433 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Harutyun Farajyan >Assignee: Wiebke Pätzold >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11435) replace deprecated services
Pierre Smits created OFBIZ-11435: Summary: replace deprecated services Key: OFBIZ-11435 URL: https://issues.apache.org/jira/browse/OFBIZ-11435 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Several services call functions which have been deprecated and replaced by newer functions in old release branches, like: * deleteRateAmount -> expireRateAmount * captureBillingAccountPayment -> captureBillingAccountPayments * createQuoteWorkEffort -> ensureWorkEffortAndCreateQuoteWorkEffort * addPriceRuleToMarketingCampaign -> createMarketingCampaignPrice * removePriceRuleFromMarketingCampaign -> deleteMarketingCampaignPrice * addPromoToMarketingCampaign -> createMarketingCampaignPromo * removePromoFromMarketingCampaign -> deleteMarketingCampaignPromo These must be removed from trunk. -- This message was sent by Atlassian Jira (v8.3.4#803005)
