[
https://issues.apache.org/jira/browse/OFBIZ-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511388
]
David E. Jones commented on OFBIZ-1133:
---------------------------------------
Just a quick note: we can't really encode this sort of string in the database,
it really needs to be done in code that passes it through various types of
limited string representations. In other words there are many possible string
encodings such as Javascript inline string, HTML text, XML text, HTTP
parameter, UTF-8 \u encoding, etc, etc. Because of all of these things we might
want to do with the data, there is no one way we can encode it in the database.
> Unescaped quotes break lookup screens functionality
> ---------------------------------------------------
>
> Key: OFBIZ-1133
> URL: https://issues.apache.org/jira/browse/OFBIZ-1133
> Project: OFBiz
> Issue Type: Bug
> Affects Versions: SVN trunk, Release Branch 4.0
> Reporter: Oleg Andreyev
> Priority: Minor
> Fix For: SVN trunk
>
>
> Example, it's impossible to select product in LookupProductAndPrice (used in
> EditQuoteItem) if product internal name contains quotas or apostrophe. The
> reason is obvious. The script "javascript:set_values('10112', 'Test product -
> Monitor 17", gray')" has error, unnecessary quote. I think the problem is
> common.
> Simple solution is to remove second parameter. There is no field internalName
> in opener form. But it's feckless way.
> Have anybody suggestion how rightly correct this problem? Modify
> HtmlFormRenderer?
> Please explain me why we don't store escaped string in database. This is
> generally accepted solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
