Wednesday, 4 June 2014
Monday, 19 May 2014
Adobe AEM/CQ invalidate cache and rebuilding libraries
/libs/granite/ui/content/dumplibs.rebuild.html
Thursday, 10 April 2014
Adobe AEM/CQ - Repository Inconsistency
http://helpx.adobe.com/experience-manager/kb/RepositoryInconsistency.html
My current project is running into some IndexNotFound exceptions which is caused by repository being inconsistent.
I ran the ConsistencyCheck as per the article in the link above but it came back with 699 unrepairable nodes.
I used the query-builder to search for one of the complaining missing node and it turns out that the culprit node(s) were from CQ itself:
Results:
So we decided to re-index the repository:
The repository inconsistent related errors were gone initially, but it returned to haunt us again. So far this haven't impact any functionality or performance, but it is still a risk that it might become worst.
We are leaving it for now as we have ran out of ideas, I'll keep myself posted here.
Update 1:
Change of events, apparently the way I search the uuid in querybuilder is incorrect. The correct query to be use should be:
And it returns nothing from that query...
Battle continue...
My current project is running into some IndexNotFound exceptions which is caused by repository being inconsistent.
I ran the ConsistencyCheck as per the article in the link above but it came back with 699 unrepairable nodes.
I used the query-builder to search for one of the complaining missing node and it turns out that the culprit node(s) were from CQ itself:
1. Access http://[host]:4502/libs/cq/search/content/querydebug.html 2. Search with:path=/content uuid=[complaining-missing-node]
/content/catalogs/content/catalogs/jcr:content/content/campaigns/content/campaigns/jcr:content/content/dam/content/dam/rep:policy/content/dam/rep:policy/allow/content/dam/jcr:content/content/dam/mac/content/dam/hierarchy
So we decided to re-index the repository:
1. Stop the CQ instance 2. Rename the index directory in - crx-quickstart/repository/repository/index - crx-quickstart/repository/workspaces/crx.default/index 3. Start the CQ instance
The repository inconsistent related errors were gone initially, but it returned to haunt us again. So far this haven't impact any functionality or performance, but it is still a risk that it might become worst.
We are leaving it for now as we have ran out of ideas, I'll keep myself posted here.
Update 1:
Change of events, apparently the way I search the uuid in querybuilder is incorrect. The correct query to be use should be:
path=/content property=jcr:uuid property.value=[complaining-missing-node]
And it returns nothing from that query...
Battle continue...
Tuesday, 8 April 2014
Monday, 7 April 2014
Adobe AEM/CQ - bundle version comparison
http://dev.day.com/content/dam/day/onlinetool/COI.html
- Paste JSON from http://host:port/system/console/bundles/.json into the text fields. Click "Compare" to see the diff.
- Similar bundles are displayed in white.Changed bundles version are displayed in yellow. Newly added bundles are displayed in Aqua. Deleted bundles are displayed in light red.
- Clear them by clicking "Clear"
- After Compare. Filter the data using select box. More Details at http://experiencedelivers.adobe.com/cemblog/en/experiencedelivers/2012/11/how_to_sanity_checkosgibundlesacrossenvirnoments.html
Thursday, 13 March 2014
Gmail - hidden ways to filter out emails
http://gmailblog.blogspot.com.au/2008/03/2-hidden-ways-to-get-more-from-your.html
Posted by Robby Stein, Associate Product Marketing Manager
I recently discovered some little-known ways to use your Gmail address that can give you greater control over your inbox and save you some time and headache. When you choose a Gmail address, you actually get more than just "yourusername@gmail.com." Here are two different ways you can modify your Gmail address and still get your mail:
For me, the real value in being able to manipulate your email address is that it makes it really easy to filter on those variants. For example you could use hikingfan+bank@gmail.com when you sign up for online banking and then set up a filter to automatically star, archive or label emails addressed to hikingfan+bank. You can also use this when you register for a service and think they might share your information. For example, I added "+donation" when I gave money to a political organization once, and now when I see emails from other groups to that address, I know how they got it. Solution: filtered to auto-delete.
Posted by Robby Stein, Associate Product Marketing Manager
I recently discovered some little-known ways to use your Gmail address that can give you greater control over your inbox and save you some time and headache. When you choose a Gmail address, you actually get more than just "yourusername@gmail.com." Here are two different ways you can modify your Gmail address and still get your mail:
- Append a plus ("+") sign and any combination of words or numbers after your email address. For example, if your name was hikingfan@gmail.com, you could send mail to hikingfan+friends@gmail.com or hikingfan+mailinglists@gmail.com.
- Insert one or several dots (".") anywhere in your email address. Gmail doesn't recognize periods as characters in addresses -- we just ignore them. For example, you could tell people your address was hikingfan@gmail.com, hiking.fan@gmail.com or hi.kin.g.fan@gmail.com. (We understand that there has been some confusion about this in the past, but to settle it once and for all, you can indeed receive mail at all the variations with dots.)
For me, the real value in being able to manipulate your email address is that it makes it really easy to filter on those variants. For example you could use hikingfan+bank@gmail.com when you sign up for online banking and then set up a filter to automatically star, archive or label emails addressed to hikingfan+bank. You can also use this when you register for a service and think they might share your information. For example, I added "+donation" when I gave money to a political organization once, and now when I see emails from other groups to that address, I know how they got it. Solution: filtered to auto-delete.
Subscribe to:
Posts (Atom)