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

[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

[ENVIRONMENT] Author and Publish environments (codes, bundles) out of sync

ISSUE: I have configured two environments of CQ5.5, Author (at 4502) and Publish (at 4503). Initially, when I just created pages based on default templates, the publishing went on just fine. I even activated using workflows.. However, when I created my own components/templates/jsp's, the pages stop getting fdeployed on Publish Environment. Now, even after activation (green light), the pages on publish environment display just a blank page and nothing else. I checked and found that all my new components/templates/jsp's etc. are not present in the 4503 node. Any way to keep them in sync ? RESOLVED: The issue isn't that your pages aren't being activated. They are likely in fact being activated just fine. You can verify this by examining the content tree on your publish instance. The issue is that the components you created and are using on those pages aren't present on the publish instance - as you noted. It's important to keep in my that CQ won't...
Đăng nhận xét
Đọc thêm