Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preserve the load order on the pages list in Calypso when there are more then 50 pages. #68121

Closed
2 tasks
KirkwallDay opened this issue Sep 21, 2022 · 27 comments
Closed
2 tasks
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Interaction #] > 10 (Automated) interaction count label for better visibility. Please don't add these manualliy. [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended [Type] Feature Request Feature requests

Comments

@KirkwallDay
Copy link

What

Currently, when the page count exceeds 50 pages, the load order in Calypso changes to last edited post only. Before that, it will show parent pages above their child pages, after it will not. Also, it adds a - at the beginning of the page title, this should also be removed.

Before 51 pages:
Screen Shot 2022-09-21 at 12 38 59 PM

After 51 pages:
Screen Shot 2022-09-21 at 12 40 36 PM

Gallery has moved much further down the page list, and now has a - to indicate it's a child page, but it's parent is much further up the list now.

Two customer reports:

  • 5563725-zen
  • 5575173-zen

Why

This can be confusing for users to determine which pages have children, and also when they cross the 51 page threshold the view suddenly changes and is also a confusing experience.

How

It would be best if we can keep the old view, there is discussion about this, in this issue: #60280 (comment)

And in this slack thread: p1663378153241789-slack-C03TY6J1A

@KirkwallDay KirkwallDay added the [Type] Feature Request Feature requests label Sep 21, 2022
@github-actions
Copy link

github-actions bot commented Sep 21, 2022

Support References

This comment is automatically generated. Please do not edit it.

  • 5563725-zen
  • 5575173-zen
  • 5648190-zen
  • 5846271-zen
  • 5920484-zen
  • 6428692-zen
  • 6538200-zen
  • 6569256-zen
  • 6527845-zen
  • 6648395-zen
  • 6710916-zen
  • 6782614-zen
  • 7203893-zen
  • 7429662-zen
  • 7462298-zen
  • 7704805-zen
  • 7885655-zen
  • 9247734-zen

@Greatdane Greatdane added the [Type] Bug When a feature is broken and / or not performing as intended label Sep 22, 2022
@Greatdane
Copy link

📌 FINDINGS/SCREENSHOTS/VIDEO

  • Almost tempted to label this as a bug, as I am not sure this is intended behavior. I will let Quality Squad determine the best way forward on that!

📌 ACTIONS

  • Marked as Triaged for Quality Squad review
  • Feature request kept

@Greatdane Greatdane added the Triaged To be used when issues have been triaged. label Sep 22, 2022
@youbrokesomething
Copy link
Contributor

From the linked ticket, it looks like this is the currently expected behavior. More than 50 pages will result in a Chronological view. So, I'm going to keep this as a feature request and move it to that queue.

@hacchism
Copy link

another report in 5648190-zen, suggested using classic view as a workaround

@rw-ye
Copy link

rw-ye commented Jan 8, 2023

5846271-zd-woothemes

Suggested classic view workaround.

@marianearchimbaud
Copy link

5920484-zd another user has reported the same issue

@cuemarie cuemarie added the [Pri] Normal Schedule for the next available opportuinity. label Apr 13, 2023
@sudeepbaral
Copy link

Another report here:

  • 6428692-zen

Suggested using Classic View as a workaround

@ccwalburn
Copy link

ccwalburn commented Jul 17, 2023

Another report here:

@kelasante
Copy link
Collaborator

Another report here:

6569256-zen

@tellisbethel
Copy link

Another report here: 6527845-zd-a8c
Suggested Classic Editor workaround

@CodeAllNightNDay
Copy link

Report here: 6648395-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Aug 11, 2023
@wpshellbelle
Copy link

Another report here: 6710916-zen

@github-actions github-actions bot added the [Interaction #] > 10 (Automated) interaction count label for better visibility. Please don't add these manualliy. label Sep 6, 2023
@DustinHartzler
Copy link
Contributor

Another report in 6782614-zen

@inaikem
Copy link
Contributor

inaikem commented Oct 24, 2023

@wojtekn 👋 We had a similar issue (presentation-wise) here: #60280

Is the above related in some way?

@wojtekn
Copy link
Contributor

wojtekn commented Oct 24, 2023

@inaikem yes, those two tickets are related. To give some summary - before #60280 the behavior was confusing to users:

  • on the initial load, the page showed less than 20 posts in “chronological” mode
  • after scrolling to the bottom, infinite load caused loading more posts, and when they exceeded 20, the view switched to "hierarchical" mode

The most comprehensive fix would require changing the feature architecture completely, as we would need to move hierarchy/indent calculation from Node code to the API endpoint. After a long discussion, we decided to solve the user experience gap in the following way:

  • the user who has less than 50 pages will always see a hierarchical view
  • the user who has more than 50 pages will always see a chronological view

@gabriel-fuentes
Copy link
Collaborator

7203893-zen

@caitlindawn
Copy link

7429662-zen

@OmarFPG
Copy link

OmarFPG commented Dec 18, 2023

7429662-zen asking for an update again.

@philnick206
Copy link

7462298-zd-a8c requesting an update again.

@wojtekn
Copy link
Contributor

wojtekn commented Dec 19, 2023

@OmarFPG @philnick206 there is no immediate plan to change this behavior and the current state looks as follows:

After a long discussion, we decided to solve the user experience gap in the following way:

  • the user who has less than 50 pages will always see a hierarchical view
  • the user who has more than 50 pages will always see a chronological view

@OmarFPG
Copy link

OmarFPG commented Feb 8, 2024

7704805-zen

@Greatdane
Copy link

7885655-zd-a8c

The user is confused as to why the page layout would change after 50 pages.

Can we rethink this setup? It seems strange to change the layout after a certain number of pages.

@ezebecke
Copy link

ezebecke commented Jan 6, 2025

Also on 9247734-zd-a8c

This change of order is very confusing for users and for HEs trying to troubleshoot and understand what happened.

@inaikem
Copy link
Contributor

inaikem commented Jan 12, 2025

@Copons, I know this issue doesn't quite fall into your group's area but I'd love some help increasing visibility to get it resolved.

The current logic of breaking the page load order when the page count exceeds 50 makes little logical sense to me.

@wojtekn
Copy link
Contributor

wojtekn commented Jan 14, 2025

@inaikem is it still an issue after untangling #95621 ?

@Copons
Copy link
Contributor

Copons commented Jan 14, 2025

As suggested by @wojtekn, the Pages screen is being untangled (this issue specifically #95620), so this issue is about to become irrelevant soon.

Starting this week, 90% of users will only get the wp-admin Pages screen (among other screens). This issue will remain for the other 10% until the end of the experiment (no ETA), but arguably the priority and usefulness of fixing it will be almost insignificant.

@inaikem
Copy link
Contributor

inaikem commented Jan 15, 2025

@wojtekn, @Copons, thank you! I'll close this issue for now and loop back in a couple of weeks to review the status of the experiment 🙏

@inaikem inaikem closed this as completed Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Interaction #] > 10 (Automated) interaction count label for better visibility. Please don't add these manualliy. [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended [Type] Feature Request Feature requests
Projects
None yet
Development

No branches or pull requests