March 22, 2014 at 10:47 pm 17087
why if use an html field in order to put this mark-up
March 22, 2014 at 11:49 pm 17092
So you are saying,
March 23, 2014 at 12:12 am 17096
yes and even wrapped by
March 24, 2014 at 1:45 pm 17140
To keep it formatted, it’s wrapped by
. I know you are trying to make it customize in your way, but right now that wouldn’t be possible may be.
March 24, 2014 at 2:36 pm 17149
Sorry but I didn’t understand your answer.
I’m saying that the HTML field doesn’t work as it should.
on the frontend it’s rendered:
This is for me a bug. Cause I should see just a:
I’m I wrong?
March 24, 2014 at 3:52 pm 17161
No you are not wrong. How are you see the HTML? Via firebug or chrome developer tools? These tools shows you by closing the tags if you didn’t already. See it by going actual source, it should be just the
March 24, 2014 at 4:48 pm 17164
First of all, I don’t see the code in the reply..
Then, I use firebug and even if I open the source of the web page I see the tag this way:
March 24, 2014 at 6:12 pm 17172
I’m sorry you are rigt the “autoclose” is generated by Firebug, so the problem at the end is that the html tag it’s always wrapped by the plugin, right?
Is there any workaround for this?
March 24, 2014 at 6:14 pm 17173
The point is that I’m looking for a way to “wrap” a group of fields in order to customize the template..
March 24, 2014 at 6:53 pm 17183
I know what you are trying to do. But the plugin doesn’t autoclose the tags, it just prints whatever you enter on the HTML field.
March 24, 2014 at 6:53 pm 17184
You might try the action hook field too http://docs.wedevs.com/using-action-hook-field/
March 24, 2014 at 11:58 pm 17220
I’ve tried your solution and even the action hook field is wrapped by a
that’s does not make any sense…