[Neos] Issue with ember overlay

[nikos]

Hi Aske

Thanks for the help got me investigating a bit more.
The problem I am experiencing only occurs when I have a custom content element which is cached separately and then only seems to occur when this is 
added to a TwoColumn Content element.

When looking at the rendered cached output there is a difference between generated cache entries after an edit (overlay problem occurs) compared to 
when the cache is flushed then rebuilt (no overlay problem).

It seems that in the cache after an edit the nodes are referred (rendered) to one level deeper than would be expected(difficult to describe :( )

here are a couple of examples

this is after the cache is flushed and rebuilt
<section typeof="typo3:Reroot.RerootSiteCom:Section" about="/sites/rerootsitecom/helpful-things/main/node-54d7d4946eea7 at user-nickp" ...

<div typeof="typo3:TYPO3.Neos.NodeTypes:TwoColumn" 
about="/sites/rerootsitecom/helpful-things/main/node-54d7d4946eea7/column0/node-54d876d4e5344 at user-nickp" ...

this is what is generated after an edit and the screen overlay problem:
<section typeof="typo3:Reroot.RerootSiteCom:SectionTeaser" 
about="/sites/rerootsitecom/helpful-things/main/node-54d7d4946eea7/column0/node-54d7dbc5e6649 at user-nickp"

<div typeof="typo3:TYPO3.Neos:ContentCollection" 
about="/sites/rerootsitecom/helpful-things/main/node-54d7d4946eea7/column0/node-54d876d4e5344/column0 at user-nickp"


Although both the <section> and <div> are rendered differently depending on whether the cache is flushed or after an edit th eoverlay problme only 
seems to occur if using a TwoColumn node type.

Looks to me as if there is a problem somewhere in the rendering of the cache with TYPO3.Neos.NodeTypes:TwoColumn although I don't know what it is 
exactly. I am not sure what else to do with this, any ideas welcome .

Thanks

Nikos

On 08/02/2015 10:37, Aske Ertmann wrote:
> Hi Nikos
>
> I’ve stumbled upon the same issue before. Turned out to be wrongly generated html output that caused it. It happens because the overlay tries to calculate it’s own height and then sets it to that, but overtime it does the container grows and thus the height is incremented for every calculation indefinitely.
>
> To fix it you should make sure the content you’re outputting has the correct position / wrapping. In my case it was rendered after a content collection instead of inside of it.
>
> Hope that helps.
>
> Cheers,
> Aske
>
>> On 07 Feb 2015, at 20:27, nikos <nick at jamalade.com> wrote:
>>
>> Hi
>>
>> I am wondering why I am getting
>>
>> <div id="ember759" class="ember-view neos-contentelement-overlay" style="width: 1192px; height: 4607964px;"><span></span></div>
>>
>> in my out put when I am logged in the back end.
>>
>> When locking at the page html in a browser the height is in the above is increasing.
>>
>> This overlay is hiding the content underneath.
>>
>> I can't figure out whats wrong, but it only seems to be a problem when I have a cache setting for the overlayed content.
>>
>>
>> Any help here would be approciated.
>>
>> Nick
>> _______________________________________________
>> Neos mailing list
>> Neos at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos
>