Consolidate table access classes

Save empty page ids as strings, not NULL

pid is part of primary key and so must not be NULL. Otherwise the unique constraint does not work, SQLite effectively treats every NULL as unique.

Rudimentary handling of serial data

Serial data is bound to a page but does not affect versioning

The pull request: #464 causes a fatal error when the "$this->column" is false which may happen when the column is not defined. This commit fixes that.

Make field ids more unique

On some systems the timestamp-based field ids were not unique. In addition to being invalid HTML,
this broke e.g. date pickers. Might explain and solve #375

Display human readable labels in error messages

Becouse there are plugins that extends the Lookup type, we should check
if the column is Lookup or one of its descendants.

�� Fix fatal error if no sqlite adapter is available

If the sqlite plugin is installed and active, but no sqlite is available to the php binary (e.g. if
the extension is not installed or not enabled

�� Fix fatal error if no sqlite adapter is available

If the sqlite plugin is installed and active, but no sqlite is available to the php binary (e.g. if
the extension is not installed or not enabled) then that would cause a fatal error, because
getAdapter returns null and that case and trying to access getName on null doesn't work.

Closes #440

show more ...

use multi input in bureaucracy forms

this commit fixes a bug that causes an error when submitting bureaucracy form with struct multi input.

additionally it fixes one minor bug that causes struct lo

use multi input in bureaucracy forms

this commit fixes a bug that causes an error when submitting bureaucracy form with struct multi input.

additionally it fixes one minor bug that causes struct lookup fields loosing their selected values when a bureaucracy form was send with an error.

works only with: https://github.com/splitbrain/dokuwiki-plugin-bureaucracy/pull/226

show more ...

fix: proper error handling

fix: to proper handle placeholders in default values for struct fields, we must validate them only on submit

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

feature: hidden fields in bueraucracy form from struct fields

This commit adds extra syntax which allow us to add struct fields to bureaucracy forms as hidden fields:

struct_fieldhidden "products

feature: hidden fields in bueraucracy form from struct fields

This commit adds extra syntax which allow us to add struct fields to bureaucracy forms as hidden fields:

struct_fieldhidden "products.product" "=value"

This only make sense with #354

show more ...

fix: struct_field in bureaucracy form now supports a default value

Before that we cannot use bureaucracy default values for struct_field ("=default value" syntax). Now it's possible.

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

better handling of failing sqlite plugin init. fixes #200

renamed JSON to STRUCT_JSON. fixes #157

more Validator refactoring

Return false if schema doesn't exist

This way neither the JSON has to be created nor has it to be decoded in
order to understand that the schema doesn't exist

Leave error handling of helper methods to the caller

Add docblocks, better names and exception handling

Set the user explicitly during import

If left unset, it will default to the currently logged-in user

Reinitialize db if $conf['meta'] changed

Save user on schema change and more imexport tools

Reevaluate page assignments when replacing them