It should be downloaded from maven repository
Central Repository: org/apache/jackrabbit/filevault-package-maven-plugin
can you check your maven settings?
It should be downloaded from maven repository
Central Repository: org/apache/jackrabbit/filevault-package-maven-plugin
can you check your maven settings?
Can you please tell us the use case? Its true you will not get functionality like iparsys using XF.
But rather you can you XF variations.
I would say, ignore this if this is because of DOM classes you mentioned in the screenshot.
This is the edit view and space may be required to differentiate components, if you will fix this space, it may end up creating other issues.
If you still see the issue in wcm disabled mode, just check the DOM and let us know.
Please check this if helps
you can write a Listener on child node delete event and check parent node has no children then delete parent node as well.
or write a sling scheduler to check an empty node and clear periodically.
Thanks.
You can add a checkbox in page property dialog and based on the switch you can add or remove snippet. To take advantage of inheritance you can use inheritedPageProperties
Example -
<sly data-sly-test="${inheritedPageProperties.isEnable}">
// script
</sly>
I would recommend you to use tabs resource type to create container to take input.
Now for your requirements :
1. hide all the tab expect the current tab using javascript to inject hide class.
2. Add next and previous button using javascript of dialog load event.
3. Add event handler on next button to remove hide class from next tab and add hide class to other tabs.
4. Add event handler on previous button to remove hide class from previos tab and add hide class to other tabs
5. To save only specific data make other data empty.(or use @Delete hint)
I know this is the lot of customization.
please check this blog
Please check
How to add clientlibs to cq:dialog?
How to access the metadata node to add additional property on DAM UPDATE ASSET using custom workflow?
Hi,
For adding custom properties to asset meta data, we need to add custom workflow process step to "Dam Update Asset" workflow.
Go to /libs/settings/workflow/models/dam/update_asset.html ,edit the workflow model ,add Process Step component and select your custom process step and save it.
For creating custom workflow, you can refer below
https://helpx.adobe.com/experience-manager/using/message_service_gateway_api_64.html
http://www.6dglobal.com/blog/creating-custom-CQ-workflow-process-step-2014-10-14
I created a process, added it to DAM UPDATE ASSET and it's all working fine. What I'm troubling with is how to access the metadata node in the execute() method to add properties to it.
you should be able to fix it via column settings. To access Column Settings, drag a Freeform Table to the project, then click the gear icon in the column heading. Column settings
To fix - Enable Interpret zero as no value - Determines for cells with a 0 value, determines whether to show a 0 or a blank cell.
Why the Nov 24 data come out in the report from Nov 25 to Dec 1 report?
We are using AEM 6.5 with React SPA. We want to get the content fragment models data in to React as JSON.
Expectation is make use of CF models properties data to built UI.
Any inputs here? or any suitable approach here.
Has anyone blogged or any insights to share about direct call rules and especially about the amount of rules to manage - less is better or not? I'm pretty sure answer eventually depends size and complexity of site and what else you might want to populate (custom code etc) based on rules. Let's take example. All the basic page tracking is done through extension, but you might have few shopping funnels and lots of different actions to track.
_satellite.track('start_shopping_funnel', {variable1: 'value1', variable2:'value2'} );
_satellite.track('shopping_funnel_phase2', {variable1: 'value1', variable2:'value2'} );
_satellite.track('shopping_funnel_order_completed', {variable1: 'value1', variable2:'value2'} );
OR would just use one direct call rule like this:
_satellite.track('view', {view: '<phase>', variable2:'value2'} ); // and <phase> is either "start", "phase2" or "order_completed".
My initial experience with coders is that they prefer first option to have multiple rules that are easier to understand and even Launch settings would be easier to do when you could populate (without custom code) eventX with first rule and the other rule could populate eventY. Or if you need to send data to other tools based on these rules the amount of custom code would be less on different rules etc.
However, it would be so tempting to use only one rule and that way the specs would be so much easier to do and if there are additional steps in the shopping funnel then coder could just add another "view" value without the need to do new rule in Launch. And if you need to add new variable through Tag Manager or hard-code it to the site then again less work with only one rule.
If I would use only one rule for all additional "views" then there could be another rule for "action" that could contain all kinds clicks etc. Again, you could ask would it be better to do multiple rules for different actions or just one rule like this:
_satellite.track('action', {action: '<action_name>', variable2:'value2'} );
Any comments or blogs to share about this?