Remove parbase | Community
Skip to main content
selvaganesh
selvaganesh
New Participant
October 16, 2015
Solved

Remove parbase

  • October 16, 2015
  • 2 replies
  • 2005 views

I am using sightly framework to design frontend components. I want the class <div class="parbase componentname section"> to be removed in publish instance

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Runal_Trivedi

If you are using sightly parsys component in your page component script (i.e. /libs/wcm/foundation/components/parsys) then the default cq generated div tags are auto suppressed you don't need to do anything extra. It is also mentioned on dev.day.com that sightly won't generate default tags - http://docs.adobe.com/docs/en/aem/6-0/develop/sightly.html#resource. You can also verify the same by creating a page template configured on sightly based page component available OOTB at /libs/wcm/foundation/components/page and observe the tag it outputs across the content, you won't see any default CQ tags.

 

Now if you are not using sightly based parsys component and rather using parsys at /libs/foundation/components/parsys in your scripts, then you will need to overlay parsys component under apps and in parsys.jsp you willl need to add following code with necessary publish mode check.

if(mode == publish){ IncludeOptions.getOptions(request, true).forceSameContext(Boolean.TRUE).setDecorationTagName("");; } Also comment following line of code in parsys.jsp //IncludeOptions.getOptions(request, true).getCssClassNames().add("section");

- Runal

2 replies

T
tom_maton
New Participant
July 11, 2016

I'm using sightly in AEM 6.1 and followed the advice above but I'm still getting the wrapped parbase in preview mode or even when I add wcmmode=disabled to the url.

Do I need to add any additional properties for this to work?

Thanks

Runal_Trivedi
Runal_TrivediAccepted solution
New Participant
October 16, 2015

If you are using sightly parsys component in your page component script (i.e. /libs/wcm/foundation/components/parsys) then the default cq generated div tags are auto suppressed you don't need to do anything extra. It is also mentioned on dev.day.com that sightly won't generate default tags - http://docs.adobe.com/docs/en/aem/6-0/develop/sightly.html#resource. You can also verify the same by creating a page template configured on sightly based page component available OOTB at /libs/wcm/foundation/components/page and observe the tag it outputs across the content, you won't see any default CQ tags.

 

Now if you are not using sightly based parsys component and rather using parsys at /libs/foundation/components/parsys in your scripts, then you will need to overlay parsys component under apps and in parsys.jsp you willl need to add following code with necessary publish mode check.

if(mode == publish){ IncludeOptions.getOptions(request, true).forceSameContext(Boolean.TRUE).setDecorationTagName("");; } Also comment following line of code in parsys.jsp //IncludeOptions.getOptions(request, true).getCssClassNames().add("section");

- Runal

Terms & ConditionsAccessibility statement

Loading footer...