#1 Breaks on this submission to the API

已關閉
Tsyesika9 年之前創建 · 2 條評論

Original ticket is: https://github.com/xray7224/Pamrel/issues/24

I tried posting:

{% if action_form and actions_on_top and cl.full_result_count %}
<div class='pull-left'>{% admin_actions %}</div>
{% endif %}

via pamrel-el, and got:

HTTP/1.1 500 INTERNAL SERVER ERROR
Date: Thu, 09 Apr 2015 16:42:34 GMT
Server: Apache
Connection: close
Transfer-Encoding: chunked
Content-Type: text/plain; charset=UTF-8

No content specified

But it looks like what I submitted was (as formencoded):

content=%7B%25%20if%20action_form%20and%20actions_on_top%20and%20cl.full_result_count%20%25%7D%0A%3Cdiv%20class%3D%27pull-left%27%3E%7B%25%20admin_actions%20%25%7D%3C%2Fdiv%3E%0A%7B%25%20endif%20%25%7D%0A&language=css%2Bjinja

which does have content= stuff, so not sure what's going on.

Posting other things works just fine.

**Original ticket is:** https://github.com/xray7224/Pamrel/issues/24 I tried posting: ``` {% if action_form and actions_on_top and cl.full_result_count %} <div class='pull-left'>{% admin_actions %}</div> {% endif %} ``` via pamrel-el, and got: ``` HTTP/1.1 500 INTERNAL SERVER ERROR Date: Thu, 09 Apr 2015 16:42:34 GMT Server: Apache Connection: close Transfer-Encoding: chunked Content-Type: text/plain; charset=UTF-8 No content specified ``` But it looks like what I submitted was (as formencoded): ``` content=%7B%25%20if%20action_form%20and%20actions_on_top%20and%20cl.full_result_count%20%25%7D%0A%3Cdiv%20class%3D%27pull-left%27%3E%7B%25%20admin_actions%20%25%7D%3C%2Fdiv%3E%0A%7B%25%20endif%20%25%7D%0A&language=css%2Bjinja ``` which does have content= stuff, so not sure what's going on. Posting other things works just fine.
Jessica Tallon commented 9 年之前
所有者

The error message is actually quite misleading as. The problem that is actually happening here is that the language should be "css+django" and not "css+jinja". I believe that pygments actually accepts css+jinja however, I think for now pamrel will not accept all aliases that pygments accept.

The error message is actually quite misleading as. The problem that is actually happening here is that the language should be "css+django" and not "css+jinja". I believe that pygments actually accepts css+jinja however, I think for now pamrel will not accept all aliases that pygments accept.
Jessica Tallon commented 9 年之前
所有者

I have improved the error messages. This will not make this original issue go away, that will require a change in pamrel-el from "css+jinja" to "css+django".

I have improved the error messages. This will not make this original issue go away, that will require a change in pamrel-el from "css+jinja" to "css+django".
Sign in to join this conversation.
未選擇標籤
bug
未選擇里程碑
未指派成員
1 參與者
正在加載...
取消
保存
尚未有任何內容