[jira] [Comment Edited] (OFBIZ-10802) UserLoginPasswordHistory is not maintaining password as present in UserLogin.
[
https://issues.apache.org/jira/browse/OFBIZ-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023545#comment-17023545
]
Rohit Koushal edited comment on OFBIZ-10802 at 1/25/20 4:16 PM:
[~jleroux], records creation in that entity depends upon property
{color:#00875a}password.change.history.limit {color:#172b4d}and it allows only
when{color}{color}{color:#172b4d} that property is greater than 0.{color}
Here is the code block
!image-2020-01-25-18-30-57-571.png!
was (Author: rohit.koushal):
[~jleroux], records creation in that entity depends upon property
{color:#00875a}password.change.history.limit {color:#172b4d}and it allow only
when{color}{color:#172b4d} If that property is greater then 0.{color}{color}
{color:#00875a}{color:#172b4d}Here is the code block {color}{color}
{color:#00875a}{color:#172b4d}!image-2020-01-25-18-30-57-571.png!{color}{color}
> UserLoginPasswordHistory is not maintaining password as present in UserLogin.
> -
>
> Key: OFBIZ-10802
> URL: https://issues.apache.org/jira/browse/OFBIZ-10802
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk,
> Release Branch 15.12, 17.12.01, Release Branch 16.11, 16.11.04, 16.11.05,
> 16.11.06, Release Branch 17.12, Release Branch 18.12
>Reporter: Rohit Koushal
>Assignee: Suraj Khurana
>Priority: Major
> Attachments: OFBIZ-10802.patch, UL.png, ULPH.png,
> image-2020-01-25-18-30-57-571.png
>
>
> While maintaining UserLoginPasswordHistory in the system, the password is
> encrypted with the random salt hence it will not match with the password save
> in UserLogin. So we need to improve this area of code.
>
> Please refer below screenshots
> *UserLogin*
> *!UL.png!*
> *UserLoginPasswordHistory*
> *!ULPH.png!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11246) The createTaskContent request does not work
[
https://issues.apache.org/jira/browse/OFBIZ-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-11246:
---
Assignee: Jacques Le Roux (was: Ankush Upadhyay)
> The createTaskContent request does not work
> ---
>
> Key: OFBIZ-11246
> URL: https://issues.apache.org/jira/browse/OFBIZ-11246
> Project: OFBiz
> Issue Type: Bug
> Components: projectmgr, workeffort
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
>
> While working on OFBIZ-11123 I found that the createTaskContent request does
> not work.
> If you get to
> [https://demo-trunk.ofbiz.apache.org/projectmgr/control/EditTaskContents?workEffortId=9002]
> and enter values, the 1st error you get in log is
> {noformat}
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |UtilProperties
> |W| layoutEvents.no_files_uploaded is missing in ContentErrorUiLabels for
> locale en
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |UtilProperties
> |W| layoutEvents.no_files_uploaded is missing in ContentErrorUiLabels for
> locale en
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |ServiceUtil
> |E| {errorMessage=layoutEvents.no_files_uploaded, responseMessage=error}
> {noformat}
> The error above comes from LayoutWorker::uploadImageAndParameters with the
> below stack
> {noformat}
> org.apache.ofbiz.content.layout.LayoutWorker.uploadImageAndParameters(javax.servlet.http.HttpServletRequest,
> java.lang.String) line: 56
> sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method,
> java.lang.Object, java.lang.Object[]) line: not available [native method]
>
> sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) line: 62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) line: 43
> java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line:
> 498
> org.apache.ofbiz.minilang.MiniLangUtil.callMethod(org.apache.ofbiz.minilang.method.MethodOperation,
> org.apache.ofbiz.minilang.method.MethodContext,
> java.util.List>,
> java.lang.Class, java.lang.Object, java.lang.String,
> org.apache.ofbiz.base.util.collections.FlexibleMapAccessor)
> line: 131
> org.apache.ofbiz.minilang.method.callops.CallClassMethod.exec(org.apache.ofbiz.minilang.method.MethodContext)
> line: 93
> org.apache.ofbiz.minilang.SimpleMethod.runSubOps(java.util.List,
> org.apache.ofbiz.minilang.method.MethodContext) line: 310
> org.apache.ofbiz.minilang.SimpleMethod.exec(org.apache.ofbiz.minilang.method.MethodContext)
> line: 457
> org.apache.ofbiz.minilang.SimpleMethod.runSimpleMethod(java.lang.String,
> java.lang.String, org.apache.ofbiz.minilang.method.MethodContext) line: 274
> org.apache.ofbiz.minilang.SimpleMethod.runSimpleEvent(java.lang.String,
> java.lang.String, javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) line: 257
> org.apache.ofbiz.webapp.event.SimpleEventHandler.invoke(org.apache.ofbiz.webapp.control.ConfigXMLReader$Event,
> org.apache.ofbiz.webapp.control.ConfigXMLReader$RequestMap,
> javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) line: 70
> org.apache.ofbiz.webapp.control.RequestHandler.runEvent(javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse,
> org.apache.ofbiz.webapp.control.ConfigXMLReader$Event,
> org.apache.ofbiz.webapp.control.ConfigXMLReader$RequestMap, java.lang.String)
> line: 784
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse, java.lang.String,
> org.apache.ofbiz.entity.GenericValue, org.apache.ofbiz.entity.Delegator)
> line: 507
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) line: 212
> org.apache.ofbiz.webapp.control.ControlServlet.doPost(javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) line: 85
> org.apache.ofbiz.webapp.control.ControlServlet(javax.servlet.http.HttpServlet).service(javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) line: 665
> org.apache.ofbiz.webapp.control.ControlServlet(javax.servlet.http.HttpServlet).service(javax.servlet.ServletRequest,
> javax.servlet.ServletResponse) line: 750
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(javax.servlet.ServletRequest,
> javax.servlet.ServletResponse) line: 231
> org.apache.catalina.core.ApplicationFilterChain.doFilter(javax.servlet.ServletRequest,
> javax.servlet.ServletResponse) line: 166
>
[jira] [Comment Edited] (OFBIZ-11246) The createTaskContent request does not work
[
https://issues.apache.org/jira/browse/OFBIZ-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023544#comment-17023544
]
Jacques Le Roux edited comment on OFBIZ-11246 at 1/25/20 2:05 PM:
--
Thanks for sharing error logs [~jleroux],
I am able to replicate the same on latest trunk and also did my research around
it.
Here are the details:
-- *createWorkEffortContent* is being triggers on file upload, and the request
object is getting parsed using *ServletFileUpload* two times,
1. Inside UtilHttp.getMultiPartParameterMap() while making combined map object
from request object using method UtilHttp.getCombinedMap(request).
2. from *createWorkEffortContent* event, inside
LayoutWorker.uploadImageAndParameters()
So before calling *createWorkEffortContent* event, from #1, the uploaded file
is getting removed from the parse method on request object:
{code}
uploadedItems = UtilGenerics.cast(upload.parseRequest(request));
{code}
It seems that same request can not be parsed multiple times if it has multi
part object in it as the parse method remove it after that.
Found one stackoverflow link around the same:
[https://stackoverflow.com/questions/13881272/servletfileuploadparserequestrequest-returns-an-empty-list]
I believe that all places/uploads using this workflow should resulting the same
issue.
was (Author: ankush.upadhyay):
Thanks for sharing error logs [~jleroux],
I am able to replicate the same on latest trunk and also did my research around
it.
Here are the details:
-- *createWorkEffortContent* is being triggers on file upload, and the request
object is getting parsed using *ServletFileUpload* two times,
1. Inside UtilHttp.getMultiPartParameterMap() while making combined map object
from request object using method UtilHttp.getCombinedMap(request).
2. from *createWorkEffortContent* event, inside
LayoutWorker.uploadImageAndParameters()
So before calling *createWorkEffortContent* event, from #1, the uploaded file
is getting removed from the parse method on request object:
{code}
uploadedItems = UtilGenerics.cast(upload.parseRequest(request));
{code}
It seems that same request can not be parsed multiple times if it has multi
part object in it as the parse method remove it after that.
Found one stackoverflow link around the same:
[https://stackoverflow.com/questions/13881272/servletfileuploadparserequestrequest-returns-an-empty-list]
I believe that all places/uploads using this workflow should resulting the same
issue.
> The createTaskContent request does not work
> ---
>
> Key: OFBIZ-11246
> URL: https://issues.apache.org/jira/browse/OFBIZ-11246
> Project: OFBiz
> Issue Type: Bug
> Components: projectmgr, workeffort
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
>
> While working on OFBIZ-11123 I found that the createTaskContent request does
> not work.
> If you get to
> [https://demo-trunk.ofbiz.apache.org/projectmgr/control/EditTaskContents?workEffortId=9002]
> and enter values, the 1st error you get in log is
> {noformat}
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |UtilProperties
> |W| layoutEvents.no_files_uploaded is missing in ContentErrorUiLabels for
> locale en
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |UtilProperties
> |W| layoutEvents.no_files_uploaded is missing in ContentErrorUiLabels for
> locale en
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |ServiceUtil
> |E| {errorMessage=layoutEvents.no_files_uploaded, responseMessage=error}
> {noformat}
> The error above comes from LayoutWorker::uploadImageAndParameters with the
> below stack
> {noformat}
> org.apache.ofbiz.content.layout.LayoutWorker.uploadImageAndParameters(javax.servlet.http.HttpServletRequest,
> java.lang.String) line: 56
> sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method,
> java.lang.Object, java.lang.Object[]) line: not available [native method]
>
> sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) line: 62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) line: 43
> java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line:
> 498
> org.apache.ofbiz.minilang.MiniLangUtil.callMethod(org.apache.ofbiz.minilang.method.MethodOperation,
> org.apache.ofbiz.minilang.method.MethodContext,
> java.util.List>,
> java.lang.Class, java.lang.Object, java.lang.String,
> org.apache.ofbiz.base.util.collections.FlexibleMapAccessor)
> line: 131
> org.apache.ofbiz.minilang.method.callops.CallClassMethod.exec(org.apache.ofbiz.minilang.method.MethodContext)
> line: 93
>
[jira] [Updated] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10850: Fix Version/s: (was: Upcoming Branch) Thanks Akash, When we backport we don't put "Upcoming Branch" in "Fix Version/s" please refer to https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-ManageJIRA%27sissues > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Fix For: 17.12.01, 18.12.01 > > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-11325: --- Assignee: Jacques Le Roux (was: Humera Khan) > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Jacques Le Roux >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023563#comment-17023563 ] ASF subversion and git services commented on OFBIZ-11325: - Commit 6f3974169b8ef15613b213bd0cbfa6426cb38dd8 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=6f39741 ] Fixed: Fixed the issue on party page that will upload the data each time after refreshing the page. (OFBIZ-11325) Earlier 'view' response type is used on the request that cause the issue. We need to use request-redirect response type along with the required redirect-parameter instead of view response type, i.e. We need to request-redirect on viewProfile along with partyId as redirect-parameter. Thanks: Humera Khan > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Humera Khan >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[
https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023561#comment-17023561
]
Jacques Le Roux edited comment on OFBIZ-11325 at 1/25/20 1:40 PM:
--
Here is what I got:
{noformat}
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ git pull
Already up to date.
Current branch trunk is up to date.
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ patch -p0 < OFBIZ-11325.patch
patching file applications/party/webapp/partymgr/WEB-INF/controller.xml
Hunk #12 FAILED at 1028.
Hunk #13 succeeded at 1055 (offset 4 lines).
Hunk #14 succeeded at 1151 (offset 4 lines).
Hunk #15 succeeded at 1165 (offset 4 lines).
Hunk #16 succeeded at 1260 (offset 4 lines).
Hunk #17 succeeded at 1281 (offset 4 lines).
1 out of 17 hunks FAILED -- saving rejects to file
applications/party/webapp/partymgr/WEB-INF/controller.xml.rej
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ tail -n100 applications/party/webapp/partymgr/WEB-INF/controller.xml.rej
--- applications/party/webapp/partymgr/WEB-INF/controller.xml (revision
1873128)
+++ applications/party/webapp/partymgr/WEB-INF/controller.xml (working copy)
@@ -1028,8 +1066,12 @@
-
-
+
+
+
+
+
+
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
{noformat}
The reason is it was already applied for OFBIZ-11171, see:
[https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;a=commitdiff;h=2cb33566ab7807e7aaf49224aa64640cc11fb619]
If I remove
{noformat}
@@ -990,8 +1028,12 @@
-
-
+
+
+
+
+
+
{noformat}
>From your patch, it works. That's why I asked you to "git pull" and recreate
>the patch. Then we would not have had this issue, better to not mix patches ;)
OK I'll commit and backport... a bit later...
was (Author: jacques.le.roux):
Here is what I got:
{noformat}
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ git pull
Already up to date.
Current branch trunk is up to date.
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ patch -p0 < OFBIZ-11325.patch
patching file applications/party/webapp/partymgr/WEB-INF/controller.xml
Hunk #12 FAILED at 1028.
Hunk #13 succeeded at 1055 (offset 4 lines).
Hunk #14 succeeded at 1151 (offset 4 lines).
Hunk #15 succeeded at 1165 (offset 4 lines).
Hunk #16 succeeded at 1260 (offset 4 lines).
Hunk #17 succeeded at 1281 (offset 4 lines).
1 out of 17 hunks FAILED -- saving rejects to file
applications/party/webapp/partymgr/WEB-INF/controller.xml.rej
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ tail -n100 applications/party/webapp/partymgr/WEB-INF/controller.xml.rej
--- applications/party/webapp/partymgr/WEB-INF/controller.xml (revision
1873128)
+++ applications/party/webapp/partymgr/WEB-INF/controller.xml (working copy)
@@ -1028,8 +1066,12 @@
-
-
+
+
+
+
+
+
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
{noformat}
The reason is it was already applied for OFBIZ-11171, see:
[https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;a=commitdiff;h=2cb33566ab7807e7aaf49224aa64640cc11fb619]
If I remove
{noformat}
@@ -990,8 +1028,12 @@
-
-
+
+
+
+
+
+
{noformat}
>From your patch, it works. That's why I asked you to "git pull" and recreate
>the patch. Then we would not have had this issue ;)
OK I'll commit and backport... a bit later...
> Fixed the issue on party page that will upload the data each time after
> refreshing the page.
>
>
> Key: OFBIZ-11325
> URL: https://issues.apache.org/jira/browse/OFBIZ-11325
> Project: OFBiz
> Issue Type: Sub-task
> Components: party
>Affects Versions: Trunk
>Reporter: Humera Khan
>Assignee: Humera Khan
>Priority: Major
> Fix For: Trunk
>
> Attachments: OFBIZ-11325.patch
>
>
> Please refer OFBIZ-11171
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[
https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023561#comment-17023561
]
Jacques Le Roux commented on OFBIZ-11325:
-
Here is what I got:
{noformat}
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ git pull
Already up to date.
Current branch trunk is up to date.
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ patch -p0 < OFBIZ-11325.patch
patching file applications/party/webapp/partymgr/WEB-INF/controller.xml
Hunk #12 FAILED at 1028.
Hunk #13 succeeded at 1055 (offset 4 lines).
Hunk #14 succeeded at 1151 (offset 4 lines).
Hunk #15 succeeded at 1165 (offset 4 lines).
Hunk #16 succeeded at 1260 (offset 4 lines).
Hunk #17 succeeded at 1281 (offset 4 lines).
1 out of 17 hunks FAILED -- saving rejects to file
applications/party/webapp/partymgr/WEB-INF/controller.xml.rej
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
$ tail -n100 applications/party/webapp/partymgr/WEB-INF/controller.xml.rej
--- applications/party/webapp/partymgr/WEB-INF/controller.xml (revision
1873128)
+++ applications/party/webapp/partymgr/WEB-INF/controller.xml (working copy)
@@ -1028,8 +1066,12 @@
-
-
+
+
+
+
+
+
Jacques@LDLC MINGW64 /c/projectsASF/Git/ofbiz-framework (trunk)
{noformat}
The reason is it was already applied for OFBIZ-11171, see:
[https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;a=commitdiff;h=2cb33566ab7807e7aaf49224aa64640cc11fb619]
If I remove
{noformat}
@@ -990,8 +1028,12 @@
-
-
+
+
+
+
+
+
{noformat}
>From your patch, it works. That's why I asked you to "git pull" and recreate
>the patch. Then we would not have had this issue ;)
OK I'll commit and backport... a bit later...
> Fixed the issue on party page that will upload the data each time after
> refreshing the page.
>
>
> Key: OFBIZ-11325
> URL: https://issues.apache.org/jira/browse/OFBIZ-11325
> Project: OFBiz
> Issue Type: Sub-task
> Components: party
>Affects Versions: Trunk
>Reporter: Humera Khan
>Assignee: Humera Khan
>Priority: Major
> Fix For: Trunk
>
> Attachments: OFBIZ-11325.patch
>
>
> Please refer OFBIZ-11171
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain closed OFBIZ-10850. -- Resolution: Fixed > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Fix For: 17.12.01, Upcoming Branch, 18.12.01 > > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain updated OFBIZ-10850: --- Fix Version/s: (was: Release Branch 18.12) (was: Release Branch 17.12) 18.12.01 17.12.01 > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Fix For: 17.12.01, Upcoming Branch, 18.12.01 > > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023550#comment-17023550 ] Yashwant Dhakad commented on OFBIZ-10577: - I have prevented the inbound and outbound transactions and uploaded the latest patch for these changes. I have added database changes form earlier patch as well so all the changes of this feature available in OFBIZ-10577.patch. Please have a look and let me know if you found any issues or improvements. > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive >
[jira] [Updated] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain updated OFBIZ-10850: --- Fix Version/s: Release Branch 18.12 Release Branch 17.12 Upcoming Branch > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Fix For: Upcoming Branch, Release Branch 17.12, Release Branch > 18.12 > > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10577: Attachment: (was: OFBIZ-10577.patch) > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive > Issuance and return inventory in manufacturing Job > Kit breakup > Update Location > Physical Variance creation > The locked locations won’t have any bearing on the transactions that are > affecting the only ATP of parts i.e. Reserving component for Jobs/Sales > Orders etc. as they don’t affect QOH
[jira] [Comment Edited] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023548#comment-17023548 ] Akash Jain edited comment on OFBIZ-10850 at 1/25/20 1:16 PM: - This issue has been fixed at: Trunk: 61ad77166b636ff818670e0b56c1c1e30ec71a31 R18: 3045557f3212f2e199233abc7e2d4d0b3096d431 R17: 224d2f67b8d7e3f8eea73496945b99024cd8a898 Thanks, [~ashish.sharma] and [~ankush.upadhyay] for your contribution. was (Author: akash.jain): This issue fixed at: Trunk: 61ad77166b636ff818670e0b56c1c1e30ec71a31 R18: 3045557f3212f2e199233abc7e2d4d0b3096d431 > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10577: Attachment: (was: OFBIZ-10577.patch) > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > OFBIZ-10577.patch > > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive > Issuance and return inventory in manufacturing Job > Kit breakup > Update Location > Physical Variance creation > The locked locations won’t have any bearing on the transactions that are > affecting the only ATP of parts i.e. Reserving component for Jobs/Sales > Orders etc. as
[jira] [Updated] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10577: Attachment: OFBIZ-10577.patch > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > OFBIZ-10577.patch > > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive > Issuance and return inventory in manufacturing Job > Kit breakup > Update Location > Physical Variance creation > The locked locations won’t have any bearing on the transactions that are > affecting the only ATP of parts i.e. Reserving component for Jobs/Sales > Orders etc. as they don’t
[jira] [Updated] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10577: Attachment: OFBIZ-10577.patch > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > OFBIZ-10577.patch > > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive > Issuance and return inventory in manufacturing Job > Kit breakup > Update Location > Physical Variance creation > The locked locations won’t have any bearing on the transactions that are > affecting the only ATP of parts i.e. Reserving component for Jobs/Sales > Orders etc. as they don’t
[jira] [Commented] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023548#comment-17023548 ] Akash Jain commented on OFBIZ-10850: This issue fixed at: Trunk: 61ad77166b636ff818670e0b56c1c1e30ec71a31 R18: 3045557f3212f2e199233abc7e2d4d0b3096d431 > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023547#comment-17023547 ] ASF subversion and git services commented on OFBIZ-10850: - Commit 3045557f3212f2e199233abc7e2d4d0b3096d431 in ofbiz-plugins's branch refs/heads/release18.12 from akash [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=3045557 ] Fixed: User is unable to create return. (OFBIZ-10850) Thanks, Ashish and Ankush Upadhyay for your contribution. > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023546#comment-17023546 ] ASF subversion and git services commented on OFBIZ-10850: - Commit 224d2f67b8d7e3f8eea73496945b99024cd8a898 in ofbiz-plugins's branch refs/heads/release17.12 from akash [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=224d2f6 ] Fixed: User is unable to create return. (OFBIZ-10850) Thanks, Ashish and Ankush Upadhyay for your contribution. > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10802) UserLoginPasswordHistory is not maintaining password as present in UserLogin.
[
https://issues.apache.org/jira/browse/OFBIZ-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023545#comment-17023545
]
Rohit Koushal commented on OFBIZ-10802:
---
[~jleroux], records creation in that entity depends upon property
{color:#00875a}password.change.history.limit {color:#172b4d}and it allow only
when{color}{color:#172b4d} If that property is greater then 0.{color}{color}
{color:#00875a}{color:#172b4d}Here is the code block {color}{color}
{color:#00875a}{color:#172b4d}!image-2020-01-25-18-30-57-571.png!{color}{color}
> UserLoginPasswordHistory is not maintaining password as present in UserLogin.
> -
>
> Key: OFBIZ-10802
> URL: https://issues.apache.org/jira/browse/OFBIZ-10802
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk,
> Release Branch 15.12, 17.12.01, Release Branch 16.11, 16.11.04, 16.11.05,
> 16.11.06, Release Branch 17.12, Release Branch 18.12
>Reporter: Rohit Koushal
>Assignee: Suraj Khurana
>Priority: Major
> Attachments: OFBIZ-10802.patch, UL.png, ULPH.png,
> image-2020-01-25-18-30-57-571.png
>
>
> While maintaining UserLoginPasswordHistory in the system, the password is
> encrypted with the random salt hence it will not match with the password save
> in UserLogin. So we need to improve this area of code.
>
> Please refer below screenshots
> *UserLogin*
> *!UL.png!*
> *UserLoginPasswordHistory*
> *!ULPH.png!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11246) The createTaskContent request does not work
[
https://issues.apache.org/jira/browse/OFBIZ-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023544#comment-17023544
]
Ankush Upadhyay commented on OFBIZ-11246:
-
Thanks for sharing error logs [~jleroux],
I am able to replicate the same on latest trunk and also did my research around
it.
Here are the details:
-- *createWorkEffortContent* is being triggers on file upload, and the request
object is getting parsed using *ServletFileUpload* two times,
1. Inside UtilHttp.getMultiPartParameterMap() while making combined map object
from request object using method UtilHttp.getCombinedMap(request).
2. from *createWorkEffortContent* event, inside
LayoutWorker.uploadImageAndParameters()
So before calling *createWorkEffortContent* event, from #1, the uploaded file
is getting removed from the parse method on request object:
{code}
uploadedItems = UtilGenerics.cast(upload.parseRequest(request));
{code}
It seems that same request can not be parsed multiple times if it has multi
part object in it as the parse method remove it after that.
Found one stackoverflow link around the same:
[https://stackoverflow.com/questions/13881272/servletfileuploadparserequestrequest-returns-an-empty-list]
I believe that all places/uploads using this workflow should resulting the same
issue.
> The createTaskContent request does not work
> ---
>
> Key: OFBIZ-11246
> URL: https://issues.apache.org/jira/browse/OFBIZ-11246
> Project: OFBiz
> Issue Type: Bug
> Components: projectmgr, workeffort
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Ankush Upadhyay
>Priority: Major
>
> While working on OFBIZ-11123 I found that the createTaskContent request does
> not work.
> If you get to
> [https://demo-trunk.ofbiz.apache.org/projectmgr/control/EditTaskContents?workEffortId=9002]
> and enter values, the 1st error you get in log is
> {noformat}
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |UtilProperties
> |W| layoutEvents.no_files_uploaded is missing in ContentErrorUiLabels for
> locale en
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |UtilProperties
> |W| layoutEvents.no_files_uploaded is missing in ContentErrorUiLabels for
> locale en
> 2019-10-11 10:01:12,097 |ajp-nio-8009-exec-8 |ServiceUtil
> |E| {errorMessage=layoutEvents.no_files_uploaded, responseMessage=error}
> {noformat}
> The error above comes from LayoutWorker::uploadImageAndParameters with the
> below stack
> {noformat}
> org.apache.ofbiz.content.layout.LayoutWorker.uploadImageAndParameters(javax.servlet.http.HttpServletRequest,
> java.lang.String) line: 56
> sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method,
> java.lang.Object, java.lang.Object[]) line: not available [native method]
>
> sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) line: 62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) line: 43
> java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line:
> 498
> org.apache.ofbiz.minilang.MiniLangUtil.callMethod(org.apache.ofbiz.minilang.method.MethodOperation,
> org.apache.ofbiz.minilang.method.MethodContext,
> java.util.List>,
> java.lang.Class, java.lang.Object, java.lang.String,
> org.apache.ofbiz.base.util.collections.FlexibleMapAccessor)
> line: 131
> org.apache.ofbiz.minilang.method.callops.CallClassMethod.exec(org.apache.ofbiz.minilang.method.MethodContext)
> line: 93
> org.apache.ofbiz.minilang.SimpleMethod.runSubOps(java.util.List,
> org.apache.ofbiz.minilang.method.MethodContext) line: 310
> org.apache.ofbiz.minilang.SimpleMethod.exec(org.apache.ofbiz.minilang.method.MethodContext)
> line: 457
> org.apache.ofbiz.minilang.SimpleMethod.runSimpleMethod(java.lang.String,
> java.lang.String, org.apache.ofbiz.minilang.method.MethodContext) line: 274
> org.apache.ofbiz.minilang.SimpleMethod.runSimpleEvent(java.lang.String,
> java.lang.String, javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) line: 257
> org.apache.ofbiz.webapp.event.SimpleEventHandler.invoke(org.apache.ofbiz.webapp.control.ConfigXMLReader$Event,
> org.apache.ofbiz.webapp.control.ConfigXMLReader$RequestMap,
> javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) line: 70
> org.apache.ofbiz.webapp.control.RequestHandler.runEvent(javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse,
> org.apache.ofbiz.webapp.control.ConfigXMLReader$Event,
> org.apache.ofbiz.webapp.control.ConfigXMLReader$RequestMap, java.lang.String)
> line: 784
>
[jira] [Updated] (OFBIZ-10802) UserLoginPasswordHistory is not maintaining password as present in UserLogin.
[ https://issues.apache.org/jira/browse/OFBIZ-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Koushal updated OFBIZ-10802: -- Attachment: image-2020-01-25-18-30-57-571.png > UserLoginPasswordHistory is not maintaining password as present in UserLogin. > - > > Key: OFBIZ-10802 > URL: https://issues.apache.org/jira/browse/OFBIZ-10802 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12, 17.12.01, Release Branch 16.11, 16.11.04, 16.11.05, > 16.11.06, Release Branch 17.12, Release Branch 18.12 >Reporter: Rohit Koushal >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10802.patch, UL.png, ULPH.png, > image-2020-01-25-18-30-57-571.png > > > While maintaining UserLoginPasswordHistory in the system, the password is > encrypted with the random salt hence it will not match with the password save > in UserLogin. So we need to improve this area of code. > > Please refer below screenshots > *UserLogin* > *!UL.png!* > *UserLoginPasswordHistory* > *!ULPH.png!* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10850) User is unable to create return
[ https://issues.apache.org/jira/browse/OFBIZ-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023542#comment-17023542 ] ASF subversion and git services commented on OFBIZ-10850: - Commit 61ad77166b636ff818670e0b56c1c1e30ec71a31 in ofbiz-plugins's branch refs/heads/trunk from akash [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=61ad771 ] Fixed: User is unable to create return. (OFBIZ-10850) Thanks, Ashish and Ankush Upadhyay for your contribution. > User is unable to create return > --- > > Key: OFBIZ-10850 > URL: https://issues.apache.org/jira/browse/OFBIZ-10850 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10850.patch, OFBIZ-10850.png > > > *Step to reproduce* > Login with valid username and password. > Navigate to ecommerce. > Create a sales order. > Navigate to order history. > Click on return request > *Expected result:* All the data should be properly aligned. > *Actual result:* Error message is displayed in Return item section. > Screen print attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-10526) Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window
[ https://issues.apache.org/jira/browse/OFBIZ-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain reassigned OFBIZ-10526: -- Assignee: Sourabh Punyani (was: Akash Jain) > Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window > - > > Key: OFBIZ-10526 > URL: https://issues.apache.org/jira/browse/OFBIZ-10526 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Sourabh Punyani >Priority: Major > Attachments: OFBIZ-10526.patch > > > Currently the generation of the report happens in the same window as the > application. For a better user experience this should happen in a new window, > so that the user doesn't need to click back to get to the screen. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10526) Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window
[ https://issues.apache.org/jira/browse/OFBIZ-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023533#comment-17023533 ] Akash Jain commented on OFBIZ-10526: Hello Sourabh, There are more places where ViewFacilityInventoryByProduct report opened into same tab: Facility > Report > Print (PDF) Facility > Inventory > Print (PDF) Note: Export ViewFacilityInventoryByProduct report should also open into new tab. > Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window > - > > Key: OFBIZ-10526 > URL: https://issues.apache.org/jira/browse/OFBIZ-10526 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10526.patch > > > Currently the generation of the report happens in the same window as the > application. For a better user experience this should happen in a new window, > so that the user doesn't need to click back to get to the screen. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023524#comment-17023524 ] Humera Khan commented on OFBIZ-11325: - Actually I took the latest update/pull then applied the patch and it is working fine. > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Humera Khan >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023519#comment-17023519 ] Jacques Le Roux commented on OFBIZ-11325: - When I try to apply the patch in Eclipse the hunk above does not pass, all others are. I guess you need to update/pull your working copy in order to generate a new up to date patch. > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Humera Khan >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-10526) Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window
[ https://issues.apache.org/jira/browse/OFBIZ-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain reassigned OFBIZ-10526: -- Assignee: Sourabh Punyani (was: Akash Jain) > Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window > - > > Key: OFBIZ-10526 > URL: https://issues.apache.org/jira/browse/OFBIZ-10526 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Sourabh Punyani >Priority: Major > Attachments: OFBIZ-10526.patch > > > Currently the generation of the report happens in the same window as the > application. For a better user experience this should happen in a new window, > so that the user doesn't need to click back to get to the screen. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-10526) Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window
[ https://issues.apache.org/jira/browse/OFBIZ-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain reassigned OFBIZ-10526: -- Assignee: Akash Jain (was: Sourabh Punyani) > Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window > - > > Key: OFBIZ-10526 > URL: https://issues.apache.org/jira/browse/OFBIZ-10526 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10526.patch > > > Currently the generation of the report happens in the same window as the > application. For a better user experience this should happen in a new window, > so that the user doesn't need to click back to get to the screen. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-10879) updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients from mail subject for general redirected mails
[
https://issues.apache.org/jira/browse/OFBIZ-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pawan Verma closed OFBIZ-10879.
---
Fix Version/s: 18.12.01
Upcoming Branch
17.12.01
Resolution: Fixed
This has been fixed at:
Trunk: 832076ce91dbca182ffab38d27ea72ca5e2cb0be
R18: bbcc4692dccdf573aa0205f927b56bc271719031
R17: 9706acf064e26c291c0bd10081df8286ae6b359b
> updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients
> from mail subject for general redirected mails
> ---
>
> Key: OFBIZ-10879
> URL: https://issues.apache.org/jira/browse/OFBIZ-10879
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Ulrich Heidfeld
>Assignee: Pawan Verma
>Priority: Minor
> Fix For: 17.12.01, Upcoming Branch, 18.12.01
>
> Attachments: OFBIZ-10879.patch, OFBIZ-10879.patch
>
>
> "updateCommEventAfterEmail" method in CommunicationEventServices.java could
> generate wrong result. If general.properties value
> "mail.notifications.redirectTo" is used, it is possible that the subject
> string has more than 255 character.
> Now:
> {code:java}
> Original subject [To: , Cc: , Bcc: ]
> {code}
> Solution:
> {code:java}
> Original subject [RedirectedTo: recipi...@example.com]
> {code}
> In this way we have fixed this in one of our OFBiz forks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (OFBIZ-10526) Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window
[ https://issues.apache.org/jira/browse/OFBIZ-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain reassigned OFBIZ-10526: -- Assignee: Akash Jain (was: Sourabh Punyani) > Have Print PDF function @ ViewFacilityInventoryByProduct open in a new window > - > > Key: OFBIZ-10526 > URL: https://issues.apache.org/jira/browse/OFBIZ-10526 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Akash Jain >Priority: Major > Attachments: OFBIZ-10526.patch > > > Currently the generation of the report happens in the same window as the > application. For a better user experience this should happen in a new window, > so that the user doesn't need to click back to get to the screen. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10879) updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients from mail subject for general redirected mails
[
https://issues.apache.org/jira/browse/OFBIZ-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023505#comment-17023505
]
ASF subversion and git services commented on OFBIZ-10879:
-
Commit 9706acf064e26c291c0bd10081df8286ae6b359b in ofbiz-framework's branch
refs/heads/release17.12 from Pawan Verma
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=9706acf ]
Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail
for CommunicationEvent.subject field
(OFBIZ-10879)
CommunicationEventServices#updateCommEventAfterEmail could generate wrong
result. If general.properties value 'mail.notifications.redirectTo' is used, it
is possible that the subject string has more than 255 character.
Thanks, Ulrich Heidfeld for your contribution.
> updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients
> from mail subject for general redirected mails
> ---
>
> Key: OFBIZ-10879
> URL: https://issues.apache.org/jira/browse/OFBIZ-10879
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Ulrich Heidfeld
>Assignee: Pawan Verma
>Priority: Minor
> Attachments: OFBIZ-10879.patch, OFBIZ-10879.patch
>
>
> "updateCommEventAfterEmail" method in CommunicationEventServices.java could
> generate wrong result. If general.properties value
> "mail.notifications.redirectTo" is used, it is possible that the subject
> string has more than 255 character.
> Now:
> {code:java}
> Original subject [To: , Cc: , Bcc: ]
> {code}
> Solution:
> {code:java}
> Original subject [RedirectedTo: recipi...@example.com]
> {code}
> In this way we have fixed this in one of our OFBiz forks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-10879) updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients from mail subject for general redirected mails
[
https://issues.apache.org/jira/browse/OFBIZ-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023503#comment-17023503
]
ASF subversion and git services commented on OFBIZ-10879:
-
Commit bbcc4692dccdf573aa0205f927b56bc271719031 in ofbiz-framework's branch
refs/heads/release18.12 from Pawan Verma
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=bbcc469 ]
Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail
for CommunicationEvent.subject field
(OFBIZ-10879)
CommunicationEventServices#updateCommEventAfterEmail could generate wrong
result. If general.properties value 'mail.notifications.redirectTo' is used, it
is possible that the subject string has more than 255 character.
Thanks, Ulrich Heidfeld for your contribution.
> updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients
> from mail subject for general redirected mails
> ---
>
> Key: OFBIZ-10879
> URL: https://issues.apache.org/jira/browse/OFBIZ-10879
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Ulrich Heidfeld
>Assignee: Pawan Verma
>Priority: Minor
> Attachments: OFBIZ-10879.patch, OFBIZ-10879.patch
>
>
> "updateCommEventAfterEmail" method in CommunicationEventServices.java could
> generate wrong result. If general.properties value
> "mail.notifications.redirectTo" is used, it is possible that the subject
> string has more than 255 character.
> Now:
> {code:java}
> Original subject [To: , Cc: , Bcc: ]
> {code}
> Solution:
> {code:java}
> Original subject [RedirectedTo: recipi...@example.com]
> {code}
> In this way we have fixed this in one of our OFBiz forks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-10879) updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients from mail subject for general redirected mails
[
https://issues.apache.org/jira/browse/OFBIZ-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023501#comment-17023501
]
ASF subversion and git services commented on OFBIZ-10879:
-
Commit 832076ce91dbca182ffab38d27ea72ca5e2cb0be in ofbiz-framework's branch
refs/heads/trunk from Pawan Verma
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=832076c ]
Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail
for CommunicationEvent.subject field
(OFBIZ-10879)
CommunicationEventServices#updateCommEventAfterEmail could generate wrong
result. If general.properties value 'mail.notifications.redirectTo' is used, it
is possible that the subject string has more than 255 character.
Thanks, Ulrich Heidfeld for your contribution.
> updateCommEventAfterEmail: Restore original sendTo/sendCc/sendBcc recipients
> from mail subject for general redirected mails
> ---
>
> Key: OFBIZ-10879
> URL: https://issues.apache.org/jira/browse/OFBIZ-10879
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Ulrich Heidfeld
>Assignee: Pawan Verma
>Priority: Minor
> Attachments: OFBIZ-10879.patch, OFBIZ-10879.patch
>
>
> "updateCommEventAfterEmail" method in CommunicationEventServices.java could
> generate wrong result. If general.properties value
> "mail.notifications.redirectTo" is used, it is possible that the subject
> string has more than 255 character.
> Now:
> {code:java}
> Original subject [To: , Cc: , Bcc: ]
> {code}
> Solution:
> {code:java}
> Original subject [RedirectedTo: recipi...@example.com]
> {code}
> In this way we have fixed this in one of our OFBiz forks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023488#comment-17023488 ] Humera Khan edited comment on OFBIZ-11325 at 1/25/20 10:24 AM: --- Hello Jacques, Can you please elaborate, what we need to update in the patch? was (Author: humera.khan): Sure Jacques, thanks > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Humera Khan >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11107) Issue date of a quote should always be a date before quote's expiry date
[ https://issues.apache.org/jira/browse/OFBIZ-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Sharma updated OFBIZ-11107: --- Attachment: (was: OFBIZ-11107) > Issue date of a quote should always be a date before quote's expiry date > > > Key: OFBIZ-11107 > URL: https://issues.apache.org/jira/browse/OFBIZ-11107 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Dikpal Kanungo >Assignee: Praveen Sharma >Priority: Minor > Attachments: OFBIZ-11107.patch, QuoteReport.pdf > > > The issue date of a quote should always fall before the quote expires, in the > current implementation user is able to select any date, irrespective of the > from and thru date. > Expected- > We should apply a validation while submitting the quote, that will check if > the issue date is exceeding expiry date, if yes we should display a message > to select a date before the expiry date. > Please have a look at the attached quote pdf to have a better understanding. > > Steps to regenerate- > Navigate to - > [https://demo-trunk.ofbiz.apache.org/ordermgr/control/createQuote] > Try creating a quote. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11107) Issue date of a quote should always be a date before quote's expiry date
[ https://issues.apache.org/jira/browse/OFBIZ-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023500#comment-17023500 ] Praveen Sharma commented on OFBIZ-11107: I have provided the patch with a fix to check thruDate should be greater than fromDate. > Issue date of a quote should always be a date before quote's expiry date > > > Key: OFBIZ-11107 > URL: https://issues.apache.org/jira/browse/OFBIZ-11107 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Dikpal Kanungo >Assignee: Praveen Sharma >Priority: Minor > Attachments: OFBIZ-11107.patch, QuoteReport.pdf > > > The issue date of a quote should always fall before the quote expires, in the > current implementation user is able to select any date, irrespective of the > from and thru date. > Expected- > We should apply a validation while submitting the quote, that will check if > the issue date is exceeding expiry date, if yes we should display a message > to select a date before the expiry date. > Please have a look at the attached quote pdf to have a better understanding. > > Steps to regenerate- > Navigate to - > [https://demo-trunk.ofbiz.apache.org/ordermgr/control/createQuote] > Try creating a quote. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11107) Issue date of a quote should always be a date before quote's expiry date
[ https://issues.apache.org/jira/browse/OFBIZ-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Sharma updated OFBIZ-11107: --- Attachment: OFBIZ-11107.patch > Issue date of a quote should always be a date before quote's expiry date > > > Key: OFBIZ-11107 > URL: https://issues.apache.org/jira/browse/OFBIZ-11107 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Dikpal Kanungo >Assignee: Praveen Sharma >Priority: Minor > Attachments: OFBIZ-11107.patch, QuoteReport.pdf > > > The issue date of a quote should always fall before the quote expires, in the > current implementation user is able to select any date, irrespective of the > from and thru date. > Expected- > We should apply a validation while submitting the quote, that will check if > the issue date is exceeding expiry date, if yes we should display a message > to select a date before the expiry date. > Please have a look at the attached quote pdf to have a better understanding. > > Steps to regenerate- > Navigate to - > [https://demo-trunk.ofbiz.apache.org/ordermgr/control/createQuote] > Try creating a quote. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11327) Unable to upload content at view profile screen
Mohammed Rehan Khan created OFBIZ-11327: --- Summary: Unable to upload content at view profile screen Key: OFBIZ-11327 URL: https://issues.apache.org/jira/browse/OFBIZ-11327 Project: OFBiz Issue Type: Bug Components: ecommerce Affects Versions: Trunk Reporter: Mohammed Rehan Khan Attachments: FileManager-Ecommerce.png Steps to regenerate - # Open URL https://demo-stable.ofbiz.apache.org/ecommerce/control/main # Click on the profile tab # Go to file manager section # Upload any type of content Error - No uploaded content found in the context Expected - User should be able to upload content Please refer attachment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11107) Issue date of a quote should always be a date before quote's expiry date
[ https://issues.apache.org/jira/browse/OFBIZ-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Sharma updated OFBIZ-11107: --- Attachment: OFBIZ-11107 > Issue date of a quote should always be a date before quote's expiry date > > > Key: OFBIZ-11107 > URL: https://issues.apache.org/jira/browse/OFBIZ-11107 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Dikpal Kanungo >Assignee: Praveen Sharma >Priority: Minor > Attachments: OFBIZ-11107, QuoteReport.pdf > > > The issue date of a quote should always fall before the quote expires, in the > current implementation user is able to select any date, irrespective of the > from and thru date. > Expected- > We should apply a validation while submitting the quote, that will check if > the issue date is exceeding expiry date, if yes we should display a message > to select a date before the expiry date. > Please have a look at the attached quote pdf to have a better understanding. > > Steps to regenerate- > Navigate to - > [https://demo-trunk.ofbiz.apache.org/ordermgr/control/createQuote] > Try creating a quote. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11293) Duplicate entries at Tax Identification and Exemption
[ https://issues.apache.org/jira/browse/OFBIZ-11293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023499#comment-17023499 ] Dikpal Kanungo commented on OFBIZ-11293: Hello, [~singh.vivek599], just to add here, the functionality to 'delete' is also not working. Please keep a note of it while you fix the issue. > Duplicate entries at Tax Identification and Exemption > - > > Key: OFBIZ-11293 > URL: https://issues.apache.org/jira/browse/OFBIZ-11293 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Release Branch 16.11 >Reporter: Dikpal Kanungo >Assignee: vivek singh bisen >Priority: Minor > Attachments: Duplicate Tax Identification and Exemption.png > > > Steps to regenerate - > 1. Open - [https://demo-trunk.ofbiz.apache.org/ecommerce/] > 2. Navigate to adding delivery address while making as quick checkout > 3. Add a single item for more than one time from the dropdown of Tax > Identification and Exemption > > Issue: Duplicate items should not be listed as shown in the attached image > > Expected: If an item is added from the dropdown, it should not be listed > again. > > !Duplicate Tax Identification and Exemption.png! Please have a look at the > attached screenshot- > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11326) Entity find pagination(next, last, changes in the number of pages) stopped working
[
https://issues.apache.org/jira/browse/OFBIZ-11326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-11326:
---
Assignee: Jacques Le Roux
> Entity find pagination(next, last, changes in the number of pages) stopped
> working
> --
>
> Key: OFBIZ-11326
> URL: https://issues.apache.org/jira/browse/OFBIZ-11326
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pawan Verma
>Assignee: Jacques Le Roux
>Priority: Major
>
> After this change done under OFBIZ-11007, entity find pagination(next, last,
> changes in the number of pages) stopped working. Getting following error:
> {code:java}
> // ERROR MESSAGEorg.apache.ofbiz.webapp.control.RequestHandlerException:
> Unknown request [entity]; this request does not exist or cannot be called
> directly.{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-11326) Entity find pagination(next, last, changes in the number of pages) stopped working
[
https://issues.apache.org/jira/browse/OFBIZ-11326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-11326:
Description:
After this change done under OFBIZ-11007, entity find pagination(next, last,
changes in the number of pages) stopped working. Getting following error:
{code:java}
// ERROR MESSAGEorg.apache.ofbiz.webapp.control.RequestHandlerException:
Unknown request [entity]; this request does not exist or cannot be called
directly.{code}
was:
After this change done under https://issues.apache.org/jira/browse/OFBIZ-11007,
entity find pagination(next, last, changes in the number of pages) stopped
working. Getting following error:
{code:java}
// ERROR MESSAGEorg.apache.ofbiz.webapp.control.RequestHandlerException:
Unknown request [entity]; this request does not exist or cannot be called
directly.{code}
> Entity find pagination(next, last, changes in the number of pages) stopped
> working
> --
>
> Key: OFBIZ-11326
> URL: https://issues.apache.org/jira/browse/OFBIZ-11326
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pawan Verma
>Priority: Major
>
> After this change done under OFBIZ-11007, entity find pagination(next, last,
> changes in the number of pages) stopped working. Getting following error:
> {code:java}
> // ERROR MESSAGEorg.apache.ofbiz.webapp.control.RequestHandlerException:
> Unknown request [entity]; this request does not exist or cannot be called
> directly.{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11297) Tools to backport
[ https://issues.apache.org/jira/browse/OFBIZ-11297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-11297: --- Assignee: Jacques Le Roux > Tools to backport > - > > Key: OFBIZ-11297 > URL: https://issues.apache.org/jira/browse/OFBIZ-11297 > Project: OFBiz > Issue Type: Sub-task >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > > Currently backport in Git (to R18 and R17) is mostly done by cherry picking. > This is hand work. I think we should concentrate on tools necessary to > backport with Git. Like the convenient scripts we had previously with Svn. > And if we want to continuously/seriously backport to R16 we need a such tool > too, from Git to Svn, using patches maybe. An alternative is to stop > supporting R16 and release R17. Sincerely, I'm actually more inclined to this > alternative... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11326) Entity find pagination(next, last, changes in the number of pages) stopped working
Pawan Verma created OFBIZ-11326:
---
Summary: Entity find pagination(next, last, changes in the number
of pages) stopped working
Key: OFBIZ-11326
URL: https://issues.apache.org/jira/browse/OFBIZ-11326
Project: OFBiz
Issue Type: Bug
Components: framework/webtools
Affects Versions: Trunk
Reporter: Pawan Verma
After this change done under https://issues.apache.org/jira/browse/OFBIZ-11007,
entity find pagination(next, last, changes in the number of pages) stopped
working. Getting following error:
{code:java}
// ERROR MESSAGEorg.apache.ofbiz.webapp.control.RequestHandlerException:
Unknown request [entity]; this request does not exist or cannot be called
directly.{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11223) User should not be directed to main page after adding product to cart from showcart page
[ https://issues.apache.org/jira/browse/OFBIZ-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023491#comment-17023491 ] ASF subversion and git services commented on OFBIZ-11223: - Commit 15750b9d5ad0f1da0c67fb6da7e7f81cb7997d8c in ofbiz-plugins's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=15750b9 ] Fixed: User should not be directed to main page after adding product to cart from showcart page (OFBIZ-11223) Navigate to URL: https://demo-trunk.ofbiz.apache.org/ecomseo/ Click on View Cart at top-right of the page (User will be directed to showcart page) Enter product number (Eg: GZ-2644) Enter quantity Click on add to cart Product is added to the cart but user is directed to main page of ecommerce. Thanks: Arpit Mor for report, Sourabh Punyani for the fix > User should not be directed to main page after adding product to cart from > showcart page > > > Key: OFBIZ-11223 > URL: https://issues.apache.org/jira/browse/OFBIZ-11223 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-11223.patch, Video1.webm > > > Steps to regenerate: > # Navigate to URL: [https://demo-trunk.ofbiz.apache.org/ecomseo/] > # Click on View Cart at top-right of the page (User will be directed to > showcart page) > # Enter product number (Eg: GZ-2644) > # Enter quantity > # Click on add to cart > Actual: Product is added to the cart but user is directed to main page of > ecommerce. Please refer attachmnet: Video1 > Expected: User should remain at showcart page after the product is added to > cart -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023488#comment-17023488 ] Humera Khan commented on OFBIZ-11325: - Sure Jacques, thanks > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Humera Khan >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11223) User should not be directed to main page after adding product to cart from showcart page
[ https://issues.apache.org/jira/browse/OFBIZ-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-11223: --- Assignee: Jacques Le Roux (was: Sourabh Punyani) > User should not be directed to main page after adding product to cart from > showcart page > > > Key: OFBIZ-11223 > URL: https://issues.apache.org/jira/browse/OFBIZ-11223 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-11223.patch, Video1.webm > > > Steps to regenerate: > # Navigate to URL: [https://demo-trunk.ofbiz.apache.org/ecomseo/] > # Click on View Cart at top-right of the page (User will be directed to > showcart page) > # Enter product number (Eg: GZ-2644) > # Enter quantity > # Click on add to cart > Actual: Product is added to the cart but user is directed to main page of > ecommerce. Please refer attachmnet: Video1 > Expected: User should remain at showcart page after the product is added to > cart -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-10983) Unable to choose the catalog in storefront apart from demo catalog
[ https://issues.apache.org/jira/browse/OFBIZ-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-10983: --- Assignee: Komal Dayle (was: Jacques Le Roux) > Unable to choose the catalog in storefront apart from demo catalog > -- > > Key: OFBIZ-10983 > URL: https://issues.apache.org/jira/browse/OFBIZ-10983 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Komal Dayle >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10983.docx > > > *Step to reproduce* > 1. Login with valid username and password. > 2. Navigate to ecommerce.[https://demo-trunk.ofbiz.apache.org/ecomseo] > 3. Select the catalog as eBay catalog in choose catalog dropdown. > *Actual Result*: After page refresh demo catalog is applied. > *Screen attached* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-10983) Unable to choose the catalog in storefront apart from demo catalog
[ https://issues.apache.org/jira/browse/OFBIZ-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10983. --- Resolution: Cannot Reproduce Thanks Komal, THis is indeed no longer an issue > Unable to choose the catalog in storefront apart from demo catalog > -- > > Key: OFBIZ-10983 > URL: https://issues.apache.org/jira/browse/OFBIZ-10983 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10983.docx > > > *Step to reproduce* > 1. Login with valid username and password. > 2. Navigate to ecommerce.[https://demo-trunk.ofbiz.apache.org/ecomseo] > 3. Select the catalog as eBay catalog in choose catalog dropdown. > *Actual Result*: After page refresh demo catalog is applied. > *Screen attached* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-10983) Unable to choose the catalog in storefront apart from demo catalog
[ https://issues.apache.org/jira/browse/OFBIZ-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-10983: --- Assignee: Jacques Le Roux > Unable to choose the catalog in storefront apart from demo catalog > -- > > Key: OFBIZ-10983 > URL: https://issues.apache.org/jira/browse/OFBIZ-10983 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10983.docx > > > *Step to reproduce* > 1. Login with valid username and password. > 2. Navigate to ecommerce.[https://demo-trunk.ofbiz.apache.org/ecomseo] > 3. Select the catalog as eBay catalog in choose catalog dropdown. > *Actual Result*: After page refresh demo catalog is applied. > *Screen attached* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-11223) User should not be directed to main page after adding product to cart from showcart page
[ https://issues.apache.org/jira/browse/OFBIZ-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023441#comment-17023441 ] Jacques Le Roux edited comment on OFBIZ-11223 at 1/25/20 9:49 AM: -- Hello, I have added [^OFBIZ-11223.patch] for the same. Please verify. was (Author: sourabh.punyani): Hello, I have added a patch(OFBIZ-11223.patch) for the same. Please verify. > User should not be directed to main page after adding product to cart from > showcart page > > > Key: OFBIZ-11223 > URL: https://issues.apache.org/jira/browse/OFBIZ-11223 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Arpit Mor >Assignee: Sourabh Punyani >Priority: Minor > Attachments: OFBIZ-11223.patch, Video1.webm > > > Steps to regenerate: > # Navigate to URL: [https://demo-trunk.ofbiz.apache.org/ecomseo/] > # Click on View Cart at top-right of the page (User will be directed to > showcart page) > # Enter product number (Eg: GZ-2644) > # Enter quantity > # Click on add to cart > Actual: Product is added to the cart but user is directed to main page of > ecommerce. Please refer attachmnet: Video1 > Expected: User should remain at showcart page after the product is added to > cart -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-11325: --- Assignee: Humera Khan (was: Jacques Le Roux) > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Humera Khan >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[
https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023482#comment-17023482
]
Jacques Le Roux commented on OFBIZ-11325:
-
HI Humera,
This hunk does not fit:
{code:xml}
{code}
Please update before creating a new patch, thanks
> Fixed the issue on party page that will upload the data each time after
> refreshing the page.
>
>
> Key: OFBIZ-11325
> URL: https://issues.apache.org/jira/browse/OFBIZ-11325
> Project: OFBiz
> Issue Type: Sub-task
> Components: party
>Affects Versions: Trunk
>Reporter: Humera Khan
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: Trunk
>
> Attachments: OFBIZ-11325.patch
>
>
> Please refer OFBIZ-11171
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-11325: --- Assignee: Jacques Le Roux (was: Humera Khan) > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Jacques Le Roux >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer [OFBIZ-11171|https://issues.apache.org/jira/browse/OFBIZ-11171] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11325) Fixed the issue on party page that will upload the data each time after refreshing the page.
[ https://issues.apache.org/jira/browse/OFBIZ-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-11325: Description: Please refer OFBIZ-11171 (was: Please refer [OFBIZ-11171|https://issues.apache.org/jira/browse/OFBIZ-11171]) > Fixed the issue on party page that will upload the data each time after > refreshing the page. > > > Key: OFBIZ-11325 > URL: https://issues.apache.org/jira/browse/OFBIZ-11325 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Jacques Le Roux >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-11325.patch > > > Please refer OFBIZ-11171 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-10983) Unable to choose the catalog in storefront apart from demo catalog
[ https://issues.apache.org/jira/browse/OFBIZ-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023465#comment-17023465 ] Komal Dayle edited comment on OFBIZ-10983 at 1/25/20 9:19 AM: -- As per the description in the ticket I followed the steps to regenerate the issue in the latest trunk but now it is working fine as expected. was (Author: komal.dayle): As per the description in the ticket I followed the steps to regenerate the issue in the latest trunk and now it is working fine as expected. > Unable to choose the catalog in storefront apart from demo catalog > -- > > Key: OFBIZ-10983 > URL: https://issues.apache.org/jira/browse/OFBIZ-10983 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10983.docx > > > *Step to reproduce* > 1. Login with valid username and password. > 2. Navigate to ecommerce.[https://demo-trunk.ofbiz.apache.org/ecomseo] > 3. Select the catalog as eBay catalog in choose catalog dropdown. > *Actual Result*: After page refresh demo catalog is applied. > *Screen attached* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
[ https://issues.apache.org/jira/browse/OFBIZ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023469#comment-17023469 ] Jacques Le Roux commented on OFBIZ-9475: Hi [~deepak], will you commit it? > Refactor serialize and non-serialize inventory item implementaion > - > > Key: OFBIZ-9475 > URL: https://issues.apache.org/jira/browse/OFBIZ-9475 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, OFBIZ-9475.patch, OFBIZ-9475.patch, > OFBIZ-9475.patch, OFBIZ-9475.patch > > > As discussed on dev mailing list [1][2] we need to refactor serialize and > non-serialize inventory item design. > As per current implementation serialize inventory item work on status and > non-serialized inventory item work on inventory item detail. > Proposed Design: > - Use inventory item detail for both serialise and non-serialize inventory > item. Only one additional condition for serialized inventory item that qoh > can't be greater then one. > - We can maintain inventory item status record for both type > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > As we do a lot of discussion in the respective mail threads. > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > According to this email threads, I conclude that:- > There are 2 types of the inventory item in OFBiz. > 1. *Serialized* > 2. *Non serialized* > Majorly there are 3 entities to manage the various transaction of serialised > and non-serialized inventory items. > 1. _InventoryItem_ > 2. _InventoryItemDetail_ > 3. _InventoryItemStatus_ > Following changes need to be done in the workflow of inventory item records:- > 1) There is no need to manage a different workflow for serialised and non- > serialised inventory items. > 2) Transaction of serialised and non-serialised inventory item should be > managed in both InventoryItemStatus and InventoryItemDetail entity. > a) Transaction of serialised inventory items is managed by > inventoryItemstatus entity not managed in inventoryItemDetail entity. While > inventoryItemDetail and inventoryItemStatus should be managed for both > serialised and non-serialised inventory items. > b) As ATP/QOH/AQT are updated on the basis of ATPDIFF/QOHDIFF/AQTDIFF in > non-serialised inventory item. We should follow the same pattern for > serialised inventory item. > c) Change in ATP/QOH/AQT is tracked by inventoryItemDetail entity. > d)Status transaction of an inventory item is tracked in > InventoryItemStatus entity. > 3) No need to manage separate status for serialised and non-serialised > inventory item. They are already distinguished on the basis of inventory item > type. > 1. *Serialised*:- > In a serialised inventory item as of now ATP/QOH/AQT are managed on the > basis of inventory item status.While ATP/QOH/AQT should be the sum of > ATPDIFF/QOHDIFF/AQTDIFF of inventory item detail. > Ex: > 1. If we receive 2 inventory of serialised inventory item then 2 separate > inventory item records are created > InventoryItem:- > inventoryItemId="10001",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" > inventoryItemId="10002" statusId="AVAILABLE" > 2. If status of inventory item is changed from AVAILABLE -> PROMISED then > InventoryItem:- > inventoryItemId="10001",status="PROMISED", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10001", inventoryItemDetailSeqId="10002", ATPDIFF="-1", > QOHDIFF="0", AQTDIFF="0" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" statusEndDateTime="" > inventoryItemId="10002" statusId="PROMISED" > 2. *Non-serialised*:- > At the time of receive non-serialised inventory, Item should be received > in Available status. So that status of non-serialised inventory item can be > managed further. > Status of non-serialised inventory item should be managed at inventory > item level not on inventory item
[jira] [Assigned] (OFBIZ-10983) Unable to choose the catalog in storefront apart from demo catalog
[ https://issues.apache.org/jira/browse/OFBIZ-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Komal Dayle reassigned OFBIZ-10983: --- Assignee: (was: Komal Dayle) > Unable to choose the catalog in storefront apart from demo catalog > -- > > Key: OFBIZ-10983 > URL: https://issues.apache.org/jira/browse/OFBIZ-10983 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10983.docx > > > *Step to reproduce* > 1. Login with valid username and password. > 2. Navigate to ecommerce.[https://demo-trunk.ofbiz.apache.org/ecomseo] > 3. Select the catalog as eBay catalog in choose catalog dropdown. > *Actual Result*: After page refresh demo catalog is applied. > *Screen attached* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10983) Unable to choose the catalog in storefront apart from demo catalog
[ https://issues.apache.org/jira/browse/OFBIZ-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023465#comment-17023465 ] Komal Dayle commented on OFBIZ-10983: - As per the description in the ticket I followed the steps to regenerate the issue in the latest trunk and now it is working fine as expected. > Unable to choose the catalog in storefront apart from demo catalog > -- > > Key: OFBIZ-10983 > URL: https://issues.apache.org/jira/browse/OFBIZ-10983 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ashish Sharma >Assignee: Komal Dayle >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10983.docx > > > *Step to reproduce* > 1. Login with valid username and password. > 2. Navigate to ecommerce.[https://demo-trunk.ofbiz.apache.org/ecomseo] > 3. Select the catalog as eBay catalog in choose catalog dropdown. > *Actual Result*: After page refresh demo catalog is applied. > *Screen attached* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11007) REST: adding segmented URI support
[
https://issues.apache.org/jira/browse/OFBIZ-11007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023462#comment-17023462
]
Jacques Le Roux commented on OFBIZ-11007:
-
Hi Pawan,
I too crossed this issue while working on OFBIZ-11306. I think I found a
solution, which unfortunately is not enough for OFBIZ-11306. Please open a new
Jira I'll try to handle it, thanks.
> REST: adding segmented URI support
> --
>
> Key: OFBIZ-11007
> URL: https://issues.apache.org/jira/browse/OFBIZ-11007
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Affects Versions: Trunk
> Environment:
>Reporter: Artemiy Rozovyk
>Assignee: Nicolas Malin
>Priority: Minor
> Labels: REST, URI
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-11007_refactor-entitymaint.patch,
> OFBIZ-11007_refactor-entitymaint.patch,
> OFBIZ-11007_refactor-entitymaint.patch, entitymaint_example.patch,
> restful_URIs.patch
>
>
> Following the discussion on making OFBiz RESTful OFBIZ-4274 i implemented the
> support of segmented URIs without interfering with current mechanisms of URI
> resolution nor with _overrideView()_ feature.
> Combined with work on associating URIs and HTTP methods done by [~mthl] in
> OFBIZ-10438 , we are now able to provide RESTful APIs as follows:
> {code:java}
>
> ...
>
> ...
>
> ...
> {code}
> After we matched a request-map having parametrized URI as in
> {code:java}
> uri="foo/bar/{baz}"
> {code}
> the value is available inside the request attributes with the corresponding
> key (here _"baz"_)
> The *restful_URIs.patch* allows segmented URI support.
> The *entitymaint_example.patch* is a modified _entitymaint_ part that serves
> as an example of possible application of new system.
> Any questions or comments are welcomed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
