feat: Enable usage in sidebars etc.

By replacing $ID with $INFO['id'] the entries now work in sidebars and
especially in the new footers (see SPR-699) as expected.

Tested:
* Sorting
* Dynamic filte

feat: Enable usage in sidebars etc.

By replacing $ID with $INFO['id'] the entries now work in sidebars and
especially in the new footers (see SPR-699) as expected.

Tested:
* Sorting
* Dynamic filters
* $STRUCT.tablename.field$ placeholder
* $ID placeholders

SPR-348

show more ...

Fixed SearchConfig offset not being set bug

adjust for removed option in AccessTable

refactor SchemaData into AccessTable with factory

first part of the refactoring for the SchemaData and SchemaLookupData
classes. Both now inherit from AccessTable which provides common methods
and t

refactor SchemaData into AccessTable with factory

first part of the refactoring for the SchemaData and SchemaLookupData
classes. Both now inherit from AccessTable which provides common methods
and two factory methods to automatically create the correct class
depending on the schema.

Both classes no longer inherit from Schema. Instead they contain a
Schema as a member variable. This makes it possible to initialize them
with an existing schema (which is required for the factory methods).

The flow is now like this:

1: init a schema (read info from the database)
2: look at the schema to figure out if it's a lookup or not
3: initialize the right Data object with the schema

show more ...

MultiCol match: empty array means empty filter

a $STRUCT.*$ filter doesn't need reference the same schemas

A filter may reference all schemas of the page the aggregation is on
which are not necessarily the same schemas that are queried.

allow multicolumn filters #124

when referencing a multi value column through the $STRUCT.<column>$
filter placeholder, all found values are used for the comparison using
an OR sub group.

To make th

allow multicolumn filters #124

when referencing a multi value column through the $STRUCT.<column>$
filter placeholder, all found values are used for the comparison using
an OR sub group.

To make this work some changes had to be introduced. You can only
reference _one_ column in a filter, not multiple. Anything before or
after the column placeholder will be applied to each value in the
multicolumn.

Types overrifding the filter() method need to make sure they handle
arrays in $value correctly.

show more ...

Revert "Add $TITLE$ placeholder for aggregations and tests"

This reverts commit 7249dd99c6b513e7a0e270e0532734a1bf838ae4.

As discussed in #133 the $TITLE$ place holder is no longer needed since
tit

Revert "Add $TITLE$ placeholder for aggregations and tests"

This reverts commit 7249dd99c6b513e7a0e270e0532734a1bf838ae4.

As discussed in #133 the $TITLE$ place holder is no longer needed since
title columns match against the pid as well. Since gathering the title
data for the filter is actually performance relevant, it makes sense to
remove it again.

show more ...

use rawValue for old revisions and column filters #131 #129

run rawValue on found columns only

introduce Type::rawValue(). fixes #131

Add $TITLE$ placeholder for aggregations and tests

Use DokuWiki new autoloader for class files

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

adjust cachung if an aggregation depends on dynamic values #75

fixed struct filter vars and added tests #75

support for dynamic filter place holders #75

tests for struct stuff still missing
no cache handling, yet

avoid errors when no schema or column is given

streamline sort direction handling

we now use a boolean everywhere

correctly apply dynamic params to the search config

schemas and columns need to be known before init dyn params

major refactoring of the whole table aggregation

this is still completely untested

make dynamic parameters a bit better to handle

Now the aggregation class no longer needs to juggle around with ugly
strings but can simply call functions on the SearchConfigParameter class
to genera

make dynamic parameters a bit better to handle

Now the aggregation class no longer needs to juggle around with ugly
strings but can simply call functions on the SearchConfigParameter class
to generate new parameters.

show more ...

Let SearchConfig handle all configuration

SPR-309. SPR-317 GitHub Issue #22

Add the sort config to the search object

began work on the syntax component to aggregate data

This copies over a lot of configuration functionality from the data
plugin, but is still missing the functionality itself.