Beginner Question: content tree problems in ui

Using Neos & Flow
1

Hi,

i just installed a new neos instance, simply following the tutorial in the docs ( Code Q Neos-Skeleton).

Installation went fine, system is up and running, i am logged in in the backend.

Now, when i start to add some “Standard Pages”, the pages get created ok, and i can publish them to live o.k.

but the content tree on the left side in the ui is quite shaky, i have to constantly click on the refresh button, otherwise only one of the page nodes stays visible:

for example:

  • click refresh: three page nodes are visible.
  • click on a page node: editor view changes to correct page, but the content tree also changes and the other page nodes in the treenodes on the left side disappear.
  • click on refresh in the node browser: page nodes are back.

this behaviour is driving me crazy.

is this a known problem, what can i do to get a reliable content tree view?

specs of the installation:

  • working on mac m1 laptop
  • installed php 8.0 and composer
  • using postgres db.
  • installation: just as documented in your neos tutorial with the codeq skeleton.

Thanks,
Max

2

Hi Max,

welcome to the community!
Sounds very unusual, I’m not aware of that issue.

So just to fully understand, you have issues with the page tree or the content tree, or both?

I assume if you did a fresh install you run Neos 7.3.1, can you verify that?

Regards
Seb

3

Hi,

sorry, i should’ve been more precise in my description of the issue:

it’s the page tree i am talking about, not the content tree.
Admin > Package Management shows: noes/neos 7.3.1 and neos/neos-ui 7.3.1.

two things i can add to my experience:

  1. adding a new page: and i get the “shaky” page tree.
    stopping neos and flushing caches: then the page tree is o.k. until i add another page.

  2. it’s happening not only on my mac, tried it yesterday on a linux machine: same behavior. also tried with different browsers: safari, firefox, chromium. no difference.

maybe it’s some setting in the codeq skeleton, because that’s what i am using, following strictly the tutorial in the docs.

Thanks,
Max

4

Ok thx, can’t reproduce this issue in my Neos 7.3.

Maybe you can also provide a short screencast which might make it easier for us to reproduce / understand.

Do you also have a stock Neos 7.3 with the Demo site setup where you can compare the behaviour?
Then we know if its the skeleton or some general ui issue.

5

Short screencast: neos_skeleton

will try to setup a stock neos 7.3.1 with the demo site in the evening or tomorrow.

thanks,
max

6

Did a quick install now without the codeq skeleton:

composer create-project neos/neos-base-distribution neos-example

Install and import of Neos.Demo worked, and here i am NOT getting this weird Document Tree behavior. Can add pages and the document tree is working as expected.

Max

7

is this the same issue? Slack

8

Hi guys,

i just opened an issue in the repo of the neos skeleton project of codeq, maybe they have an idea.

Since the problem doesn’t seem to happen, when working without the codeq skeleton, i will move on with my neos tests by just starting a project from scratch, without any template. should be better for the learning experience anyways.

thanks for your feedback,

Max

1 Like
9

Thanks for your feedback. I do not think that’s a bug of the skeleton, since the endpoint is not in any way manipulated.

10

I could reproduce the issue too, this is my setup:

  • Linux
  • Neos run with flow server:run
  • MariaDB in a Docker container
  • Neos 7.x or also 8.x

Creating a site from scratch using the site kickstarter the issue did not appear.
Using the CodeQ sekeleton site package, the same issue could be reproduced.

Till now I could not figure out yet where the issue is. Interesting fact is, that after flushing the cache the issue disappears and it appears again if I create other new pages in the document tree.

So my assumption is that it has to do something with the Caching config…

11

I think I have found the issue by accident :slight_smile: @maxodoble, @rolandschuetz, @Marc and @sebobo.

The source of the problem is the Footer.fusion file and its cache configuration: Neos-Skeleton/Footer.fusion at master · code-q-web-factory/Neos-Skeleton · GitHub

    @cache {
        mode = 'cached'
        entryIdentifier {
            site = ${site}
        }
        entryTags {
            1 = ${Neos.Caching.nodeTag(site)}
        }
    }

If I remove the cache config or if I adapt it to this:

  @cache {
    mode = 'cached'
    entryIdentifier {
      site = ${site}
    }
    entryTags {
      1 = ${Neos.Caching.nodeTag(site)}
      2 = ${Neos.Caching.descendantOfTag(site)}
    }
  }

The “content tree disappear” issue seems to be resolved.

Currently I don’t understand yet why this is the cause.

Maybe a real Neos Cache and Neos UI expert has some answers. I assume that there were some changes in the handling of this Cache config in the past maybe before Neos v7.4?

The docs Caching - Rendering - Manual - Neos CMS - Neos Docs mention, that the entryTags should always contain the node identifier if the cache mode is set to cached. But then my question would be: how do you define a Cache config for a Footer component which should only be flushed if the site node changes because you store the Footer data/items on the site node directly? The idea behind is that the Footer is always the same on every page and it stores its data on the site node. Or is this pattern not a good pattern for such a case?

1 Like
12

If you can reproduce the issue an issue on Github for the neos-ui package would be helpful for us with detailed information.

For an actual globally cached footer you should take a look at my related blog post Globally cached fragments in Neos CMS - Blog - Mind the Seb

1 Like
13

Thanks @sebobo for the link to the Blog article!

Regarding “Creating a Github issue”: I’m not very sure yet, if it is really an issue in the “Neos UI” package. Maybe it is just a wrong usage or config of the cache for this Footer component?

14

The Content Tree in the UI shouldn’t be affected by the rendered content. I removed that dependency in Neos (UI) 7.2. If this still happens, then it’s a bug.

2 Likes
15

I see this makes sense, thanks @sebobo.

I have created a bug report here: Newly created pages in the document tree disappear/are not displayed · Issue #3248 · neos/neos-ui · GitHub

2 Likes