You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2022. It is now read-only.
When I modify any of the wiki pages containing the "data" customer blocks, and then subsequently go to the "results" page, the data does not automatically refresh. I have to actually edit the "results" page, make a change, and save it for the table to take any changes into effect in the "data" customer blocks.
Is this a bug or normal behaviour?
Thanks.
The text was updated successfully, but these errors were encountered:
Hi, at the moment that is the intended behaviour. Strata lets DokuWiki cache the results of queries, so pages can be presented to the user faster.
You can place the default dokuwiki no-cache syntax on the page to force the page to be refreshed every time it is visited:
~~NOCACHE~~
Alternatively, for a single update you could also edit the page, which forces a refresh as well.
Hope this helps!
Aside: Implementing fully propagated cache refreshing isn't trivial, as it would need to take into account all page from which data was used to answer your query. I'll think about how to handle a simpler form of caching, as this is indeed a problem.
So I am struggling a bit with syntax of Strata so I haven't messed up.
As a test, I have three or four DokuWiki pages with blocks similar to:
[data customer]
Name: Bloke
Product: pdm
Enterprise: yes
CUCM: no
Lync: no
ShoreTel: no
Avaya: no
Genesis: no
[/data]
Then I have a separate page, call it "results" for clarity:
[table ?c "Customer" ?p "Product" ?m "CUCM"]
?c is a: customer
?p = egw
?c Product: ?p
?c CUCM: ?m
[/table]
When I modify any of the wiki pages containing the "data" customer blocks, and then subsequently go to the "results" page, the data does not automatically refresh. I have to actually edit the "results" page, make a change, and save it for the table to take any changes into effect in the "data" customer blocks.
Is this a bug or normal behaviour?
Thanks.
The text was updated successfully, but these errors were encountered: