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

IParsys issue

Avatar

Avatar
Validate 10
Level 3
vijayk87714775
Level 3

Likes

12 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
vijayk87714775
Level 3

Likes

12 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
vijayk87714775
Level 3

20-06-2018

Hi All,

In our project, we're seeing an issue with iParys. The component is available on both Dev1 and Dev3 environment. On Dev3 , I'm able to edit the iParsys on all parent and  child pages but on Dev1 I am unable to edit even though same set of permission is there in both the environments.

When I inspect on iParsys, in markup I could see the class "is-disabled" is there on Dev1 environment page but on Dev3, on both parent and child pages . Code wise everything is same on both environments and no difference at all. and used ootb   resourceType='wcm/foundation/components/iparsys' .

And can edit all the Parsys on the page . I can be able to perform all actions (add ,del,copy) on both Dev’s. Only issue is with the Iparsys container. What could possibly be wrong? If it's the issue with permission then how can I figure out? Cos' I've already created permission package from UAT and deployed on INT. Still the issue persists .

Thanks in advance.@

Iparsys-issue.png

ashu4pma

Replies

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

20-06-2018

What AEM Version are you using?

Avatar

Avatar
Validate 10
Level 3
vijayk87714775
Level 3

Likes

12 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
vijayk87714775
Level 3

Likes

12 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
vijayk87714775
Level 3

20-06-2018

Hi Smac , we are using AEM 6.2 CFP14

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

20-06-2018

Also - can you please explain what you are trying to accomplish with IParsy. If using AEM 6.3/6.4 and you want to control components - lock some, control which components an author can use, etc - look at using editable templates - which are much better then using IParsy.

Read this that explains the benefits of IPARSY: Centralizing configuration data using an Inherited Paragraph System

All of this can now be accomplished via editable templates and policies. Once you move to 6.3/6.4 - use editable templates over IPARSY.

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

20-06-2018

Ok 6.2 - you cannot use editable templates - are you see any browser error?

Avatar

Avatar
Validate 10
Level 3
vijayk87714775
Level 3

Likes

12 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
vijayk87714775
Level 3

Likes

12 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
vijayk87714775
Level 3

20-06-2018

Hi Smac ,       No sign of any error. Checked on the browser console and also in the error logs. Thanks.

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

20-06-2018

Read the doc I referenced and see if it helps you -- Centralizing configuration data using an Inherited Paragraph System

When you update to AEM 6.4 - I strongly recommend that you use Editable Templates as opposed to IParsy -- Scott's Digital Community: Guided Journey for Experience Manager on Editable Templates