[jira] [Commented] (OFBIZ-10817) Configure stackTrace displaying on ftl rendering

2019-01-21 Thread Jacques Le Roux (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748471#comment-16748471
 ] 

Jacques Le Roux commented on OFBIZ-10817:
-

Hi Nicolas,

I find the idea good, but could we not at least show a small message to the 
user saying there was a problem?

> Configure stackTrace displaying on ftl rendering
> 
>
> Key: OFBIZ-10817
> URL: https://issues.apache.org/jira/browse/OFBIZ-10817
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: Failure.png, FailureSafe.png, OFBIZ-10817.patch
>
>
> Currently when freemarker failed to execute a template, you have on end 
> screen rendered all java stack trace generate.
> I propose to improve this to display the stack trace only when the property 
> widget.verbose is true, no regression during development and when you switch 
> to production site, in general your widget.verbose is false so end user 
> haven't stack trace (that totally unused for them).
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10814) Error parsing JWT

2019-01-21 Thread Deepak Dixit (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748445#comment-16748445
 ] 

Deepak Dixit commented on OFBIZ-10814:
--

One minor improvement in ExternalLoginKeysManager.getUserlogin method, if 
userLogin found then we need to check if its enabled or not.



> Error parsing JWT
> -
>
> Key: OFBIZ-10814
> URL: https://issues.apache.org/jira/browse/OFBIZ-10814
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
>Priority: Major
> Attachments: Apache OFBiz JWT Test.postman_collection.json, 
> OFBIZ-10814_JWT_parsing_error.patch
>
>
> I have problems using the Authorization: Bearer header value for requests 
> towards OFBiz. OFBiz has problems parsing externally generated JSON Web 
> Tokens.
> I have generated them using both [1] and [2] using HS512 and the default 
> secret.
> The JWT check fails because of a parsing error:
> {noformat}
> 2019-01-17 16:48:36,233 |jsse-nio-8443-exec-7 |JavaEventHandler  
> |E| Problems Processing Event
> io.jsonwebtoken.MalformedJwtException: Unable to read JSON value: 
> �z��'G�#�$�uB"�&�r#�$�3S"
>     at 
> io.jsonwebtoken.impl.DefaultJwtParser.readValue(DefaultJwtParser.java:554) 
> ~[jjwt-0.9.1.jar:0.9.1]
>     at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:252) 
> ~[jjwt-0.9.1.jar:0.9.1]
>     at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:481) 
> ~[jjwt-0.9.1.jar:0.9.1]
>     at 
> io.jsonwebtoken.impl.DefaultJwtParser.parseClaimsJws(DefaultJwtParser.java:541)
>  ~[jjwt-0.9.1.jar:0.9.1]
>     at 
> org.apache.ofbiz.webapp.control.JWTManager.validateToken(JWTManager.java:124) 
> ~[ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.ExternalLoginKeysManager.jwtValidation(ExternalLoginKeysManager.java:292)
>  ~[ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.ExternalLoginKeysManager.checkJWTLogin(ExternalLoginKeysManager.java:196)
>  ~[ofbiz.jar:?]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_152]
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_152]
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_152]
>     at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_152]
>     at 
> org.apache.ofbiz.webapp.event.JavaEventHandler.invoke(JavaEventHandler.java:86)
>  [ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.RequestHandler.runEvent(RequestHandler.java:774)
>  [ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:407)
>  [ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:208) 
> [ofbiz.jar:?]
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:645) 
> [javax.servlet-api-4.0.1.jar:4.0.1]
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:750) 
> [javax.servlet-api-4.0.1.jar:4.0.1]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:191)
>  [ofbiz.jar:?]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:156)
>  [ofbiz.jar:?]
>     at javax.servlet.http.HttpFilter.doFilter(HttpFilter.java:127) 
> [javax.servlet-api-4.0.1.jar:4.0.1]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) 
> [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> 

[jira] [Updated] (OFBIZ-10818) Fix the EntitySync Push and Pull functionality

2019-01-21 Thread Arun Patidar (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Patidar updated OFBIZ-10818:
-
Issue Type: Bug  (was: Improvement)

> Fix the EntitySync Push and Pull functionality
> --
>
> Key: OFBIZ-10818
> URL: https://issues.apache.org/jira/browse/OFBIZ-10818
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk, 16.11.05
>Reporter: Arun Patidar
>Assignee: Arun Patidar
>Priority: Major
> Fix For: 17.12.01, 16.11.06
>
>
> Pull and Push functionality of EntitySync is breaking on various places. Need 
> to test and fix the work flow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-10818) Fix the EntitySync Push and Pull functionality

2019-01-21 Thread Arun Patidar (JIRA)
Arun Patidar created OFBIZ-10818:


 Summary: Fix the EntitySync Push and Pull functionality
 Key: OFBIZ-10818
 URL: https://issues.apache.org/jira/browse/OFBIZ-10818
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: 16.11.05, Trunk
Reporter: Arun Patidar
Assignee: Arun Patidar
 Fix For: 17.12.01, 16.11.06


Pull and Push functionality of EntitySync is breaking on various places. Need 
to test and fix the work flow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10814) Error parsing JWT

