Diazo add unwanted html header into json response_问答_开发者

Diazo add unwanted html header into json response

开发者 https://www.devze.com 2023-04-06 20:33 出处：网络

I have a blank Plone开发者_开发技巧 4.1 site with only collective.quickupload installed. The upload portlet worked fine until I install plone.app.theming and apply my theme. The files were still uploa

相关专题：diazo plone

Inspecting the ajax response from server I found that they were wrapped by html header. The old response (before install diazo & apply my theme) was simply

{"success":true}

The new response (after install diazo and apply my theme) was being wrapped by a html tag:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"><body><p>{"success":true}</p></body></html>

I've pasted my rule.xml file here (nothing special, there is only one rule conditioned by css:if-content="#visual-portal-wrapper"): http://pastebin.com/SaK13Fni

What should I do to work around this ?

Thanks

To avoid this behavior you have to add an exception in your rules.xml that specify to not apply your theme to your specific view , like this:

<notheme if-path="myjson_view"/>

edit:

I've tried with one of my diazo themes and a json view and I didn't have your issue. So I think the problem is either in your rules.xml or in your json view. You should try one of these two way:

change your rules.xml this way:

   <rules
    xmlns="http://namespaces.plone.org/diazo"
    xmlns:css="http://namespaces.plone.org/diazo/css"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

    <!-- Prevent theme usage in zmi-->
    <rules css:if-content="#visual-portal-wrapper">
        <theme href="index.html" />
    </rules>

have you already specified the "Content-type" of the output in your json view? Like this:
```
self.request.response.setHeader("Content-type","application/json")
return json_data
```
If not, that's probably the problem.

Watch out for using Chrome inspector... it adds the html head and pre tags around your json when you inspect it...it's not actually there if you look at view:source of the page (old school)...