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

AEM 6.3 (Latest SP May 9 3.3.4)

Avatar

Avatar
Validate 1
Level 3
sdouglasmc
Level 3

Likes

22 likes

Total Posts

83 posts

Correct Reply

4 solutions
Top badges earned
Validate 1
Give Back
Ignite 1
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 3
sdouglasmc
Level 3

Likes

22 likes

Total Posts

83 posts

Correct Reply

4 solutions
Top badges earned
Validate 1
Give Back
Ignite 1
Boost 5
Boost 3
View profile
sdouglasmc
Level 3

02-06-2019

We upgraded 6.3 to SP 3.3.2.  We have a custom rollout configuration that worked just fine in 6.3.1.  Since moving to 3.3.2 we noticed that the rollout configs were not being inherited from their masters even though everything looked correct.  I doubled back through the .msm. selector and couldn't find the issue - it was defaulting to no rollout configurations not being found so using just the default... by default.

If I replaced the msm-core from 6.3.1 and used it in 6.3.3.2, things went back to working.  I noticed a new CF on May 9th that looked like it might be handling this issue.  However, after installing it, it still does not behave correctly.

What could I be missing?

Replies

Avatar

Avatar
Validate 1
Level 3
sdouglasmc
Level 3

Likes

22 likes

Total Posts

83 posts

Correct Reply

4 solutions
Top badges earned
Validate 1
Give Back
Ignite 1
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 3
sdouglasmc
Level 3

Likes

22 likes

Total Posts

83 posts

Correct Reply

4 solutions
Top badges earned
Validate 1
Give Back
Ignite 1
Boost 5
Boost 3
View profile
sdouglasmc
Level 3

03-06-2019

With 3.3.2 upgrade this used to only show the default configuration - because no configurations could be found, not because it was only set to that.

http://xxx:4502/content/phonakpro/lang/en/home.msm.json (inherits from blueprint)

When I took the msm-core bundle from 6.3.1 and replaced the msn-core .54 version with it, things worked again.  It found our versioning and default configuration.

Same thing happens with 3.3.4... does not work the way it used to.

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

03-06-2019

Please log a daycare ticket with reproducible steps to check if this is a Bug in the 3.3.4 release