Using htmlarea in conjunction with the attached_node.module produces a conflict. Don't know if it is due to the order of the input filters, but here is the problem and solution so far.

Scenario: Some text, then the node:ID codes and end of paragraph using the htmlarea editor. Result is (omitting the darts from the codes):

p ... yada yada node:507 /pp and start of next text /p
----------- problem here ^^ ----------

Result is that the text following the node:ID code is not shown when the page is rendered.

The htmlarea editor forces the paragraph end code and the next paragraph begin code to butt against one another. SOLUTION: Put one hard return thusly:
p ... yada yada node:507 /p
p and start of next text /p

The attached_node will then properly render and the following text will display. I can replicate this. Took 1-1/2 hours to figure it out by experimentation.

gil

Comments

javanaut’s picture

javanaut commented

Do you have any of the other tag-based modules installed? Since I modeled this after the image filter (4.4 version), I'm curious to see if others are affected by the use of htmlarea. If so, then perhaps htmlarea can be altered to accommodate the tag-based modules.

I'll look into it either way.

Thanks,
-Mark

Capnj’s picture

Capnj commented
Status: Active » Closed (fixed)

I'm closing this due to (a) the htmlarea issues in 4.6 which I'm now using and (b) that the author is aware of it and can re-open if this is still an issue.