I have some filters adding heading tags(markdown and some custom filters). If I put edit_section filter above everything, then it puts the edit links where there is an html heading in the original user input. It is normal behavior I think, because it can't know anything about the filters operating after.
On the other hand if I put edit_section below those filters, it correctly handles and I see edit links just right in the page.
But if I click one of them, a form opens with a content starting from where I click back to the first 'unprocessed' html heading.
So if one pushes an edit link, I think it searches backwards for another heading tag in the 'original node' but not the processed page.
I couldn't think a way to fix this?

Comments

oz_an’s picture

oz_an commented

I think it is not possible loading the filtered cached content to the node edit form and saving it as if it is original user input. The module is loading the original node and naturally searches for start and stop offsets there. Since there is no h tag in my original input, it loads all the node to the form.
I hacked the regex in the module and add a few of the patterns of the filters which manipulate the h tags. It worked. Because it is not only searching for h tags but other tags that I add(like **[section]**,etc]
Is there any other way to let the module know the h tags of other filters when loading the edit form? Because it seems it is just working with the h tags if it is directly in the original user input.

janis_lv’s picture

janis_lv commented

yep, markdown with ## and so on isn't triggering by the section

pifagor’s picture

pifagor commented
Issue summary: View changes
Status: Active » Closed (outdated)