Components not editable independently in SP2 Classic | Community
Skip to main content
pakram
pakram
Level 2
October 16, 2015
Solved

Components not editable independently in SP2 Classic

  • October 16, 2015
  • 6 replies
  • 1436 views

We are experiencing a sitewide issue in 6.0 SP2 for Classic UI where components almost seem to "fuse" together and are no longer editable individually. In SP1 this is not an issue. 

To elaborate further, when in edit mode the green border that appears around components should highlight each component individually. Right clicking will allow you authors to edit the components details. This works exactly as expected in SP1. However, in SP2 the green border is drawn around an entire group of components and not individually. Authors cannot delete or edit components individually. Interestingly enough, if an author double clicks on the "fused" component, all the the effected components dialog popups will open at once. 

Anyone seeing this? 

My over simplified graphic illustrating the issue:

[img]sp1-vs-sp2.png[/img]

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by pakram

I believe that I have solved this issue finally. After much poking and prodding, I discovered that the sightly version of parsys had infact changed between SP1 and SP2.

SP1 Sample:
 

data-sly-resource="${paragraph.resourcePath @ resourceType=paragraph.resourceType, decorationTagName='div'}"

SP2 Sample:
 

data-sly-resource="${paragraph.resourcePath @ resourceType=paragraph.resourceType}"

decorationTagName='div' is the difference. If I added this line back to the SP2 version everything works fine.

The Solution if you are having this issue, is to use the .jsp version of parsys instead of sighhtly.

6 replies

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

When you look under /content and open the page in CRXDE lite- are you seeing each component individually? 

Sham_HC
Sham_HC
Level 10
October 16, 2015

Not seen such issue so far. Log a support ticket with below details

*   Affected browser & its version.

*   Steps to reproduce on geometrixx site.

*   Java script error details if any

pakram
pakramAuthor
Level 2
October 16, 2015

Before I file a ticket, let me ask a question first. Are there any known issues with multiple parsys systems from columns?  I noticed just a little bit ago while debugging that our column system seems to reproduce the issue but the Adobe column does not. Here is our code for a two column component.

<div class="group"> <div class="half" data-sly-resource="${'gridHalf1' @ resourceType='wcm/foundation/components/parsys'}">.half</div> <div class="half" data-sly-resource="${'gridHalf2' @ resourceType='wcm/foundation/components/parsys'}">.half</div> </div>

I know adobe uses a different column system but our requirements called for a different class naming convention. Anyway, looking at the code above does anything stand out as incorrect or as having any known defects?

Thanks!

pakram
pakramAuthor
Level 2
October 16, 2015

Yes, all the components are shown individually in the JCR. I attached a screenshot just in case it proves useful. 

[img]Google Chrome-001.png[/img]

FWIW, let me add some additional information that may be related. We initially discovered this issue when using the edit bar. The edit bar would float left when the component was in a right column. Initially we blamed the "Fusing" effect on the edit bar and decided to disable the edit bar. Turns out the issue was not isolated to the edit bar. 

Sham_HC
Sham_HC
Level 10
October 16, 2015

WIth aem6 should not be an issue for multiple or nested parsys,  for 5.6 you might need a fix.   I suspected it is custom implementation that is reason asked for geometrixx.

pakram
pakramAuthorAccepted solution
Level 2
October 16, 2015

I believe that I have solved this issue finally. After much poking and prodding, I discovered that the sightly version of parsys had infact changed between SP1 and SP2.

SP1 Sample:
 

data-sly-resource="${paragraph.resourcePath @ resourceType=paragraph.resourceType, decorationTagName='div'}"

SP2 Sample:
 

data-sly-resource="${paragraph.resourcePath @ resourceType=paragraph.resourceType}"

decorationTagName='div' is the difference. If I added this line back to the SP2 version everything works fine.

The Solution if you are having this issue, is to use the .jsp version of parsys instead of sighhtly.

Terms & ConditionsAccessibility statement

Loading footer...