2019-01-21 Thread Deepak Dixit (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748389#comment-16748389
 ] 

Deepak Dixit commented on OFBIZ-10814:
--

Thanks Michael, 
Changes look good to me. 

> Error parsing JWT
> -
>
> Key: OFBIZ-10814
> URL: https://issues.apache.org/jira/browse/OFBIZ-10814
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
>Priority: Major
> Attachments: Apache OFBiz JWT Test.postman_collection.json, 
> OFBIZ-10814_JWT_parsing_error.patch
>
>
> I have problems using the Authorization: Bearer header value for requests 
> towards OFBiz. OFBiz has problems parsing externally generated JSON Web 
> Tokens.
> I have generated them using both [1] and [2] using HS512 and the default 
> secret.
> The JWT check fails because of a parsing error:
> {noformat}
> 2019-01-17 16:48:36,233 |jsse-nio-8443-exec-7 |JavaEventHandler  
> |E| Problems Processing Event
> io.jsonwebtoken.MalformedJwtException: Unable to read JSON value: 
> �z��'G�#�$�uB"�&�r#�$�3S"
>     at 
> io.jsonwebtoken.impl.DefaultJwtParser.readValue(DefaultJwtParser.java:554) 
> ~[jjwt-0.9.1.jar:0.9.1]
>     at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:252) 
> ~[jjwt-0.9.1.jar:0.9.1]
>     at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:481) 
> ~[jjwt-0.9.1.jar:0.9.1]
>     at 
> io.jsonwebtoken.impl.DefaultJwtParser.parseClaimsJws(DefaultJwtParser.java:541)
>  ~[jjwt-0.9.1.jar:0.9.1]
>     at 
> org.apache.ofbiz.webapp.control.JWTManager.validateToken(JWTManager.java:124) 
> ~[ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.ExternalLoginKeysManager.jwtValidation(ExternalLoginKeysManager.java:292)
>  ~[ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.ExternalLoginKeysManager.checkJWTLogin(ExternalLoginKeysManager.java:196)
>  ~[ofbiz.jar:?]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_152]
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_152]
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_152]
>     at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_152]
>     at 
> org.apache.ofbiz.webapp.event.JavaEventHandler.invoke(JavaEventHandler.java:86)
>  [ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.RequestHandler.runEvent(RequestHandler.java:774)
>  [ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:407)
>  [ofbiz.jar:?]
>     at 
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:208) 
> [ofbiz.jar:?]
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:645) 
> [javax.servlet-api-4.0.1.jar:4.0.1]
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:750) 
> [javax.servlet-api-4.0.1.jar:4.0.1]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:191)
>  [ofbiz.jar:?]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:156)
>  [ofbiz.jar:?]
>     at javax.servlet.http.HttpFilter.doFilter(HttpFilter.java:127) 
> [javax.servlet-api-4.0.1.jar:4.0.1]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
>  [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) 
> [tomcat-catalina-9.0.13.jar:9.0.13]
>     at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) 
> 

[jira] [Commented] (OFBIZ-10817) Configure stackTrace displaying on ftl rendering

2019-01-21 Thread Deepak Dixit (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748386#comment-16748386
 ] 

Deepak Dixit commented on OFBIZ-10817:
--

I like the idea, 
One small suggestion: 
Can we use ModelWidget.widgetBoundaryCommentsEnabled method instead of just 
getting widget.verbose from properties files?
 

