Bug report: Cache issue in ProjectConfigOptions?
Page: 1
In my module I use ProjectConfigOptions.class.php for storing some settins for project. While debugging my module I think i found a bug.
The ProjectConfigOptions are cached, but when I alter and save my option, the cache won't refresh. Database record is OK. I have investigated the source and there was no chace refresh by updating the project config in db.
The solution for me was creating a method in my module's Controller, which deletes the cache record for that option each time my config option is saved.
The ProjectConfigOptions are cached, but when I alter and save my option, the cache won't refresh. Database record is OK. I have investigated the source and there was no chace refresh by updating the project config in db.
The solution for me was creating a method in my module's Controller, which deletes the cache record for that option each time my config option is saved.
Thanks for reply, I check that in SettingsController.
I use ProjectConfigOptions::setValue(), because there is an argument $project. I didn't find a way to tell ConfigOptions that I need to create/change the ProjectConfigOption. Maybe I only looked in a wrong place...
I use ProjectConfigOptions::setValue(), because there is an argument $project. I didn't find a way to tell ConfigOptions that I need to create/change the ProjectConfigOption. Maybe I only looked in a wrong place...



