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

"Request a new translation" button on support pages is too large #97652

Closed
mikeicode opened this issue Dec 19, 2024 · 3 comments
Closed

"Request a new translation" button on support pages is too large #97652

mikeicode opened this issue Dec 19, 2024 · 3 comments
Labels
[Feature Group] Support All things related to WordPress.com customer support. [Feature] Support Docs Site & Infrastructure The site, theming, and infrastructure that hosts all WordPress.com's official support documentation. [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@mikeicode
Copy link

Quick summary

There is a "Request a new translation" button on the support pages. The button should like this:

Image

But on some pages it looks like this:

Image

I believe it's caused when a button block is added to the page content.

Image

Image

This makes this button look like the most important CTA on the page, which is an issue for obvious reasons, especially on pages where we are trying to sell items using other CTAs.

Steps to reproduce

  1. Visit this page
  2. Compare with this page

What you expected to happen

Image

What actually happened

Image

Impact

Some (< 50%)

Available workarounds?

There is no user impact

If the above answer is "Yes...", outline the workaround.

There might not be a technical user impact, but this could affect sales and is a bad user experience.

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

@mikeicode mikeicode added [Feature Group] Support All things related to WordPress.com customer support. [Feature] Support Docs Site & Infrastructure The site, theming, and infrastructure that hosts all WordPress.com's official support documentation. [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Dec 19, 2024
@github-actions github-actions bot added the [Pri] Low Address when resources are available. label Dec 19, 2024
@Robertght Robertght added [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. and removed [Pri] Low Address when resources are available. Needs triage Ticket needs to be triaged labels Dec 20, 2024
@Robertght
Copy link

I'm able to see it too. I'm changing priority to Normal for now.

@Robertght Robertght moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Dec 20, 2024
@Robertght
Copy link

Sharing the extra context I got from @happychait (thanks again)

This will be something only us(logged in superadmins) will see so for now we'll keep it a low priority.

This is what I see when I'm not logged in or logged in as a test user:

Image

@Robertght Robertght added [Pri] Low Address when resources are available. and removed [Pri] Normal Schedule for the next available opportuinity. labels Dec 20, 2024
@donalirl
Copy link

Fixed in #98468

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature Group] Support All things related to WordPress.com customer support. [Feature] Support Docs Site & Infrastructure The site, theming, and infrastructure that hosts all WordPress.com's official support documentation. [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

No branches or pull requests

3 participants