allow preset filters and related schemas for cloud

This refactors the cloud aggregation to make use of the
SearchSQLBuilder, this in turn allows for reusing much but not all of
the default parameter

allow preset filters and related schemas for cloud

This refactors the cloud aggregation to make use of the
SearchSQLBuilder, this in turn allows for reusing much but not all of
the default parameter handling.

By allowing joins (on pid) and setting filters we can output clouds
based on the same data as a shown aggregation.

show more ...

translation update

Remove some unnecessary texts

New syntax component "filter"

lists: correctly handle nesting with empty values

empty values are shown as n/a when they are used in nesting, otherwise
not shown just as before

Add variable date filter based on strtotime

Rename internal schemas to "internal"

Config option noedit

Makes it possible to freeze a schema

Allow displaying publish status in aggregations of page data

PHP code sniffer autofixes

Value aggregation type (#386)

* Allow a single value to be used inline in the page

* Removed debug line

* Added short form of value syntax - {{$s.f}}

* Refactor inline parsing into a new cl

Value aggregation type (#386)

* Allow a single value to be used inline in the page

* Removed debug line

* Added short form of value syntax - {{$s.f}}

* Refactor inline parsing into a new class and add filtering for page ID

* Allow recovery if the user has used single quotes

* Fixed metadata rendering when using $INFO['id']

* Handle no result better

* Add configuration for whether to show a no records text

* Linter fixes

* Match array style with other entries

* Simplify tokenising with -> separator

* Replace use of GLOBALS array

* Revert to dots, remove block syntax

* Suggestion of future syntax

* Use space-separated parameters

* Explanatory comments

* Increase sort order

* Don't lint for errors required by DokuWiki

* Move syntax description to class documentation

* Draft InlineConfigParser test

* Docstring alignment

show more ...

Add config option to show data on the top of the page (#550)

* Add config option to show data on the top of the page

Currently the default behavior is to show the data below the first
heading if

Add config option to show data on the top of the page (#550)

* Add config option to show data on the top of the page

Currently the default behavior is to show the data below the first
heading if it is found, or else on the top of the page.
In addition to the existing option to always show the data on the
bottom, let's also add an option to show it always on the top.

As we want to stay compatible with existing setups that use the
'bottomoutput' option we add another boolean 'topoutput'. The former
takes precedence over the latter and only if both are unset, the
default behavior of showing the data below the first heading is used.

Signed-off-by: Frieder Schrempf <dev@fris.de>

* fixup! Add config option to show data on the top of the page

show more ...

Add config option to disable deleting serial data in aggregations

Use "global" option in CSV export instead of defunct "lookup"

Option to display page data at the bottom

Resolves issue #371

Prepare to use unified schema in admin CSV export/import

Remove islookup property of schemas

CSV import must still be adjusted

Start unifying schema types

Schemas per se are type agnostic, isLookup property is removed. Data is stored and accessed differently based on how it is entered and retrieved.

The crucial change is i

Start unifying schema types

Schemas per se are type agnostic, isLookup property is removed. Data is stored and accessed differently based on how it is entered and retrieved.

The crucial change is introduction of the composite key of pid and rid. Previous page data utilizes rid = 0 to differentiate itself. Other types, notably lookup, have autoincrementing rid.

Database migration is not implemented yet.

show more ...

Add comparator strings

Add missing translations

This commit adds '%lastsummary%' special column for page schemas. The column contains the summary of last page revision.

fix: make html5 datetime picker actually work

The datetime picker expects and produces dates / time pairs separated by
the "T" character, not a space. Further, it does not handle seconds at
all.

Th

fix: make html5 datetime picker actually work

The datetime picker expects and produces dates / time pairs separated by
the "T" character, not a space. Further, it does not handle seconds at
all.

Therefore, we have to provide the timestamp in the input field separated
by a "T" and for consistency drop seconds altogether. Hence, it
becomes necessary to replace the "T" by a space again before providing it to jQuery
date picker fallback.

Further, we have to actually parse the "T" when validating the
timestamps we receive from the user.

show more ...

"struct_lookup" action for bureaucracy

Action allows create struct lookup entries using bureaucracy form. Syntax:
<form>
action struct_lookup
...
</form>

<form> can contain any number of st

"struct_lookup" action for bureaucracy

Action allows create struct lookup entries using bureaucracy form. Syntax:
<form>
action struct_lookup
...
</form>

<form> can contain any number of struct_field or struct_schema. Data will be saved to respective lookup schemas.

show more ...

More German translations

Add button to clear schema data