<![CDATA[FrontAccounting forum — quoting problem in manufacturing/inquiry/where_used_inquiry.php]]> https://frontaccounting.com/punbb/viewtopic.php?id=638 Thu, 14 May 2009 20:36:57 +0000 PunBB <![CDATA[Re: quoting problem in manufacturing/inquiry/where_used_inquiry.php]]> https://frontaccounting.com/punbb/viewtopic.php?pid=2545#p2545 Yes, this is a problem. Here is conflict between two meanings of ampersand. First it is used to quote special chars in database, second it can be used as hotkey prefix. At first glance I think we could remove the access_string call in pager_link function without harm, but I'm not sure now. Please report this issue on mantis to be fixed asap.

Janusz

]]> Thu, 14 May 2009 20:36:57 +0000 https://frontaccounting.com/punbb/viewtopic.php?pid=2545#p2545 <![CDATA[quoting problem in manufacturing/inquiry/where_used_inquiry.php]]> https://frontaccounting.com/punbb/viewtopic.php?pid=2539#p2539 When I run a where used query I see:

GRIT-12 - 12quot; Grit Kit

when it should say

GRIT-12 - 12" Grit Kit

HTML

<tr class='evenrow'>
<td ><a href='../../manufacturing/manage/bom_edit.php?stock_id=GRIT-12' accesskey='Q'>GRIT-12 - 12<u>q</u>uot; Grit Kit</a></td>
<td >Garage</td>
<td >Default</td>
<td >1</td>

This is because the short cut key syntax uses &,

Maybe before checking for the & the code should urldecode the string and then re-urlencode the string?

I looked around in the code, but got a bit lost...
I am sure you know right where to go...

tom

]]> Thu, 14 May 2009 11:21:46 +0000 https://frontaccounting.com/punbb/viewtopic.php?pid=2539#p2539