added a config option not to add the validate_uniqness validation. i need this fir e.g. translated fields. and i had issues loading vhost before the globalize2 extension (was not able to use the derived classes of page then ...)
updated readme with install instructions
this works on a clean radiant install
missed to copy rb file
flatten! returns nil if there is no subarray (no sti in vhost.yml); j…
…ust load applicationcontrollers
add meta tags to the mix, realy remove indizes
thanks for the contribution. I'm going to pull this, but I'm thinking that we should put these special cases in the config file. I pulled out a lot of "if this model" kind of code from the original.
yes, sure. all needed customizations should be in the yaml file.
Or perhaps there's another way. Maybe we could check for an index on name and conditionally alter that so that we don't need to do configuration.
if it would be on a naming scheme it would work with convention over configuration. but there are special cases like the snippet which is not named with the rails naming scheme but a custom name. I don't know if this is necessary
added config option for not adding uniqness validations
Merge branch 'master' of git://github.com/saturnflyer/radiant-vhost-e…
Merge branch 'master', remote-tracking branch 'krug/master'
just standard radiant models in default config
use the first as default host (like with apache vhosts)
copy if not in vendor extensions
work on specs for vhost extension
all spec pass
add tmp to ignore
add defaults to rack cache
vhost import sheets