-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
admin cache
- Thread starter prophoto
- Start date
rob
Administrator
The issue here is that by enabling the system cache plugin you are telling Joomla to cache per page (based on the page's URI).
This cache is then checked when Joomla initializes - if a page matching the URI is found then that cached page is loaded.
If you disable the system cache plugin then you are asking each component/module to store its cached data.
When we save a record we clear out our component cache, we don't clear out Joomla's page cache.
You will see that Joomla itself behaves in the same manner, if you try to view an article, edit it in the admin and then view it again in the front end the initially cached page is still loaded.
Only once the cached page has expired is the new content queried for and shown in the browser.
If this is not the behaviour you need then turn off the system cache plugin.
This cache is then checked when Joomla initializes - if a page matching the URI is found then that cached page is loaded.
If you disable the system cache plugin then you are asking each component/module to store its cached data.
When we save a record we clear out our component cache, we don't clear out Joomla's page cache.
You will see that Joomla itself behaves in the same manner, if you try to view an article, edit it in the admin and then view it again in the front end the initially cached page is still loaded.
Only once the cached page has expired is the new content queried for and shown in the browser.
If this is not the behaviour you need then turn off the system cache plugin.