View Issue Details

IDProjectCategoryView StatusLast Update
0003039OXID eShop (all versions)4.07. Source code, Testpublic2012-12-10 13:44
Reportertomas_liubinas Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status resolvedResolutionno change required 
Summary0003039: oxConfig::appendUrl() method separates URL params using &_amp;
DescriptionWhile researching strange paypal module behaviour we realised that oxConfig::appendUrl() method separates URL params using &_amp instead of single char &. The output of the method is used in oxConfig::getShopHomeUrl() which (I assume) could be used directly in templates for further reference. When we do it, &_amp; separator instead of single char & separator is a clearly wrong choice. But this is theoretical, in practice nobody complained about it and there must be a reason why &_amp; was implemnted anyway, that's why I am not sure if it's wrong or not. Needs to be researched. As a note I would like to mention, that the separator is only added in limited conditions (when resolving urls for different language for ssl or something like this) so the harmful effect of this behaviour might not be noticed under normal circumstances.

P.S. I added an underscore within special char description as Mantis tends to screw them.
TagsNo tags attached.
ThemeBoth
BrowserAll
PHP Versionany
Database Versionany

Activities

rimvydas_paskevicius

2011-08-01 16:04

reporter   ~0004908

Last edited: 2011-08-01 16:05

The reason why char & is converted in URL params using &_amp is that WC3 validator does not allows & char as it is special html character. Links can't contain & char as it has special meaning and must be converted to &_amp;.