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

FSE Plugin: Broken Homepage Layouts in Mag 16. #42368

Open
5 tasks
iamtakashi opened this issue May 19, 2020 · 1 comment
Open
5 tasks

FSE Plugin: Broken Homepage Layouts in Mag 16. #42368

iamtakashi opened this issue May 19, 2020 · 1 comment

Comments

@iamtakashi
Copy link
Contributor

This is something I've noticed while I was working on #41364, also @AtrumGeost has reported in #37782.

I've tested all the homepage layouts in the mag16, and I thought about what we need to do to fix them so that they will be available in a good shape for all the mag16.

  • Locate the translations (or make them if it's never translated) for Balasana, Maywood, Shawburn, Twenty Twenty homepages. Test, fix, and deploy the translations so that we stop the confusing experience with the fallback.

Screenshot 2020-05-19 at 16 39 43

  • Fix the translation for Subscription block on the default layout in fr, es, and tr

Screenshot 2020-05-19 at 16 21 43

  • Fix the translation for Block and Subscription blocks on Levan's homepage layout in all of the mag 16

Screenshot 2020-05-19 at 16 24 31

Screenshot 2020-05-19 at 16 24 41

  • Fix the dropdown form on Rockfield homepage in all of the mag 16 (Not sure why it's broken yet.)

Screenshot 2020-05-19 at 16 27 33

  • Fix the Contact Info block on Startford homepage in all of the mag 16

Screenshot 2020-05-19 at 16 32 18

cc @ianstewart @alaczek @akirk @obenland

@github-actions
Copy link

github-actions bot commented Aug 8, 2021

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants