We have been in the process of building a large (300+ page) DNN based predominantly on the Text/HTML module. DNN is running on a dual core server with 4GB of memory. During the creation of pages through the DNN admin we have experienced a number of problems that appear to be cache related. Here is an example:
A user adds a new module to the top of a page that already contains a module. The module is then moved down using the drop down menu. After the page refreshes the module remains at the top of the page. If the drop menu is selected again it indicates that the module is now at the bottom of the page (it only has a 'move up' option). This indicated to me that the database had recorded the position of the module correctly but the page returned to the user was a cached page.
Similiar problems have been experienced when changing page settings, changing module settings and viewing pages in the page manager.
Clearing or switching the cache off resolves these problems. However, the cache cannot be swtiched off permanently as it severely degrades perfomance. We have tried the low, moderate and high disk based cache settings.
These problems tend to occur more frequently if network access is poor (high latency). We also noted that this problem occured frequently if the copy function was used. We requested that users not use this function but the problem has persisted.
This is considered a critical issue by our client. The user experience is poor and has resulted in users repeating actions because they believe the action has not occurred the first time.
Has anyone else experienced this? Is there anyway of resolving this problem other than disabling the cache?