Chuyển đến nội dung chính

[COMPONENT] What is the automatically generated div tag around a component used for / How to remove DIV tag is generated by CQ

Question:

If a component is included for example by the <cq:include> tag, a div tag is added automatically around the component in the generated HTML.
What is this div tag used for and is it possible to suppress the automatic creation of it?

Resolution:

Add the below code in to global.jsp, which you include for all the component jsp's.

if (WCMMode.fromRequest(request) != WCMMode.EDIT && WCMMode.fromRequest(request) != WCMMode.DESIGN) {
         IncludeOptions.getOptions(request, true).forceSameContext(Boolean.TRUE);
}

This will not generate any more extra <div> tags for any number of components you add.

Reference:

This div tag is used for the editing system of CQ5 (drawing the edit bars, rollover frames etc), the Designer system of CQ5 (set CSS class name, Designer CSS styling) and also for identifying the component in the client DOM.

It's possible to suppress this generated div tag either by specifying an empty property cq:cellName in the component definition (see How are Design Cell Ids built) or by using the IncludeOptions.forceSameContext(true).
Note: In both cases, you won't be able to edit the component anymore (i.e. no dialogs).

The generated div tag has always at least a CSS class name attribute built from the cell name of the component (see How are Design Cell Ids built) used for the CSS styling of the component.
This CSS class name attribute can't be suppressed.
It's possible to add additional attributes for this generated "DIV" tag by the node cq:htmlTag in the component definition.
Each property of this node will be added as tag attribute.
It's also possible to 'overwrite' the CSS class name attribute of the div tag by adding the property class in the node cq:htmlTag.
In this case the cell name is not added automatically anymore. Therefor the css relevant design properties from the design dialog (added to the generated Designer css file) have no effect anymore -> the cell name has to be added to the property class in the node cq:htmlTag manually.
The automatically generated Designer css file (/etc/designs/<designname>.css) includes the css relevant design properties form the design dialog with the css class name equal to the component div. You have to make sure that the css class names from your static css file (/etc/designs/<designname>/static.css) don't clash with this names!

CQ5.3 and above

Starting with CQ5.3, a new and more dedicated API has been implemented that allows for better control of (automatically created) decoration tags:
option for specifying the tag name for a component (cq:htmlTag/cq:tagName property)
option for controlling the tag per include: IncludeOptions#setDecorationTagName
option for controlling the default tag name: ComponentContext#setDefaultDecorationTagName
All the options above allow to suppress the decoration tag if set to an empty string.

Question:

How to remove the "DIV" which is generated by CQ

Answer by Adobe consultant:

CQ wraps each component in with a specific "<div>" when rendering an HTML page. As mentioned in this online article (http://helpx.adobe.com/experience-manager/kb/ComponentDiv.html), it is not possible to remove the wrapping <div> without loosing the editing capabilities of a given component. If you need to remove the <div> (and as such disable the editing capabilities) you can do so by either specifying an empty property cq:cellName in the component definition (see How are Design Cell Ids built) or by using the IncludeOptions.forceSameContext(true) in the JSP code.
An alternative option is to remove the <div> in publish mode only (ie WCMMODE != edit and WCMMODE != design) but you will probably end up having a different look and feel in author mode. Since the generated HTML code will be different in author, the CSS rules defined in your application code will react differently than on the publish mode (without the extra div). To remove the wrapping <div> only in publish mode, add the following code in your JSPs:

if (WCMMode.fromRequest(request) != WCMMode.EDIT && WCMMode.fromRequest(request) != WCMMode.DESIGN) {
}

The recommendation from Adobe Consulting is to leave the wrapping "<div>" tags and work with the front- end development team to take these tags in account when designing HTML code running on CQ.

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene...
Đăng nhận xét
Đọc thêm

[Query Builder] Advanced Search

Using the Advanced Search When using a list, select from the 'Build list using' options 'Advanced Search.' This will open a new tab in the list window with one text box labeled: 'Querybuilder Predicate Notation.' This is asking for a few lines of code to define search parameters. Example Code - With Explanations of Results Searching for Pages type=cq:Page property=jcr:content/jcr:title property.value=Places 'type' defines what sort of object you'll be searching for (it's usually a page). 'property' defines what property of the object you'll be filtering by; in this case, its by the title. 'property.value' defines your search term. So this search would be searching all PAGES with the TITLE of PLACES. So it would find every page titled Places. *IMPORTANT* Searches by title ARE case-sensitive, so 'Places' is not the same as 'places'. type=cq:Page path=/cq/sandbox property=jcr:cont...
Đăng nhận xét
Đọc thêm

[CQ6-SYSTEM] MAINTAINING THE REPOSITORY - Reduce repository size (cleanup repository)

Compacting Tar Files As data is never overwritten in a tar file, the disk usage increases even when only updating existing data. To make up for the growing size of the repository, AEM employs a garbage collection mechanism called Tar Compaction. The mechanism will reclaim disk space by removing obsolete data from the repository. Revision Clean Up By default, tar file compaction is automatically run each night between 2 am and 5 am. The automatic compaction can be triggered manually in the Operations Dashboard via a maintenance job called Revision Clean Up. To start Revision Clean Up you need to: Go to the AEM Welcome Screen. In the main AEM window, go to Tools - Operations - Dashboard - Maintenance or directly browse to http://localhost:4502/libs/granite/operations/content/maintenance.html Click on Daily Maintenance Window. Hover over the Revision Clean Up window and press the Start button. The icon will turn orange to indicate that the Revision Clean Up ...
Đăng nhận xét
Đọc thêm