Use database storage instead of variables table for better memory usage with multiple instances

+++ b/colorizer.admin.inc
@@ -267,15 +267,7 @@ function colorizer_admin_form_submit($form, &$form_state) {
-    // Delete old files.
-    foreach (variable_get('colorizer_' . $instance . '_files', array()) as $file) {
-      @drupal_unlink($file);
-    }
-    if (isset($file) && $file = dirname($file)) {
-      @drupal_rmdir($file);
-    }

Not sure why the file deletion code was removed. Don't see it in colorizer_delete.

Hi Guys,

I've just updated to latest dev from 1.4 within my custom distribution.

I'm running some tests now on sites and custom colours stored in the database seem to be getting lost when update.php is ran. I could export the variables to a feature but I'm not sure that that will help if Colorizer is no longer using variable storage. Can you please provide some advice here?

I'm using radix subthemes / radix colorizer.

I am not able to reproduce any problem here. The custom colors on our sites are retained with updates. If you can reproduce this somehow please open a new issue with more details.