London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

[BUG] Translating a Required, Non-CultureSpecific string property that has a space becomes null

Vote:
 

Create a page type with a required, non-culturespecific string property. Create an instance of this page, put in a space for this field and then translate the page. The translated page now has NULL for this field and since it is non-culturespecific you cannot change it (only on the language where it was originally created).

This is a problem because we do not do null-checking on required fields. Perhaps we should?

I am guessing behind the scenes EPiServer is doing a Trim on the field, discovers the field is an empty string and does not set the value for the translation.

I can see two possible solutions:

  1. do not allow spaces/tabs/(whitespace?) for required properties (trim suer input before checking so check will fail)
  2. do not trim a property when translating a page

Not entirely sure what is going on so my solutions could be wrong :)

#63801
Nov 29, 2012 17:22
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.