> Configure stackTrace displaying on ftl rendering
> 
>
> Key: OFBIZ-10817
> URL: https://issues.apache.org/jira/browse/OFBIZ-10817
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: Failure.png, FailureSafe.png, OFBIZ-10817.patch
>
>
> Currently when freemarker failed to execute a template, you have on end 
> screen rendered all java stack trace generate.
> I propose to improve this to display the stack trace only when the property 
> widget.verbose is true, no regression during development and when you switch 
> to production site, in general your widget.verbose is false so end user 
> haven't stack trace (that totally unused for them).
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (OFBIZ-10768) Cannot sort fields of a form if it has a parent

2019-01-21 Thread Taher Alkhateeb (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Taher Alkhateeb closed OFBIZ-10768.
---

> Cannot sort fields of a form if it has a parent
> ---
>
> Key: OFBIZ-10768
> URL: https://issues.apache.org/jira/browse/OFBIZ-10768
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10768.patch
>
>
> To repeat the bug:
>  * Create a form with a few fields and do not set the 
> sort-field-parameter-name attribute
>  * Create another form that extends from this form and again do not set the 
> sort-field-parameter-name attribute
>  * Now make any field sortable by setting sort-field="true"
>  * Observe how the link is broken. instead of having sortField=whatever in 
> the URL, instead you would get intra-app=whatever. Thus sort field 
> functionality becomes broken.
> After investigating this issue, I realized the reason was an error in the 
> ModelForm.java file. I will provide a patch for a fix.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10817) Configure stackTrace displaying on ftl rendering

2019-01-21 Thread Nicolas Malin (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Malin updated OFBIZ-10817:
--
Attachment: OFBIZ-10817.patch

> Configure stackTrace displaying on ftl rendering
> 
>
> Key: OFBIZ-10817
> URL: https://issues.apache.org/jira/browse/OFBIZ-10817
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: Failure.png, FailureSafe.png, OFBIZ-10817.patch
>
>
> Currently when freemarker failed to execute a template, you have on end 
> screen rendered all java stack trace generate.
> I propose to improve this to display the stack trace only when the property 
> widget.verbose is true, no regression during development and when you switch 
> to production site, in general your widget.verbose is false so end user 
> haven't stack trace (that totally unused for them).
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-10817) Configure stackTrace displaying on ftl rendering

2019-01-21 Thread Nicolas Malin (JIRA)
Nicolas Malin created OFBIZ-10817:
-

 Summary: Configure stackTrace displaying on ftl rendering
 Key: OFBIZ-10817
 URL: https://issues.apache.org/jira/browse/OFBIZ-10817
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk
Reporter: Nicolas Malin
Assignee: Nicolas Malin
 Attachments: Failure.png, FailureSafe.png

Currently when freemarker failed to execute a template, you have on end screen 
rendered all java stack trace generate.

I propose to improve this to display the stack trace only when the property 
widget.verbose is true, no regression during development and when you switch to 
production site, in general your widget.verbose is false so end user haven't 
stack trace (that totally unused for them).

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10816) URL not encoding in FTL

2019-01-21 Thread Murugeswari (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murugeswari updated OFBIZ-10816:

Description: 
Hi,

I have created Product as TEST#01 in [demo 
site|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST%2301]
 and attached the Same to category 101. In the category master searched for 
category 101 went to product tab, when I am trying to open a product master, 
link is generated 
[like|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST#01]
 and asking for creating new product. But in product search and menu click is 
working fine problem is from ftl url are not getting encoded... But when debug 
it encoding is done properly. Don`t know whats happening on FTL printing

  was:
Hi,

I have created Product as TEST#01 in demo 
site([#https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST%2301])
 and attached the Same to category 101. In the category master searched for 
category 101 went to product tab, when I am trying to open a product master, 
link is generated like 
([#https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST#01])
 and asking for creating new product. But in product search and menu click is 
working fine problem is from ftl url are not getting encoded... But when debug 
it encoding is done properly. Don`t know whats happening on FTL printing


> URL not encoding in FTL 
> 
>
> Key: OFBIZ-10816
> URL: https://issues.apache.org/jira/browse/OFBIZ-10816
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 16.11
>Reporter: Murugeswari
>Priority: Major
>
> Hi,
> I have created Product as TEST#01 in [demo 
> site|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST%2301]
>  and attached the Same to category 101. In the category master searched for 
> category 101 went to product tab, when I am trying to open a product master, 
> link is generated 
> [like|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST#01]
>  and asking for creating new product. But in product search and menu click is 
> working fine problem is from ftl url are not getting encoded... But when 
> debug it encoding is done properly. Don`t know whats happening on FTL 
> printing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10816) URL not encoding in FTL

2019-01-21 Thread Murugeswari (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murugeswari updated OFBIZ-10816:

Description: 
Hi,

I have created Product as TEST#01 in [demo 
site|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST%2301]
 and attached the Same to category 101. In the category master searched for 
category 101 went to product tab, when I am trying to open a product master, 
link is generated 
[like|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST#01]
 and asking for creating new product. But in product search and menu click is 
working fine problem is from ftl url are not getting encoded...Don`t know whats 
happening on FTL printing 

  was:
Hi,

I have created Product as TEST#01 in [demo 
site|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST%2301]
 and attached the Same to category 101. In the category master searched for 
