Web Content Articles are localizable, but Web Content folders are fixed

• Type: Bug
• Status: Closed
• Resolution: Won't Fix
• Affects Version/s: 7.0.X, 7.1.X, Master
• Fix Version/s: None
• Component/s: ~[Archived] WCM
• Labels:
  • STAB_TST_JA
  • STAB_TST_JA_MUST
• Fix Priority: 4

Summary
Web Content Articles are localizable to whatever the instance is configured to, but Web Content folders are in a fixed state without any options to localize. Because the parent container cannot be localized, it seems like there is an inconsistency.

Steps to Reproduce

1. Create a Web Content article
2. Assert that there are localizable fields throughout the content creation process
3. Create a Web Content folder

Actual Results
There is only one field without any localization for Web Content Folders.

Expected Behavior
The parent container (i.e. the web content folder) should be localizable to allow for a more seamless localized experience.