Aliases not saved in 0.9.6 when MODx charset not set as UTF-8 - My Forums

Re: Aliases not saved in 0.9.6 when MODx charset not set as UTF-8

Aramaki — Oct 17, 2007, 11:48 AM

Thanks - that helped.

Need to develop new project without waiting for version update

Re: Aliases not saved in 0.9.6 when MODx charset not set as UTF-8

davidm — Jul 18, 2007, 06:44 AM

Yeah and you can find a quick and dirty fix for Latin1 here if you can’t wait : here

(It’s in french )

Re: Aliases not saved in 0.9.6 when MODx charset not set as UTF-8

rethrash — Jul 17, 2007, 10:09 AM

Already fixed in the SVN ... but thanks for pointing that out!

Aliases not saved in 0.9.6 when MODx charset not set as UTF-8

zombiemx — Jul 17, 2007, 09:01 AM

Hi there,

MODx 0.9.6 has been released in May 2007 and nobody seems to have noticed that there was a problem with documents aliases.

In "manager/processors/save_content.processor.php", in the function "stripAlias()" on line 859 :

$alias = strtr($alias, $replace_array);

The problem is that the array "$replace_array" is only declared if the configuration charset is set as UTF-8 :

if (strtoupper($modx->config['modx_charset']) == 'UTF-8'){

So, an error occured while saving the alias because the function "strtr()" don’t find any array as second parameter.

To make the thing work even if the configuration charset is not UTF-8, this should be placed within the "if" statement :

$alias = strtr($alias, $replace_array);

I hope this would be helpful (and quickly corrected).

Thank you,

Benjamin