V14-RC3 - Not able to page back when having many content nodes in the content tree

nikcio commented 5 months ago

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.0.0-rc3

Bug summary

When the content tree has a lot of nodes a "Load more" button becomes visible but after clicking this there is no indication of what page you are on. There is also no indication of the total items or a way to go to the previous page.

https://github.com/umbraco/Umbraco-CMS/assets/24605285/2e80790a-dc26-4214-bc33-67c6d1c31348

Specifics

No response

Steps to reproduce

Create a lot of content nodes.
Scroll down and press the "Load more" button

Tip: To quickly create a bunch of content nodes you can add a API endpoint in the program.cs like this:

app.MapGet("/create-content/{number:int}", ([FromServices] IContentService contentService, int number) =>
{
    for (int i = 0; i < number; i++)
    {

        contentService.CreateAndSave($"Home-{Guid.NewGuid()}", -1, "home");
    }

    return Results.Ok("Done :)");
});

Expected result / actual result

I would expect to see the total content items, load more, and be able to go back if pagination is the way we want this tree to function.

Alternatively I think it would be a better solution to use a virtual scroller here as this wouldn't require showing the total nodes and you would always be able to scroll back up to the other content nodes.

github-actions[bot] commented 5 months ago

Hi there @nikcio!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
We'll replicate the issue to ensure that the problem is as described.
We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:

Zeegaan commented 5 months ago

Heyo! 👋 I think this is more of a feature request than a "bug", as i agree it's a little confusing, but it's by design 🤣 I will pass this on to the frontend team to get a better view on this 😊

Zeegaan commented 5 months ago

I am getting word that it should be fixed in rc4, please re-open this if the issue still persists there 😁

umbraco / Umbraco-CMS