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

[DAM] Custom DAM management / Add 'Alt' into images

Issue:

We need, for each asset to be able to edit the ‘alt’ text. The ‘alt’ text must be used on the site each time an asset is displayed.
When displaying an asset, the mechanism is the following :
-       Get the Locale from the request
-       When getting the asset, get the associated Alt property corresponding to the locale.
-       Populate the alt attribute with this value.

Resolution:

To achieve this, we can customize the DAM Asset Editor.
The AssetEditor is the form used to input asset properties and metadata.
Below is a screenshot of a customized form with four “alt” input (for four different locales).

The DAM uses the following nodes to render Asset Editor forms:
-       /libs/dam/content/asseteditors/formitems
-       /libs/dam/content/asseteditors/images/formitems
-       /libs/dam/content/asseteditors/images/jpeg/formitems
-       /libs/dam/content/asseteditors/image/tiff/formitems
We must not modify these files as it is source files for CQ.
But we can copy the /libs/dam/content/asseteditors node (and it’s child nodes) to /apps/dam/content/asseteditors to customize the form.
In this case, several nodes were added with the following specs:
• Label : Alt (or Alt Fr, Fr,…)
• jcr:PrimaryType: cq:Widget
• name: ./dc:alt (or ./dc:altDe…)
• xtype: textfield
etc,etc…..
Below is a representation of the new asseteditors/formitems tree:
Once the form is persisted, the new metadata are stored under the following node :
        /content/dam/{imagepath}/jcr:content/metadata
where now, the metadata node contains the following properties:

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