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

Full site editing: Unable to view a page template if the page is marked as a blog archive #62288

Closed
arunsathiya opened this issue Mar 27, 2022 · 8 comments
Assignees
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Empathy Testing This tag is applied to bugs found when testing user flows. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Post/Page Editor The editor for editing posts and pages. [Goal] Full Site Editing Groundskeeping Issues handled through Dotcom Groundskeeping rotations Posts [Pri] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@arunsathiya
Copy link
Contributor

arunsathiya commented Mar 27, 2022

Quick summary

When a page is marked as blog archive, there's no way to open that page's editor view to view the applied template. It's possible only after un-setting the page as blog archive on the Customizer.

Steps to reproduce

What you expected to happen

There's an option to open the editor view of a page once it's marked as a blog archive.

What actually happened

  • The only option on the pages list is to view the blog archive on the live site. There's no editor view.
  • This makes it impossible to identify what template is applied to the blog archive page. It's necessary to un-set the page from being the blog archive first, in order to open the editor view.

Context

Customer report on 4885219-zen.

Simple, Atomic or both?

Simple, Atomic

Theme-specific issue?

No, I believe it applies to all but I have tested only with core theme Twenty Twenty-Two.

Browser, operating system and other notes

Not applicable.

Reproducibility

Consistent

Severity

All

Available workarounds?

No and the platform is unusable

Workaround details

No response

@arunsathiya arunsathiya added [Type] Bug When a feature is broken and / or not performing as intended [Goal] Full Site Editing User Report Empathy Testing This tag is applied to bugs found when testing user flows. labels Mar 27, 2022
@arunsathiya
Copy link
Contributor Author

@arunsathiya
Copy link
Contributor Author

Interestingly, this does not happen on WordPress.org: I can access the editor view of a blog archive page fine.

image

It's only on WordPress.com where I cannot open the editor view:

image

image

@vajrasar vajrasar added Posts [Pri] High Address as soon as possible after BLOCKER issues labels Apr 14, 2022
@vajrasar
Copy link

vajrasar commented Apr 14, 2022

Hi @arunsathiya 👋 Thanks for the detailed report.

I checked and I can confirm the issue on .com (Simple + AT sites) where you do not get the option to edit the "Blog" page (set as the Posts Page) on the Page Editor, and also you do not have any way to edit the Blog page template via Site Editor.

While on non .com sites you get the option to edit the "Blog" page, the changes you make are not visible. Hence, it does not make any difference if the editing is available. But, same like .com you do not have any way to make changes to the Blog page template using Site Editor even on non .com site.

Both of the above cases are true when the "Blog" page is set as the Posts Page of the site.

The workaround is to unset the "Blog" page from the Posts Page, select Static Posts page, move to Site Edito, make changes on the Home template, and then go ahead and set "Blog" page as the Posts page again. The changes you made o the Home template will reflect on the Blog page now.

@vajrasar
Copy link

cc: @Automattic/cylon

@creativecoder
Copy link
Contributor

This one is very hard to fix... even if we added links to "Edit" the Home and/or Posts page from the page list, typically you would see empty post_content in the editor, because the content for those pages primarily comes from templates. Opening an empty homepage in the editor is quite confusing!

Ultimately, we're dependent on Gutenberg/Core to improve the in editor content preview for these special pages. For now I think the best workaround is to select and edit the template from the site editor:

image

@cuemarie cuemarie added [Feature] Post/Page Editor The editor for editing posts and pages. [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. labels Oct 5, 2023
@github-actions github-actions bot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label Oct 5, 2023
@cuemarie
Copy link

cuemarie commented Oct 5, 2023

📌 ACTIONS

  • Due to the age of this issue, I've downgraded the priority from High to Normal to better reflect its status in the larger context of open bugs in this repo.
  • I also quickly retested on a new free site (Themes Fewer and TT3), and I'm not sure this issue is still occurring:
fYflGN.mp4

@creativecoder do you agree?

@cuemarie cuemarie added [Pri] Normal Schedule for the next available opportuinity. and removed [Pri] High Address as soon as possible after BLOCKER issues [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts labels Oct 5, 2023
@cuemarie cuemarie moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Oct 5, 2023
@github-actions
Copy link

github-actions bot commented Oct 5, 2023

Support References

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

  • 4885219-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Oct 5, 2023
@cuemarie cuemarie added [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. and removed Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". labels Oct 5, 2023
@cuemarie cuemarie added the Triaged To be used when issues have been triaged. label Oct 5, 2023
@mrfoxtalbot mrfoxtalbot moved this to To triage in Dotcom Core Fix Needed Sep 2, 2024
@gikaragia gikaragia self-assigned this Sep 5, 2024
@gikaragia
Copy link
Contributor

Did some testing and investigation around this and it seems that this is expected behavior.

The posts page is supposed to be defined by the theme itself so users do not make sense to edit this page. If we allow editing in such a page, there is a warning that says 'You are currently editing the page that shows your latest posts.' on top and any changes will not appear anywhere. There is more information about this here and this is the issue that removed these links in the first place.

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Sep 6, 2024
@gikaragia gikaragia added the Groundskeeping Issues handled through Dotcom Groundskeeping rotations label Sep 6, 2024
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". Empathy Testing This tag is applied to bugs found when testing user flows. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Post/Page Editor The editor for editing posts and pages. [Goal] Full Site Editing Groundskeeping Issues handled through Dotcom Groundskeeping rotations Posts [Pri] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Development

No branches or pull requests

5 participants