�� Automatic code style fixes

combobox representation for dropdowns and lookups

apply #670 and manually cleanup afterwards

fixes some failing tests
uses sexplode over array_pad
reformats multiline arrays

�� Automatic code style fixes

PHP code sniffer autofixes

Automatic coding style fixes

Refactor to use buildAttributes -> cleaner code

Fix multiple inputs in one label: it's invalid ��

Multiple inputs within a single label in invalid HTML. This bug can not
only occur in multi-fields but also in plugin-provided single fields
which m

Fix multiple inputs in one label: it's invalid ��

Multiple inputs within a single label in invalid HTML. This bug can not
only occur in multi-fields but also in plugin-provided single fields
which may contain multiple input-fields which are then only combined by
javascript.

Thus, we provide an id which every type can assign to the edit-field
best suited. For multi-types this is usually the new-input-template.

Fixes #292

show more ...

another fix for multi value dropdowns

This had been only partly fixed in a3f28bd5749019a23c6a298391781f8480629536

use correct value for multi lookups. fixes #208

The problem was in how values were saved, so you need to resave your
data after this fix is applied.

Lookup Dropdowns are now handled separately

Dropdowns are now back to being simple value pickers. To select data
from a different Schema the Lookup type was introduced. This makes the
code a bit sim

Lookup Dropdowns are now handled separately

Dropdowns are now back to being simple value pickers. To select data
from a different Schema the Lookup type was introduced. This makes the
code a bit simpler.

Users who used the Dropdown type to reference schemas will need to
reconfigure their schema to make use of the Lookup type instead.

The Lookup type now handles self references (fixes #171) and references
to page schemas correctly.

show more ...

renamed JSON to STRUCT_JSON. fixes #157

Always use raw values for editors

This is another attempt to fix #140. The valueEditor() and
multiValueEditor() now always expect raw values to be passed. The Value
class was adjusted accordingly. I

Always use raw values for editors

This is another attempt to fix #140. The valueEditor() and
multiValueEditor() now always expect raw values to be passed. The Value
class was adjusted accordingly. It now allows to set the raw value
(which is what we get from POST). If done, the Value object is treated
as a rawonly Value that will throw an exception when you try to access
value or displayvalue.

show more ...

implement rendering via sub type in Dropdown

fix displayValue for looked up type, more tests

fixed constructor signature

Add Lookup Support to Dropdown

Instead of specifying values directly, one can now specify a lookup
schema where the data is read from. The specified field name may contain
a $LANG place holder to be

Add Lookup Support to Dropdown

Instead of specifying values directly, one can now specify a lookup
schema where the data is read from. The specified field name may contain
a $LANG place holder to be replaced with the current language string.

There is currently no enforcement that the specified schema is indeed a
lookup schema. It should work with a non-lookup as well.

show more ...

Clean values in multiValueEditor, not in valueEditor

Since rawValue expects a single value it may not be able to handle
multiple concatinated values.

This caused an error for the pagetype in a mult

Clean values in multiValueEditor, not in valueEditor

Since rawValue expects a single value it may not be able to handle
multiple concatinated values.

This caused an error for the pagetype in a multi value field with
usetitles enabled.

show more ...

Use DokuWiki new autoloader for class files

No longer do we need to register our own autoloader. Namespace had to be
vendor prefixed.

added empty option to dropdown to be able to deselect

implement dropdown type #36