[Task] tools: promote Beta portlet to primary
@hmoreras is already working on this.
Since Sep 2, 2026.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Promote the Tools portlet from Beta to primary once it has baked in production: drop the -beta suffix from the portlet id, the display name and the route, and add it to the default layout so it appears out of the box.
This is a separate ticket on purpose. While it ships as tools-beta, the portlet reaches only the admins who opted in through Add Portlet, and backing it out is a layout edit. Promotion is the point at which every install gets it, so it happens after product sign-off rather than inside the implementation PR.
Acceptance Criteria
-
dotCMS/src/main/webapp/WEB-INF/portlet.xml— rename thetools-betaentry totools, with<portlet-url>/tools</portlet-url>and display nameTools. -
dotCMS/src/main/webapp/WEB-INF/messages/Language.properties— dropcom.dotcms.repackage.javax.portlet.title.tools-betaand addcom.dotcms.repackage.javax.portlet.title.tools=Tools. -
core-web/apps/dotcms-ui/src/app/app.routes.ts— flip the route path fromtools-betatotools. -
dotCMS/src/test/java/com/dotmarketing/business/portal/SerializationHelperTest.java— update thetools-betaassertion intestFromXmlFileto pintools. - Any other test asserting portlet ids or portlet counts is updated.
-
UpgradeTask— an existing install whose custom layout referencedtools-betastill renders a working portlet after the upgrade. - The Tools portlet is added to the default layout so a fresh install shows it out of the box, under Settings.
- i18n keys in the portlet that carry
betain their value or their name are cleaned up. - Product sign-off is recorded on this ticket before the swap PR merges.
Priority
Low — blocked on the Beta baking in production and on product sign-off.
Additional Context
The Roles & Tools portlet keeps its Tools tab, which owns granting a section to a role. Nothing about it changes here.
QA
- Fresh install — the default layout shows Tools under Settings; the portlet loads at
/#/c/toolsand every surface works. - Upgraded install, Beta in a custom layout — an install that had
tools-betain a custom layout still renders a working Tools portlet after the upgrade, with no broken menu entry. - Upgraded install, Beta never added — the navigation is unchanged except for the new Tools entry, and no existing section or tool moved.
-
Tools (Beta)no longer appears anywhere in Add Portlet or in the navigation. - Granting and revoking sections per role in Roles & Tools still behaves exactly as before.
Refs #37351
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.