Translation Manager
Find missing translations and edit languages side by side.
- Version
- 1.1.0-beta.49
- Released
- 20 October 2026
- Licence
- Free
Price Free
Check access and installationCheck compatibility before using this Beta extension
Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.
On this page
-
Price and access
Review the price, licence and availability before deciding what to adopt.
-
Your workflow
Read how the package is used and what your application needs to provide.
-
Product captures
Review the available captures and see which part of the workflow each screen demonstrates.
-
Capabilities
See which jobs this extension supports and which parts it adds to your site.
-
Project fit
Decide what this removes from your workload and what your application still needs to supply.
-
Installation
Check the setup steps before adding the package to a project.
-
Release evidence
Review the available release, maintenance and package-review information.
Check your application before checkout
Use it in your project
Compare locale coverage in one admin page, then update the language files or package overrides that need attention.
Picture it on your site
For a multilingual release, compare the relevant locale coverage and identify missing or outdated strings before updating files or overrides. Review the affected screen in each intended language afterwards. The workspace makes gaps easier to find; it does not translate content automatically or replace review by someone who understands the audience.
Keep publishing work moving
- Find missing and stale translation entries.
- Create, import, export and save locale files.
Is this right for your project?
A publishing process people can follow
Start with the journey from a draft to a published page, not a list of status names. Who writes it, who checks it and who is responsible for the publication date? Choose the controls that match that journey. The benefit is a repeatable editorial process with fewer changes made outside the CMS; your team still supplies the content standards and the people who make publishing decisions.
Prove one complete release
Use a representative article or page to check editing, review, publication and the public result together. Include the site, language and related content that matter to your project. A scheduled record or approved status is only part of the result: visitors must see the right content at the right URL, and editors need to know how to correct it afterwards.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/translation-manager -
02
Install the extension
php artisan capell:extension-install capell-app/translation-manager
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.0-beta.49 Oct 20, 2026
- Recent activity
- 19 approved releases in the last 12 months
Review evidence for this release
File-based translation editing with locale comparison, CSV, PO and XLIFF import-export, and optional AI-drafted suggestions. Review found the admin page is access-gated, locale and file-key inputs are validated against traversal before any filesystem write, and XLIFF import explicitly rejects DOCTYPE declarations to prevent XXE. No unresolved defects were found in the reviewed source.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0-beta.49
- Approval date
- Oct 19, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Draft translation suggestions depend on the optional orchestration extension and an externally configured provider; suggestions are not automatically published. Cross-package integration was not exercised by this per-package review; the local suites used SQLite, and live browser flows and server-database behaviour were not exercised.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releases-
v1.1.0-beta.49Oct 20, 2026 -
v1.1.0-beta.48Oct 17, 2026 -
v1.1.0-beta.47Oct 9, 2026 -
v1.1.0-beta.46Oct 9, 2026 -
v1.1.0-beta.45Oct 8, 2026 -
v1.1.0-beta.44Oct 8, 2026 -
v1.1.0-beta.43Oct 7, 2026 -
v1.1.0-beta.42Oct 4, 2026 -
v1.1.0-beta.41Oct 1, 2026 -
v1.1.0-beta.40Sep 29, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.