Cloud: display count when summarize is configured

Implements #613

�� Automatic code style fixes

only have unique result rows when nesting

This fixes row duplication on nesting with multiple multival fields

Add nesting option for List Aggregations

This allows to create nested lists based on the selected number of
result columns. This is basically a group-by after the fact and
displaying it in a tree. M

Add nesting option for List Aggregations

This allows to create nested lists based on the selected number of
result columns. This is basically a group-by after the fact and
displaying it in a tree. Multivalues are split up for grouping, so that
a result can be nested by tags for example.

show more ...

more test and deprecation fixes

PHP code sniffer autofixes

Automatic coding style fixes

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

fix: fix broken cloud tags of multi-lookup columns

Since we group in the SQL query by tag, cloud tags are always single values.
However if the column we are creating the cloud from, is actually a
mu

fix: fix broken cloud tags of multi-lookup columns

Since we group in the SQL query by tag, cloud tags are always single values.
However if the column we are creating the cloud from, is actually a
multi-column then that single value is still in an array. But since that
array can never contain more than 1 value we can simply take the first
one.

The alternative of changing the type was considered but found not to be
practical, because changing the type of a value/column is not intended.
Recreating a new column and type for that value has been found to be
impractical as well.

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

fix: keep leading whitespace in value of wiki-type

Fixes #223 and fixes SPR-712

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

introduces getDisplayValue

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

begin stremalining raw handling #148

This starts implementing the wanted features in the Value and
AccessTable class. Calling classes and tests aren't adjusted, yet

Use DokuWiki new autoloader for class files

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

make Value more robust and test it #35

do not render empty values. closes #44

added validation support #11

make use of the new Value objects in the entry form

introduced Value class

This class holds the value of a single cell and a reference to the
column.