6 Commits

Author	SHA1	Message	Date
Hannah Wolfe	d587a845d4	Set migrations to use new 000 schema ... issue #632 - removed old schemas - updated base model to reflect all of the consistent behaviours and properties across the models - updated all models to match the new schema TODO - no fixtures are currently loaded except settings - need to rename properties across the codebase	2013-09-14 20:01:46 +01:00
Hannah Wolfe	0b1ffcd1f5	Updating settings types ... - issue #573, issue #632	2013-09-14 19:04:41 +01:00
Adam Howard	3823d10c35	Restructure default-settings.json and add validations to important settings.	2013-09-14 14:29:27 +01:00
Adam Howard	e24b5c3382	Proper settings infrastructure, allowing new features without compromising old data. ... On server load, check for settings which have not been set, and apply a default value to the settings table from a JSON file.	2013-09-03 22:56:34 +01:00
Hannah Wolfe	c70dfde7e3	Agressive stripping of the model attributes ... - fixes #517 - prevents this from occuring again in future with other relations - validation function & stripping done for all models - casper test for flow, plus validation & logged out tests	2013-08-25 18:12:27 +01:00
Hannah Wolfe	30b4eb07f7	App restructure - closes #245 ... - This is a first pass at getting a more logical structure. The focus is on moving from admin/frontend to client/server. - The location of the databases is highly important, this isn't expected to change again In the future - client/assets should probably become public/ - more stuff should be shared (helpers etc) - cleanup some confusion around tpl and views	2013-07-11 20:23:34 +01:00