Skip to content

fix(app-website-builder): show Translate page action without AI Powerups - #6122

Closed
adrians5j wants to merge 1 commit into
nextfrom
adrian/wb-translate-without-ai
Closed

adrians5j wants to merge 1 commit into
nextfrom
adrian/wb-translate-without-ai

Conversation

@adrians5j

Copy link
Copy Markdown
Member

What was wrong

Since 6.5.0 the Translate action in the Website Builder page list options menu was only rendered when the license granted aiPowerups.websiteBuilder.pageTranslation. Projects without AI Powerups lost the action entirely, including the manual flow: copy the page into another language and translate the content by hand. Up to 6.4.0 the action was always shown to users who can create pages.

The gate was added in #5536 (wcp.canUseAiPageTranslation()) and carried over to the feature flag in #5559.

Why the gate is not needed

  • WbMutation.translatePage (TranslatePageUseCase in api-website-builder) checks the page create permission and nothing else. It duplicates the page with the target language, path and sourcePage set.
  • WbTranslatePageDecorator in ai-powerups runs on top of that. When the AI capability is switched off or unavailable it logs and returns the plain copy.

So with AI Powerups the page is copied and translated; without it, the page is copied and left for manual translation. Both should have the menu item.

Change

TranslatePageConfig no longer checks the feature flag. The HasPermission entity="page" action="create" wrapper stays.

Testing

  • yarn lint and a type check of app-website-builder pass.
  • Not checked in a browser and no demo video: the admin app could not be started in the checkout this was written in. To verify: with a license that has no AI page translation, open Website Builder > Pages, open a page's options menu, confirm Translate is there, and translate a page into another language. The copy should appear in the chosen folder with the language set.

Workspace: wby-next3 · page translate menu missing

🤖 Generated with Claude Code

Since 6.5.0 the Translate action in the page list was hidden unless the
license granted aiPowerups.websiteBuilder.pageTranslation. Manual
translation does not need that license: the translatePage mutation copies
the page into the target language with no license check, and the AI
decorator falls back to that plain copy when AI translation is off.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🚓 Slop Cop

✅ Nothing worth flagging. The diff looks consistent with the PR's stated intent and the code-style rules.

Small, focused diff that matches the stated intent (removes a feature-flag gate) with no style or integrity issues.

Automated, non-blocking heads-up from an LLM. It can be wrong — use your judgment. Regenerates on every push.

@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Caution

Review failed

The pull request is closed.

Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@adrians5j

Copy link
Copy Markdown
Member Author

Replaced by 6123 against release/6.5.1.

@adrians5j adrians5j closed this Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant