Skip to content

Commit

Permalink
Update Documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
froemken committed Feb 12, 2020
1 parent bbe5d91 commit 27d0f74
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 1 deletion.
9 changes: 9 additions & 0 deletions Documentation/KnownProblems/Index.rst
Expand Up @@ -9,3 +9,12 @@ Known Problems

If walls.io will change their JS implementation and their XHR/Ajax Requests, this extensions
may not work anymore.

We try to keep the requests to walls.io as small as possible. That's why we cache the response into a record
of sys_registry. Why not TYPO3 Caching Framework? In past we found out, that 1 or 2 times a day we get no data
from walls.io. So, if you clear the TYPO3 Cache, the Cache of walls_io_proxy would be cleared, too. In that case it
may happen, that the output is empty and would be stored in cache_hash. In that case the output will be empty until
the cache is cleared again.
That's why we store the request in sys_registry. If you clear the cache and we don't get data from walls.io we
can still access the entry from sys_registry and show the wall. But how to remove the entry from sys_registry? We
have added a button into Plugin Preview in Backend to clear the cache for the configured wall in the plugin.
2 changes: 1 addition & 1 deletion Documentation/Settings.cfg
Expand Up @@ -27,7 +27,7 @@ project = Walls.io Proxy
# ... (recommended) version, displayed next to title (desktop) and in <meta name="book-version"
# .................................................................................

release = 2.0.0
release = 2.0.1

# .................................................................................
# ... (recommended) displayed in footer
Expand Down

0 comments on commit 27d0f74

Please sign in to comment.