Drupal Commerce and The Variables Table
Just had this idea while looking at the variables table of an ubercart site i'm working on...188 rows for uc_variables (including address formats) and 76 without those.
We might add a section in the coding standards that would "regulate" the use of the variables table ?
Comments
Agreed. We polluted the
Agreed. We polluted the variables table a great deal with Ubercart by offering limited string override capabilities that were stored in the variables table (like changing the text of the "Add to Cart" button) and storing sets of data in the variables table that would've been more appropriate in their own tables (like address formats). We eventually got a feature request from Moshe about this to possibly implement an Ubercart specific variables table, but I think the best solution would be to correct the two instances of overuse mentioned above. That should cut down on a lot of the cruft. I'll review the development standards and am open to other suggestions; in general, for any bit of text, we should simply provide a default value wrapped in t() and have users rely on module / theme customizations and other localization modules to update the text where desired.