- Can I use this bundle in a vanilla Laravel project without OroCommerce?
- No, this bundle is explicitly designed for OroCommerce and relies on its translation system (`oro:translation:update`). Vanilla Laravel projects using Symfony’s standard translator component will not work without significant modifications.
- What OroCommerce versions does this bundle support?
- The bundle is tested for OroCommerce versions 4.2 through 7.0. If your project uses a version outside this range, compatibility is not guaranteed, and you may encounter integration issues or missing features.
- How do I add translations for languages other than Italian or English?
- The bundle primarily supports Italian (it_IT) with English fallback. To add other languages, manually extend the YAML translation files in `Resources/translations/` following OroCommerce’s naming conventions. Contributions for additional languages are welcome via pull requests.
- Why does the package require a private repository setup, and how do I configure it?
- The bundle isn’t hosted on Packagist, so you must add it via a private repository (e.g., GitHub Packages or a custom Composer repo). Update your `composer.json` with the VCS URL and ensure your team has access credentials. Example: Add the `repositories` section as shown in the README.
- What post-installation steps are required after adding this bundle?
- After installation, run `php bin/console cache:clear` and `php bin/console oro:translation:update --force` to load translations. Automate these commands in your CI/CD pipeline to avoid deployment blockers, especially in production environments.
- Does this bundle include unit or integration tests?
- The current documentation and repository do not mention included tests. You’ll need to manually validate translations by testing the Oro admin panel and frontend for edge cases like missing keys or fallback behavior. Consider writing custom tests for critical translations.
- Will this bundle impact performance in large-scale OroCommerce stores?
- The bundle uses YAML-based translations, which OroCommerce typically handles efficiently. However, if your store processes thousands of translations dynamically, consider caching strategies or optimizing translation file structure to minimize load times.
- How can I extend the bundle to add custom translation domains or dynamic keys?
- To extend the bundle, create new YAML files in `Resources/translations/` for custom domains (e.g., `messages.it_IT.yml`). For dynamic keys, wrap the translation logic in a service class that interacts with the Oro translation system via `oro:translation:update`.
- What happens if I skip the `oro:translation:update` command after installation?
- Skipping the update command will prevent new translations from loading. Your application may display default or missing translations, leading to broken UI labels, validation messages, or entity names. Always run the command post-installation or in CI/CD.
- Are there alternatives to this bundle for OroCommerce localization?
- OroCommerce already includes built-in translation tools via `oro:translation:update`. If you need lightweight customizations, consider extending Oro’s default translation system instead. For advanced use cases, check community bundles like `oro/translation-bundle` or consult Algoritma’s support for tailored solutions.