Vic

I agree that the double click to edit is neither intuitive (as it's really not used in many places elsewhere) nor accessibility-friendly. Personally, I'd prefer to keep things simple. A...

In case it matters, the field "customer" in the schema "customerdocumentation" is a lookup field to "customer.fullname". But as mentioned, the lookup works fine within the field list.

Further testing confirmed: If the reference field in @@schema.field@@ is a field of type `lookup`, then it doesn't work anymore.

I can't reproduce your issue. I copied your exact text to a fresh page: ``` ====== header ====== Some text ===== subheader ===== Some more text ``` This page loads...

This is quite a nuisance, indeed. And it does clearly look like a bug. Because when you toggle back to DW Edit from WYSIWIG, you see that there indeed are...

@sharathsivakumar can we get an update?

I second the feature wish. Right now, the tool is great for making changes to an existing table but adding rows is still a bit cumbersome. Would be great if...

That's a helpful alternative, thanks! On 19.08.2015 16:03, Andreas Gohr wrote: > Rows and cols can now be added by dragging the autofill marker across > the edge of the...

I was trying to research this issue and remembered that in 2022, bureaucracy stopped submitting lookup field values altogether, as described in https://github.com/splitbrain/dokuwiki-plugin-bureaucracy/issues/313. Since a structjoin field is just a...

With some more testing, I seem to have found a workaround that may help in certain instances. While directly referencing a structjoin field in the bureaucracy form will lead to...