For anyone (now or in the future) following this thread, I've identified
the issue nurullah mentioned here. It is indeed a bug with the SnS
extension and will be resolved in the upcoming 0.5 release.
For those interested, it's caused by the interplay between the way SnS
extension stores its
What was the fix for SnS?
I saw the same problem with RBAC Base on a clean install (which I must
not have tried when we created it) and haven't had time to look into it.
-Jim
On Jun 15, 2008, at 9:19 AM, Chris Parrish wrote:
For anyone (now or in the future) following this thread, I've
Chris,
We might be able to make a rake task that loads the environment with no
extensions installed. In fact, it should be as easy as something like this:
task :minimal_environment do
Radiant::Initializer.run do |config|
config.extensions = []
end
end
Then we could make
Nate,
Glad you like it.
You are my frickin' hero!
:-)
Andrea is the hero. I just took a hatchet to his code!
can I add additional columns in extension migrations or will it
somehow break the extension?
Give it a go. I don't think it should break anything. If you want the
extra fields
Nate,
I think most of the issues in upgrading to 0.6.7 with the rails_support
extension were normal ones you face going to Rails 2. Here is what
version control and my memory tells me I changed.
-- I backed up the database, dropped all the tables, and ran the
migrations for radiant and all
I'm not opposed to your solution in anyway. I think it'd be helpful. I
just think that the right solution for my extension would be to:
* have my extension's default settings installed via the initial
migrate task
* offer a rake task to allow administrators (server admins) to
I just outlined the fix in a reply to Sean's post. It's a little more
elaborate (though I think more elegant) than I'd post here.
If you're trying to get it to just work for now you can simply comment
out the following line from the styles_n_scripts_extension.rb file:
include CustomSettings
On Sun, 2008-06-15 at 17:45 +0100, Andrew Neil wrote:
You are my frickin' hero!
:-)
Andrea is the hero. I just took a hatchet to his code!
Well the, he rocks, too. In hindsight if I had been able to figure out
how the newsletter extension all works, I might have gone that route. As
it is, I
