It would perhaps be clearer to require a user to specify that they want the query to apply to all pages with something like: /* Current page */ {{$myschema.myfield ? filter: "myfield < 5" or: "myfield > 5"}} /* Specific page */ {{$other-page.myschema.myfield ? filter: "myfield < 5" or: "myfield > 5"}} /* Search all pages */ {{$*.myschema.myfield ? filter: "myfield < 5" or: "myfield > 5"}}

That syntax is actually the same {{$ with the ID placeholder from the main Struct documentation, $ID$ (meaning this current page), as the page name.

This is a limitation of DokuWiki - you can't have any syntax inside headers: https://www.dokuwiki.org/faq:headerlinks

splitbrain on Apr 23, 2019 There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment the above does not need to happen during metadata rendering. Loading Sorry, something went wrong. Copy link Contributor Author iainhallam on Jan 20 There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment Is this not where the value would be put into the text of the abstract when rendering metadata? This is quite a complex part of the DokuWiki code and I'm not at all sure I understand it! Loading Sorry, something went wrong. Copy link Member splitbrain on Apr 21 There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment Hmm, I think you might be right. I forgot about that. Maybe give it a quick try by putting the value right at the top of the page and see what ends up in the abstract

iainhallam mentioned this issue on May 26 Value aggregation type #386

pirminkager mentioned this issue on Mar 14, 2019 Struct data as variables #145

The placeholder $STRUCT.<schema>.<field>$ always refers to the current page. But my intention is to have an aggregation as a table on a different page using the value of a struct field definied on the original page. So my suggestion for a new functionality would be like this : $STRUCTPAGE.<page>.<schema>.<field>$

create a page about software called "Dumblebum" the page will be created in :software:dumblebum:start

@NS@

This is possible - you just need to use different syntax. You need to surround the field name with either double @ or double # (@@field.name@@ or ##field.name##)

Note that the template has blank lines at the start... without them the struct data won't render for some reason

I used '---- struct table ----' with the 'filter' option to display a single record ... perfect But the value of my filter argument is static and I want to make it dynamic! I've seen how to 'call' my page with parameters but don't know how to retrieve this value and 'give' it to the 'filter' parameter of 'struct'. Any help ?

Page data is attached to pages. Each record is exactly one page

Try to avoid overthinking the issue. It's fairly simple. You define a table schema, consisting of several columns You assign it to one or more namespaces; as a consequence, each page in each of those namespaces will hold one row of the table defined in the schema defined in (1) Whenever you create a page in one of the affected namespaces, the editor will show you an entry form where you fill in the fields. The page holding the form must not be empty; you have to enter some text following the form, and if it's only a dot or period. You save your new page. From now on, it handles like any other page, with the exception that DokuWiki shows a box with the field names and values, followed by the text of the page. Editing the page will, of course, show the form again where you can edit the contents of the fields. Of course, there's more to it. You can query the rows in a given scheme, and there are ways for a page to refer to other pages, and so on. But once you've understood the basics, the rest follows quite naturally.

iainhallam commented on Mar 6 The PR has been updated; awaiting review at the moment, and there's a question of how metadata is handled which may need a separate issue. ❤️ 1 Loading Sorry, something went wrong. Copy link Contributor annda commented on Apr 21 It looks like we are finally approaching the finishing line with this useful feature. @iainhallam and other interested parties, can you comment on the hopefully final questions in the PR? #386 (comment) 🚀 1 Loading Sorry, something went wrong.

Using Unison with DokuWiki Unison is a file-synchronization tool for Unix and Windows. It allows two or more file repositories, to be kept synchronised by detecting and then propagating changes between the repositories, no matter if they are different directories on the same disk, or on completely different filesystems on different machines. I encountered several problems when I first tried to syncronise my laptop ↔ desktop ↔ webserver with this site.