The current way of storing settings in the db and then loading with each page load is suboptimal. These settings change infrequently and shouldn't need to be taken each time from the db.

At the very least we should be caching the configuration arrays. Better yet, though, we could save them as text files and load them accordingly (yes, as was done in the drupal-id approach).

I'm seeing two steps.

1. It would be quite easy to set the configurations generated through the current UI to save as text files. After all, we already have the function in place to generate the config array from the db.

2. What would be a bit harder - but arguably worth the effort - would be to eliminate the need altogether for db storage and instead both read from and write to config files. This would require writing a parser to read in settings from the config array.

We could implement 1. and leave 2 for later.

This looks like what would be needed to bring the two divergent tinymce approaches fully back together.

Comments

mupsi’s picture

Issue summary: View changes
Status: Active » Closed (outdated)