Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

p2pdatamessaging node property reverts to disabled after enabling it

Avatar

Level 3

Hello,

In my room console, inside a room:

  1. I enable p2pdatamessaging for a collectionNode
  2. I get the warning that there may be problems if flash player is not 10.3
  3. I click continue
  4. I click somewhere else, eg next collectionNode
  5. After clicking back the p2pdatamessaging is disabled again.

Any tips please?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi Mickey,

Just a heads-up : you're right, someone broke this poor little checkbox =(. We've checked in a fix that will go out in the next release, due in weeks (not months!).

  nigel

View solution in original post

2 Replies

Avatar

Level 3

Am I missing something obvious? Or has this been discussed before?

I cannot enable p2pdatamessaging on any collection node on the UI, not even for simple chat pod.

I can do a video recording if the description is unclear.

Avatar

Correct answer by
Former Community Member

Hi Mickey,

Just a heads-up : you're right, someone broke this poor little checkbox =(. We've checked in a fix that will go out in the next release, due in weeks (not months!).

  nigel

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----