Hi

I am using a custom template for one part of my site. This template has almost no clever markup.

However, When I add a field to a position, I end up with two additional nested DIVs that I really dont need.

As an example, I have a div in my template with the ID of footer. I get a text field and add it (via a position override with no additional markup) using the getValue call.

When I examine the result with Firebug I end up with:

<div id="footer">
<div id="cck10_Wired-Footer" class="seb_css3 vertical cck-deepest">
<div id="cck10_Wired-Footer_content">
<p>Footer information will go in here</p>
</div>
</div>
</div>

And all the associated CSS that goes with the additional two DIVs.

These added DIVs seem to be added because I have used renderPosition in the template and then used a position override to make sure I just get in the raw data of the field.

So, is there a way of using renderPosition and overrides so that I DONT get additional markup and styling?

Or do I have to simply call fields directly into my template and ignore using position overrides?


Joss

Hi Joss,

Pls check on below links.

www.seblod.com/support/documentation/seb...ng-field-values.html

www.seblod.com/support/documentation/seb...g-101-overrides.html

Thanks Nithin

Yes when I use just the getValue calls directly in my template, I get nice clean data.

But when I use the same calls as a position override instead, then I get additional styling that isn't adding anything useful. In fact it is adding padding values and border values that I really dont want at all.


Joss