mdelapenya/liferay-portal — pull request #13 by KocsisDaniel (2012-10-19 09:20:00+00:00)
Title: LPS-30418

Hey Manu, I would like to send my solution for a pre-review, because I am curious about your opinion. As I found the problem is not strickly related to staging but more of a DDM Structure related problem. You can reproduce the same stacktrace via create a DDM Structure (ddl portlet for example) but change its default language other the portal default and save it. The problem is with DDM the title/description map is not changing together with the structure when you change the language and it is easily piossible to create a state when the structure local is different from the name locale and the name doesn't have any translation on that locale. Because of that the validatelanguages in the DDMSLSI throws an exception when tries to get the name from the nameMap with contentDefaultLocale key. I am not sure if we did it on purpose and we have to prepare the structure/notify the customer to add translation before we save, or we can change this validation. I chose the 2nd option in my fix, and I would like to ask you opinion about that, because as I can see you introduced this method and the whole language validation over staging. Thanks, Daniel