Using External HTML adds anchor tags that break things

bgruebmeyer

I have a php page that works fine outside of Lectora. When I place it in Lectora using the Add External HTML feature, it wraps each place with a DIV that shows visibility set to inherit. It also adds an anchor tag around multiple objects in a format like: [/CODE] with visibility set to inherit. Because these anchor tags do not have IDs, I have not been able to successfully hide their existence from the page - resulting in layout issues, extra spaces appearing where it shouldn't, overriding of visibility css.

Has anyone found a work around for this issue? Is there a way to stop the external HTML from being tampered with?

~ Becky[CODE][/CODE] with visibility set to inherit. Because these anchor tags do not have IDs, I have not been able to successfully hide their existence from the page - resulting in layout issues, extra spaces appearing where it shouldn't, overriding of visibility css.



Has anyone found a work around for this issue? Is there a way to stop the external HTML from being tampered with?



~ Becky

ssneg

Why not get it by name?

http://www.w3schools.com/jsref/met_doc_getelementsbyname.asp

ray-gesualdo

I ran into this same problem while I was adding custom jQuery interactions in Lectora. It is due to Lectora positioning the closing tag for in the wrong spot. To correct this, I ended up putting my own at the very beginning of my External HTML object. This seems to do the trick.



Before:



[INDENT]your code[/INDENT]

[/CODE]

After:
[CODE]

[INDENT][/INDENT]
[INDENT]your code[/INDENT]

[/CODE]

Note: If you look at the source code, you'll notice that Lectora still keeps it's own after the entire object (whose position is what's causing this issue in the first place), but don't worry about it. Browsers will simply dump the extra closing tag.

Hope that helps![CODE]

your code

[/CODE]



After:



[INDENT][/INDENT]
[INDENT]your code[/INDENT]

[/CODE]

Note: If you look at the source code, you'll notice that Lectora still keeps it's own after the entire object (whose position is what's causing this issue in the first place), but don't worry about it. Browsers will simply dump the extra closing tag.

Hope that helps![CODE]

your code

[/CODE]



Note: If you look at the source code, you'll notice that Lectora still keeps it's own after the entire object (whose position is what's causing this issue in the first place), but don't worry about it. Browsers will simply dump the extra closing tag.



Hope that helps!