Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

keithbsalmon
Community profile keithbsalmon Level 2
Job title here
Location here
3 BADGES
Level 2

Level 2

Learn more
Joined the community 03-01-2018 8:22:52 AM
Offline
Top badges earned by keithbsalmon
Customize the badges you want to showcase on your profile
Re: Programmatically creating new Catalog Section pages
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
Thanks for your quick reply, yes it does have those. However the page that get's created using Classic UI doesn't have them and still gets rolled out. If I go ahead and create another catalog after adding the new section page, it will build the new section page. It's purely when rolling out changes to an existing catalog that a new page doesn't get rolled out. I can see in the sectionRolloutHook() it processing the existing section pages but the hook isn't being triggered for the new section pag...

Views

515

Likes

0

Replies

0
Programmatically creating new Catalog Section pages
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
We're running into a problem where rolling out changes to a Catalog Blueprint isn't propagating new section pages when they are created programmatically using the PageManager API.Take a Catalog Blueprint that was created programmatically and is located at:Creating a Catalog in Sites from this blueprint in Touch UI using Create > Catalog works fine and the catalog including all section and product pages are created as expected.If you create a new section page either through Touch UI:or even in Cl...

Views

689

Like

1

Replies

2
Is there a recommended alternative to the Generic Lists feature offered by the acs-aem-commons package?
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
As you know there is a Generic List feature offered by the acs-aem-commons package here:https://adobe-consulting-services.github.io/acs-aem-commons/features/generic-lists/index.htmlAs far as I am aware this isn't yet compatible with the Touch UI so I'm wondering if there is a recommended alternative to allowing authors to manage a list of string key value pairs that don't need any localization?

Views

275

Likes

0

Replies

0
Re: Further strange VLT behaviour
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
Version 3.1.40 is giving me a null pointer exception too:

Views

657

Likes

0

Replies

0
Re: Further strange VLT behaviour
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
Yes it is strange indeed. We are using the this version:I've tried the latest (version 3.1.42) however that returns a null pointer exception, I'm about to try version 3.1.40.Here's where the filter file is located:I wonder if this is related to this other unexpected behaviour I reported....When exporting using VLT the behaviour changes for a specific workspace filter when adding another filter

Views

657

Likes

0

Replies

1
Further strange VLT behaviour
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
When executing the following VLT commandvlt --credentials XX:XX export -v http://localhost:4502/crx / ./src/main/contentUsing the following filter.xml I expected only nodes that end with .gif would get exported. As per the official Jackrabbit Filevault documentation here: Jackrabbit Filevault - Workspace Filter It states:However, what get's exported is this:

Views

935

Likes

0

Replies

6
When exporting using VLT the behaviour changes for a specific workspace filter when adding another filter
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
When exporting content from the JCR using VLT with the following:Commandvlt --credentials XXX:XXX export -v http://localhost:4502/crx / ./src/main/contentfilter.xml All goes as expected and using one file as an example this is what gets exported:../src/main/content/jcr_root/apps/gtsp/components/common/Container/.content.xmlHowever if I add another filter (/conf/gtsp) to the filter.xml as shown below the behaviour for the existing (/apps/gtsp) filter changes Using the same file as before this is...

Views

200

Likes

0

Replies

0
Re: PageManager API not creating components
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
Thank you so much for the responses, I've been asked to focus on something else for a short while but I will be returning to this very soon.

Views

375

Likes

0

Replies

0
PageManager API not creating components
Avatar
Validate 1
Level 2
keithbsalmon
Level 2

Likes

3 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
keithbsalmon
- Adobe Experience Manager
Using AEM 6.3.We are generating some recipe detail pages programmatically based on recipe data using the PageManager API.The recipe detail page is based on a template which contains a collection of components.When creating a recipe detail through the Touch UI (Sites > Create > Page > Template: Recipe Detail > Name: RecipeTest) the page is created as shown below.RecipeTest Node Propertiesjar:content Node PropertiesHowever, when using the PageManager API as illustrated in the code snippet below, w...

Views

917

Likes

2

Replies

8
Likes from