otherwise, it added the new fields directly to SiteConfig
I don't think that's going to work… that'll change the table name of siteconfig as well… if it even gets picked up
Why do you want a separate table though?
which means, in templates would I have to change from
Extensions add functionality to an existing class… the class name remains the same
Just think about it as custom functionality you slap onto an existing class
Not as a new class by itself
so just to test it, I added
private static $table_name = 'SiteConfigExtension'; and it did add the new tables for it and when my settings tab refreshed I lost the original
Slogan I had saved previously
Should that even be allowed?