-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New line always added on save #8
Comments
I'm also having this problem. My markdown gets longer and longer every time it's saved. For example, here's the markdown (see the last field):
On the admin page, it looks like this, in the black edit field:
If I click "Save and continue editing", the text in the black field doesn't change, but it changes in the DB:
The If I click "Save and continue editing", the DB has changed again:
Then if I reload the admin page, the black edit field looks like this:
I'd really like to see a fix for this bug please! (Platform: Fedora 20 Linux, mysql) adi-: Is this the same bug you're seeing? |
Yeap, the same. I haven't found a workaround for EpicEditor, so I wrote my own. If you are interested check https://github.com/adi-/django-markdownx |
Hi @adi- and @CapnKernel thanks for reporting this. I am no longer using Django.... I've migrated most of my stuff to Rails (when I needed server side dynamics) or static generator like Nanoc for all the rest. Is your issue related to OscarGodson/EpicEditor#171 or OscarGodson/EpicEditor#363 ? If the bug is coming from EpicEditor then this issue must be reported there; otherwise a patch can be provided, as @CapnKernel propose, by checking the post data e.g. providing a clean_YOURFIELD method which would handle those bad carriage return lines.... @CapnKernel a patch is welcome then :) |
I have noticed some issues while saving/opening documents written in EpicEditor. Editor is always adding break tag to each line of text on open.
Do you know any workarounds? Can it be fixed in Django or is it EpicEditor's issue that you can't fix in django-epiceditor?
The text was updated successfully, but these errors were encountered: