1) Clear all caches (and make sure that they're really cleared).
2) Do a "DELETE FROM ezsession" in the database. 3) Make sure that the view cache mechanism is turned on...
Olivier: You're not the only one, I have the same problem.
Allman: This doesn't fix the problem for me. The only thing changed is the width of content structure being large instead of small, but changing it is still not possible.
This entry was not in my site.ini; I added it and now it works fine. Thanks! I didn't see the instruction to add it anywhere, ViewCaching=enabled was the only setting I added.
You must have missed it, the upgrade page explained it under the header: <b>Adding a setting to site.ini.append needed for the new administration interface</b>
Indeed the CachedViewPreferences[full] and ViewCaching=enabled entries were broken in my site.ini.append.php file. However even without these missing entries, I figured out that if I logout and then logon in the admin interface, the preference previously set are taken into account (at next logon of course).
Then I ran the procedure
1) Clear all caches (and make sure that they're really cleared).
2) Do a "DELETE FROM ezsession" in the database. 3) Make sure that the view cache mechanism is turned on...
suggested by Allman without any success (preferences are still taken into account after delogging and relogging.
I feel that I am close to the final solution but sth is still wrong.
Btw: in my current configuration , if i go to setup/cache management the "Content view cache" check box is grayed like it is unavailable. I don't know if this might impact the user preferences neither how to change it.
Thanks a lot Frederik: you oriented me in the right direction:
I had
ViewCaching=disabled in override/site.ini.append.php
and ViewCaching=enabled in siteaccess/admin/site.ini.append.php
I naively thought that the last entry is the one taken into account but actually it appears that override/site.ini has the precedence (am I right and is it normal? )
So I suppressed the viewcaching entry in the override/site.ini and now it works.
Olivier
You must be logged in to post messages in this topic!