You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have a collection with different locales. English, arabic .etc. When doing export arabic locale is not present. Event if it was previously selected in the menu and export button was clicked next the the locale selected. Only EN is exported, which is a bummer.
I have 25 locales configures. Only EN is exported both when using Export Whole Database or Exporting specific collection:
UPDATE: when "Export plugins content types" is selected when exporting whole database, the locales ARE exported (settings only, not data for other languages),
The text was updated successfully, but these errors were encountered:
piotrwalczak1
changed the title
[BUG] Internalization is not supported. Only EN locale is exported, even when other is selected -> export
[BUG] Internalization is not supported. Only EN locale data is exported
Feb 15, 2024
Looks like it exports only default language data (not particulary EN). It may work for you if you change default lanugage 1 by 1 and export/import like this but it may be annoying to do for 25 languages like in your case
@piotrwalczak1 export function will export the default language locale only. if you are default language locale is EN then it will export only EN content.
Describe the bug
I have a collection with different locales. English, arabic .etc. When doing export arabic locale is not present. Event if it was previously selected in the menu and export button was clicked next the the locale selected. Only EN is exported, which is a bummer.
I have 25 locales configures. Only EN is exported both when using Export Whole Database or Exporting specific collection:
UPDATE: when "Export plugins content types" is selected when exporting whole database, the locales ARE exported (settings only, not data for other languages),
The text was updated successfully, but these errors were encountered: