Phantom variables get created upon saving config

Thank you for pointing this out. I will look into it (I never noticed the phantom variables), but my concern is about when the module is already in use. That is, I have to put in code to migrate variable values from the old (current) variables to new ones and then delete the old ones.

Hi Gribnif, can you tell me which database table gets the phantom variables and what are they named like? I am having trouble spotting anything unusual. Thanks.

Just noticed this with 6.x as well.

@alpha2zee check out the variable table. The form currently saves the data once using _htmLawed_store_setting() and then system_settings_form_submit() also saves the variables based on the FAPI element name.

If you were to go Gribnif's route you could use a hook_update_N() to migrate the old variable to the new ones.

HTH

Andy

Thanks, AndyF. I will fix the codes in a week or so once I have the time.

I have released version 3.1 and 2.11 of the module for Drupal 6 to fix this issue by unsetting the unnecessary form values in _htmLawed_store_setting() to prevent the creation of the phantom variables 'cache', 'config', 'help', and 'spec'. I did not implement a functionality to remove such (harmless) phantom variables if they already exist in the 'variable' table of the Drupal database because of the possibility that some other module may be using variables with identical names.