FIX: make possible values work as intended

Newlines in possible values in custom fields are now replaced by pipe (|). This commit also fixes typo caused by copy-paste (resource was sent as type).

app/Http/Controllers/Admin/CreateNewCustomField.php

@@ -24,8 +24,7 @@ class CreateNewCustomField extends Controller
     {
         $customField = new CustomField();
 
-        // @todo add support for determination of resource for custom field (module, user, ...)
-        // @todo add possible values
+        // set mandatory fields
 
         $customField->name = $request->name;
         $customField->type_id = $request->type;
@@ -38,8 +37,9 @@ class CreateNewCustomField extends Controller
             $customField->description = $request->description;
         }
 
-        if ($request->possibleValues)
-            $customField->possible_values = $request->possibleValues;
+        if ($request->possibleValues) {
+            $customField->possible_values = trim(preg_replace('~[\r\n]+~', '|', $request->possibleValues));
+        }
 
         if ($request->defaultValue) {
             $customField->default_value = $request->defaultValue;

resources/views/admin/customFields/newForm.blade.php

@@ -46,7 +46,7 @@
             <label>
                 @lang('admin/customFields.resource')
 
-                <select name="type">
+                <select name="resource">
                     @foreach($resources as $resource => $translation)
                         <option value="{{$resource}}"@if(old('resource') == $resource) selected @endif>@lang($translation)</option>
                     @endforeach