Re: [Radiant] Re: vhost extension site scoping

2011-02-15 Thread Haselwanter Edmund
On 15.02.2011, at 01:37, craayzie wrote: Below is the migration that finally did the trick! There wasn't really a need to have an index on the name attribute anyways since it'll always require the site_id. The uniqueness of a field in rails is a programatic constrain in ruby, not a

Re: [Radiant] Re: vhost extension site scoping

2011-02-14 Thread William Ross
On 14 Feb 2011, at 08:14, craayzie wrote: So weird. I run the migration but it does nothing to db/schema.rb: add_index snippets, [name, site_id], :name = index_snippets_on_name_and_site_id, :unique = true add_index snippets, [name], :name = name, :unique = true Here's the exact

Re: [Radiant] Re: vhost extension site scoping

2011-02-14 Thread Haselwanter Edmund
Snippet: name: message: 'Name wurde schon verwendet' scope: site_id in config/vhost.yml should do the trick ... On 14.02.2011, at 09:14, craayzie wrote: So weird. I run the migration but it does nothing to db/schema.rb: add_index snippets, [name,

Re: [Radiant] Re: vhost extension site scoping

2011-02-13 Thread William Ross
On 14 Feb 2011, at 05:46, craayzie wrote: So this appears to be simple issue of the Snippets model validation not being updated. I know the proper way to do this is to create an ActiveRecord migration but just to see it work I hand-edited vendor/ radiant/app/models/snippet.rb -