category 101 went to product tab, when I am trying to open a product master, 
link is generated 
[like|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST#01]
 and asking for creating new product. But in product search and menu click is 
working fine problem is from ftl url are not getting encoded... But when debug 
it encoding is done properly. Don`t know whats happening on FTL printing


> URL not encoding in FTL 
> 
>
> Key: OFBIZ-10816
> URL: https://issues.apache.org/jira/browse/OFBIZ-10816
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 16.11
>Reporter: Murugeswari
>Priority: Major
>
> Hi,
> I have created Product as TEST#01 in [demo 
> site|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST%2301]
>  and attached the Same to category 101. In the category master searched for 
> category 101 went to product tab, when I am trying to open a product master, 
> link is generated 
> [like|https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST#01]
>  and asking for creating new product. But in product search and menu click is 
> working fine problem is from ftl url are not getting encoded...Don`t know 
> whats happening on FTL printing 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-10816) URL not encoding in FTL

2019-01-21 Thread Murugeswari (JIRA)
Murugeswari created OFBIZ-10816:
---

 Summary: URL not encoding in FTL 
 Key: OFBIZ-10816
 URL: https://issues.apache.org/jira/browse/OFBIZ-10816
 Project: OFBiz
  Issue Type: Bug
  Components: ALL COMPONENTS
Affects Versions: Release Branch 16.11
Reporter: Murugeswari


Hi,

I have created Product as TEST#01 in demo 
site([#https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST%2301])
 and attached the Same to category 101. In the category master searched for 
category 101 went to product tab, when I am trying to open a product master, 
link is generated like 
([#https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=TEST#01])
 and asking for creating new product. But in product search and menu click is 
working fine problem is from ftl url are not getting encoded... But when debug 
it encoding is done properly. Don`t know whats happening on FTL printing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10595) The query iCalendar/CALENDAR_PUB_DEMO/ no longer works

2019-01-21 Thread JIRA


[ 
https://issues.apache.org/jira/browse/OFBIZ-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747812#comment-16747812
 ] 

Jyri Sillanpää commented on OFBIZ-10595:


It can be applied to the Release Branch 16.11. not just 16.11.05.

> The query iCalendar/CALENDAR_PUB_DEMO/ no longer works
> --
>
> Key: OFBIZ-10595
> URL: https://issues.apache.org/jira/browse/OFBIZ-10595
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 16.11.06
>
> Attachments: iCalendar.patch
>
>
> ControlFilter does not allow the untypical iCalendar/CALENDAR_PUB_DEMO/ query 
> to pass.
> This feature works in the stable version. So it's a change since then
> Thanks to Jyri Sillanpaa for the detailled report: 
> https://markmail.org/message/pfd62nom3ftnpgll



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10595) The query iCalendar/CALENDAR_PUB_DEMO/ no longer works

2019-01-21 Thread JIRA


[ 
https://issues.apache.org/jira/browse/OFBIZ-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747790#comment-16747790
 ] 

Jyri Sillanpää commented on OFBIZ-10595:


Uhh, yes, that patch is to fix the problems on 16.11.05 we are planning on 
using for production.

> The query iCalendar/CALENDAR_PUB_DEMO/ no longer works
> --
>
> Key: OFBIZ-10595
> URL: https://issues.apache.org/jira/browse/OFBIZ-10595
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 16.11.06
>
> Attachments: iCalendar.patch
>
>
> ControlFilter does not allow the untypical iCalendar/CALENDAR_PUB_DEMO/ query 
> to pass.
> This feature works in the stable version. So it's a change since then
> Thanks to Jyri Sillanpaa for the detailled report: 
> https://markmail.org/message/pfd62nom3ftnpgll



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)