No progress. I don't believe hat debug point is not relevant; this issue is
deep in the editor itself because you can reproduce it by typing an empty
div into the html field in the editor ('<>') and then switching back to the
normal source - the ' ' and extraneous <p>....</p> elements are
inserted then... long before you start cleaning stuff up in mezzanine.Cheers, Paaul On Fri, 11 Sep 2015 at 04:32 Ryne Everett <[email protected]> wrote: > Did you make any progress on this? It sounds like a bug but I let it go a > few days because I was hoping somebody would have some more specific > insight. > > The first thing I'd probably do is drop a debugger in RichtextField.clean > (in mezzanine/core/fields.py) and make sure `settings.RICHTEXT_FILTER_LEVEL > == RICHTEXT_FILTER_LEVEL_NONE` is true and that the `value` is still > correct at that point. > > > > On Mon, Sep 7, 2015 at 2:40 PM, Paul Whipp <[email protected]> wrote: > >> >> I have a user working with Mezzanine 4.0.0/Django 1.8.3 >> >> They are using simple google charts to illustrate various things (all the >> data is included with the chart on the page like the standard google chart >> examples). >> >> The charts do not present correctly even though they work fine in plain >> html files tested locally. >> >> I believe the reason for the incorrect presentation is that when the user >> pastes the code into the html source, ' ' gets added into the empty >> divs placed for the charts. This reproduces the same error on a local test >> file. >> >> I'm not sure why this padding is added by the admin page editor and I >> can't remove it without it adding it straight back. If I edit '<>' remove >> the ' ' from the div content and then click OK. Opening the editor >> again shows the ' ' added right back again (and a paragraph wrapped >> around the javascript which is strange but does not seem to be causing a >> problem). >> >> 'no filtering' is set. >> >> Is there any way that I can get the 'source' edit to simply allow a >> source edit with no interference from probably well meaning but (in this >> case) bugged interference? >> >> Cheers, >> Paul Whipp >> > -- >> You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. > > >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Mezzanine Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/mezzanine-users/j4Mhu42hHlw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
