Custom fields are not being shown (or removed) until cache is refreshed
Description
is duplicated by
relates to
Activity
Derek Ramsey July 12, 2017 at 7:39 AM
Verified the option to create additional fields is working properly on trunk. Ready to merge to 11x.
Matthew Jones March 16, 2017 at 11:03 AM
It looks like we're going to need a new method in the service that will invalidate all of the calendars in the current site from the cache.
We could just invalidate the entire calendar cache (for a slightly easier solution) but this may cause performance issues depending on how often these fields were updated, so probably better to just get it right for the immediate site.
Neal Caidin April 11, 2016 at 10:44 AM
Downgrading to Major priority based on input from several institutions. Not a commonly used feature.
Neal Caidin April 11, 2016 at 10:42 AM
Tested on Marist QA server and stills seems to be an issue.
Neal Caidin May 5, 2015 at 10:34 AM
I can reproduce on the Marist QA server and on nightly trunk /Mysql.
To reproduce:
1) As instructor click on Schedule tool, then Fields
2) Enter a new field name and click Save Field Changes
3) Add a calendar item. You do not see the new field.
4) Log in as admin and clear memory cache. Log in as instructor and you will see the new field.
Details
Details
Priority
Major
When creating or removing custom schedule fields, the changes are not being reflected immediately. It seems that when resetting the Sakai caches with the Memory tool as admin, this fields are refreshed.
I wonder if is related to this issue. The problem cannot be reproduced on 10.x.
An alternative description from
On the Fields page, you can create and 'Save' new fields, which appear in the list of fields (see screenshot). Click 'Save Field Changes'. But when you click on 'Fields' again (or try to Add new event), the new fields are not there. If you use Memory tool in Admin Workspace to reset the cache, then the new field appears.
It's also not possible to remove a field, after removal, the field is still displayed. If you use Memory tool in Admin Workspace to reset the cache, then the new field disappears.