Thread

Hi,

I have one template which should output padded JSON string. If I put the URL of this template into browser’s navigation bar, I get correct output. You can see it by clicking this link:

http://www.classicsunlocked.net/index.php/ebook/jsonp_commentsNumber/?bubble_comments_basic_analysis=201&bubble_comments_morphology=202&bubble_comments_syntax=203&bubble_comments_dictionary=205&bubble_comments_commentary=204&bubble_comments_prosody=206

But when I use URL of this template as intended, i.e. to output a string to be evaluated by already defined javascript function, as here

url= "http://www.classicsunlocked.net/index.php/ebook/jsonp_commentsNumber/?bubble_comments_basic_analysis=201&bubble_comments_morphology=202&bubble_comments_syntax=203&bubble_comments_dictionary=205&bubble_comments_commentary=204&bubble_comments_prosody=206";

    // create script tag
    var script = document.createElement("script");
    script.setAttribute("type", "text/javascript");

    // set script source to the service that responds with the padded JSON data
    script.setAttribute("src", url);

    // insert script tag
    document.getElementsByTagName('head')[0].appendChild(script);

I get “Disallowed Key Characters” error.

It seems that the template in both cases should output the same padded JSON string, isn’t it? What can cause “Disallowed Key Characters” error?

I use EE v 1.6.8 build:  20100121.

Hi Laisvunas,

How are you running that script?  Is it in another template on the same site?  Does it make a difference if the script runs when you are logged out of the site?

Try changing line 448 of /system/core/core.input.php from

exit('Disallowed Key Characters');

to

exit('Disallowed Key Characters: '.$str);

...and let us know the output.

Hi Brandon,

After changing the line 448 of /system/core/core.input.php I get this output:

Disallowed Key Charactersamp;time

There is no difference if I’m logged in or logged out.

In case the line 448 of /system/core/core.input.php is commented out everything works as expected.

Hi again,

Found the culprit! One ampersand symbol in URL was unintentionally converted into HTML entity.

Thanks for your help, Brandon!

Glad you are up and running. Feel free to start a new thread if you have any more questions