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

How to add a new supported language in CQ / WEM (Translator in CQ)

Use case:  You want to add new language to CQ Change display language options in translator grid Change language name and default countries  Solution: You can access translator UI in CQ with following URL http://<HOST>:<PORT>/libs/cq/i18n/translator.html Create new language location for Dictionary Go to CRXDE lite (or your favorite JCR browser) and add this structure (assuming /apps/myapp/i18n as a typical location for custom apps): /apps/myapp/i18n [sling:Folder]     - de [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = de     - fr [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = fr Then reload the translator and the path /apps/ myapp /i18n should show up in the drop-down at the top. Note: the translator will only save translations for languages that are actually present underneath the path (e.g. /apps/myapp/i18n), others will be skipped. Then on jsp pa
Đăng nhận xét
Đọc thêm

Login / Logout on a Publish instance and Closed User Group (CUG)

In CQ5 there is the login logout could be configured using a Closed User Group. Closed User Groups (CUGs) are used to limit access to specific pages that reside within a published internet site. Such pages require the assigned members to login and provide security credentials. http://dev.day.com/docs/en/cq/5-4/howto/create_apply_cug.html The logout using /libs/cq/core/content/login.logout.html always gets redirected to the geometrixx site   http://localhost:4503/content/geometrixx-outdoors/en.html By configuring the Default login page  under the osgi configuration for com.day.cq.auth.impl.LoginSelectorHandler to be – /content/mysite/en/login But still after logout the page goes to the geometrixx site. IIRC, the redirect first goes to to / which then goes through the standard, somewhat complex handling of the root with multiple redirects: 1) / has a resource type of sling:redirect and redirects to /index.html 2) /index.html is handled by the RootMappingServlet [0] which h
Đăng nhận xét
Đọc thêm

[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