Unable to publish WebContent for localized Site
Written By
Pooja Bhambani
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- Steps to reproduce:
1. Setup the vanilla bundle and start the Liferay.
2. Go to system settings > WebContent > Administration > Changeable default language as true.
3. Set en_US, es_ES as instance languages and en_US as the default language of the instance.
4. Go to the Global site and create a new structure with a single English field named "Test".
5. Save the new structure.
6. Create a new site with es_ES as a single and default language.
7. Create new Web Content on this site using the global structure.
8. Click Save.
Observed Behavior: Request is failed and this message is appearing (The default language (en_US) does not match the portal's available languages(es_ES).
Expected Behavior: The Content must be published successfully, without any error.
Environment
- Liferay DXP 7.1
- Liferay DXP 7.2
- Liferay DXP 7.3
Resolution
- The observed behavior is a known issue.
- If the hotfix is required for this issue, please create a support ticket requesting a hotfix by attaching patch details.
-
Installing Fix Packs and Hotfixes on Liferay DXP will guide to install this hotfix in the respective environment.
Did this article resolve your issue ?