That's exactly what happened, but strange thing was it worked just fine
using the filter. I even tried making some SQL queries to fix them for me,
but that didn't work.
Oh well, it's over now ;)
On 1/10/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
>
> On 1/9/07, Stephen Mizell <[EMAIL PROTECTE
On 1/9/07, Stephen Mizell <[EMAIL PROTECTED]> wrote:
> This started throwing all kinds of errors at me about encodings, such
> as:
> 'latin-1' codec can't encode characters in position 19-20: ordinal not
> in range(256)
Almost every time I've seen this (not quite every time, but almost
every time
Well, I gave up on the automation. I couldn't get restructuredtext to
work right in my views, so I swallowed my pride and went into
copy/paste mode. I simple did this:
{% load markup %}
{% for post in posts %}
{{ post.id }}
So it seems the issue is with the restructured text. When using the
restructured text filter on a template, it works just fine. When using
restructured text in a view, it gives me tons of errors.
Any ideas?
--~--~-~--~~~---~--~~
You received this message becau
In our database we have a TextField that stores the body of our posts
in RestructuredText. I've recently added TinyMCE to the Django Admin,
so I'm wanting to convert this field from rst to plain old html.
I wrote a little thing of code to do this with Django.
def convert_post(request):
5 matches
Mail list logo
