[TYPO3-ect] xaJax - Further development

Elmar HInz elmar.hinz at team.MINUS.red.DOT.net
Wed Mar 21 22:14:55 CET 2007


Am Wed, 21 Mar 2007 18:33:14 +0100 schrieb Franz Holzinger:

> Hello Elmar,
> 
>> 2.) set XAJAX_DEFAULT_CHAR_ENCODING to  iso-8859-1 befor you instantiate
>>     xajax as the documentation suggests:
>> 
>>     http://wiki.xajaxproject.org/Documentation:xajaxResponse.inc.php#xajaxResponse_.28string_.24sEncoding.3DXAJAX_DEFAULT_CHAR_ENCODING.2C_bool_.24bOutputEntities.29
>>     http://wiki.xajaxproject.org/Documentation:xajax.inc.php#Global_Constants
>> 
> a) This gives me troubles with select boxes. The text is displayed as
> ä in clear text and not as German Umlaut ä.
> 
> b)
> $reqURI = t3lib_div::getIndpEnv('TYPO3_REQUEST_SCRIPT') . '?' .
> t3lib_div::getIndpEnv('QUERY_STRING');
> $reqURI .= '&no_cache=1';
> $reqURI = htmlentities($reqURI,ENT_QUOTES,$TSFE->renderCharset);
> $this->xajax->setRequestURI($reqURI);
> 
> Gives an error with the Internet Explorer. The no_cache parameter does
> not get passed to the server. Therfore the whole page is fetched from
> cache and returned. This causes an error message windows in the MS
> Internet Explorer.
> It seams that the JavaScript does not work because it does not accept the
> <script type="text/javascript">
> var
> xajaxRequestUri="http://p13490.jambage.com/index.php?id=1395&amp;no_cache=1";
> This is not understood by the JavaScript engine of the Internet
> Explorer. It always looses the no_cache=1 parameter.
> 
> Where
> $reqURI = tx_ttproducts_javascript::jsspecialchars($reqURI);
> has worked fine.
> 
> 
> So I ask:
> 
> 1.) Do you have a really working solution to this even for the Microsoft
> Internet Explorer?
> 2.) Or is it possible to put the
> tx_ttproducts_javascript::jsspecialchars($reqURI); function into the
> xAjax extension?
> 3.) Or should I better write my own AJAX extension?
> 
> 
> Regards,
> 
> Franz



Hi Franz,

as I mentioned in my first posting from this year I have added CDATA
comments, that cover this problem and should enable the solution you need.

http://lists.netfielders.de/pipermail/typo3-team-extension-coordination/2007-January/001151.html
http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/changeset/6208

Doesn't it work with this?

Regards

Elmar















More information about the TYPO3-team-extension-coordination mailing list