�� Automatic code style fixes

Fix tag cloud link

Fixes #692

Cloud: display count when summarize is configured

Implements #613

Add COLLATE NOCASE to sort queries

Fixes #616

apply #670 and manually cleanup afterwards

fixes some failing tests
uses sexplode over array_pad
reformats multiline arrays

�� Automatic code style fixes

Manual code style adjustments

PHP code sniffer autofixes

Automatic coding style fixes

Fix PHP notices

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 ...

Add compareValue() abstract base type & lookup

This fixes a bug, that caused the $STRUCT.table.field$ filter syntax to
be broken for lookup fields. Struct was comparing the row-id of the
argument-c

Add compareValue() abstract base type & lookup

This fixes a bug, that caused the $STRUCT.table.field$ filter syntax to
be broken for lookup fields. Struct was comparing the row-id of the
argument-column to the raw value of the referenced column at the
filtered lookup.

There were multiple options to fix this bug:
1. Add a new function to the AbstractBaseType() that return raw value by
default (this is the approach implemented by this commit)
2. Add a function to the lookup type only and use introspection to call
it if it exists.
3. Do not compare the values in the referenced columns, but compare only
the row-ids

The problem with approach 3: It is not possible to compare such
lookup-column to any other column except lookups and this is not what we
want.
Approaches 1 and 2 have different trade-offs on where additional
code/complexity is created. I decided for approach 1 because it is the
cleaner overall approach and we might want to use this functionality for future
types as well.

SPR-875

show more ...

refactor: use trait to reduce duplicate code

uses exact matches for Decimals

A LIKE operation makes no sense for numbers. This makes it possible for
the type to define how a dynamic filter is to be interpreted. Decimals
to an exact comparison

uses exact matches for Decimals

A LIKE operation makes no sense for numbers. This makes it possible for
the type to define how a dynamic filter is to be interpreted. Decimals
to an exact comparison now.

show more ...

fix: stop OR filters causing problems

The filters coming from syntax should be grouped together in a subgroup
to that OR-filters cannot undo the filters on latest=1 etc.

Since we cannot know in the

fix: stop OR filters causing problems

The filters coming from syntax should be grouped together in a subgroup
to that OR-filters cannot undo the filters on latest=1 etc.

Since we cannot know in the filter function whether there is already a
subgroup for us to use or which to use, the solution was to give the
correct subgroup to the filter function directly.

Instead of adding another parameter to the already long list of
parameters for that function, I have chosen to give the
QueryBuilderWhere a reference back to the original QueryBuilder.

show more ...

doc: update php docstrings

feat: make images in clouds square

Also move the code to generate tag cloud links to the AbstractBaseType
and overwrite it in Media and Color

refactor: make sortString available for all types

Merge pull request #166 from cosmocode/bug140

Always use raw values for editors

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 ...

Merge branch 'lookups' into validationrefactor

* lookups:
test translation feature
implement rendering via sub type in Dropdown
fix displayValue for looked up type, more tests
fixed construc

Merge branch 'lookups' into validationrefactor

* lookups:
test translation feature
implement rendering via sub type in Dropdown
fix displayValue for looked up type, more tests
fixed constructor signature
first test for new Dropdown features
adjusted tests for renamed aliases
Add Lookup Support to Dropdown
column aliases need to differ from real column names
use display value as default renderer
introduces getDisplayValue

show more ...

Validation should happen on raw value

This just renames the parameter to make this more clear

use display value as default renderer

introduces getDisplayValue

A way to represent a complex type as a single non-complex type. Usually
this is the same as the rawValue.