Hi,
I’ve been trying to install the page_attachments plugin from these
instructions:
http://wiki.radiantcms.org/Installing_Extension_-_Page_Attachments
, but they don’t seem to work any more.
I’m using the Radiant Gem 0.6.4. The error I get is:
[shiny]:~/rails/site evansj$ rake production db:migrate
(in /Users/evansj/rails/site)
rake aborted!
uninitialized constant PageAttachmentsExtension::Technoweenie
I tried ignoring the bit of the instructions that says
“page_attachments requires Radiant 0.6.2, so either freeze edge or use
the 0.6.2 gem or later”, and did a rake radiant:freeze:edge anyway,
but it still didn’t work.
I even tried creating a brand new blank radiant installation, with a
brand new database. It still gave the same error when I tried to
install the plugin.
So my first question is, what is the new procedure? 
Secondly, would I be right in saying that most of the action is
happening on the trunk, and I should just go for that? How stable is it?
Jon
On Mon, 2008-02-11 at 23:26 +0000, Jon Evans wrote:
I’m using the Radiant Gem 0.6.4. The error I get is:
[shiny]:~/rails/site evansj$ rake production db:migrate
I think what you want is:
$ rake production db:migrate:extensions
Bill
Hi Bill,
On 12 Feb 2008, at 01:41, Bill B. wrote:
On Mon, 2008-02-11 at 23:26 +0000, Jon Evans wrote:
I’m using the Radiant Gem 0.6.4. The error I get is:
[shiny]:~/rails/site evansj$ rake production db:migrate
I think what you want is:
$ rake production db:migrate:extensions
That doesn’t work either. 
[shiny]:~/rails/site evansj$ rake production db:migrate:extensions
(in /Users/evansj/rails/site)
rake aborted!
uninitialized constant PageAttachmentsExtension::Technoweenie
(See full trace by running task with --trace)
And I forgot to mention it last email, but obviously this problem
stops the site from running as well:
[shiny]:~/rails/site evansj$ RAILS_ENV=production mr
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with production environment…
/opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/vendor/rails/
activerecord/lib/…/…/activesupport/lib/active_support/
dependencies.rb:477:in const_missing': uninitialized constant PageAttachmentsExtension::Technoweenie (NameError) from /Users/evansj/rails/site/vendor/extensions/page_attachments/ page_attachments_extension.rb:25:inactivate’
from /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/lib/radiant/
extension.rb:39:in activate' from /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/lib/radiant/ extension_loader.rb:118:inactivate’
from /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/lib/radiant/
extension_loader.rb:106:in activate_extensions' from /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/lib/radiant/ extension_loader.rb:97:inselect’
from /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/lib/radiant/
extension_loader.rb:97:in activate_extensions' from /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/lib/radiant/ extension_loader.rb:42:inrun’
from /opt/local/lib/ruby/gems/1.8/gems/radiant-0.6.4/lib/radiant/
initializer.rb:45:in initialize_extensions' ... 17 levels... from /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/ mongrel/command.rb:212:inrun’
from /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/
mongrel_rails:281
from /opt/local/bin/mongrel_rails:19:in `load’
from /opt/local/bin/mongrel_rails:19
Jon
Hi Jon,
On Tue, 2008-02-12 at 10:02 +0000, Jon Evans wrote:
That doesn’t work either.
[shiny]:~/rails/site evansj$ rake production db:migrate:extensions
(in /Users/evansj/rails/site)
rake aborted!
uninitialized constant PageAttachmentsExtension::Technoweenie
You might want to look at how you installed the extension. Your
page_attachments directory should contain lib/technoweenie/ where the
attachment_fu code lives. I don’t really know the mechanism, but
radiant/rails finds code in the lib directories automatically.
Anyway the technoweenie code is an svn:external wrt page_attachments.
Perhaps it’s just not installed?
I’d refer back to the wiki page for installing the extension, but I
can’t seem to load it just now… Anyway I followed those instructions
very recently and things worked properly.
One thing that might not be in those instructions is the need to load
the shards extension prior to other extensions - I have a line in my
config/environment.rb that reads:
config.extensions = [ :shards, :textile_filter, :markdown_filter, :all ]
Another difference between my setup and yours is that I am using Rev 631
of radiant, not the 0.6.4 gem, and also not the trunk from svn. (I chose
that rev because it contains a page caching fix I wanted.) I was worried
about stability of the trunk, and prefer to use official releases where
possible.
Also I’m using Rev 58 of page attachments.
Let me know if any of this helps…
Bill
Hi Bill,
On 12 Feb 2008, at 19:32, Bill B. wrote:
You might want to look at how you installed the extension. Your
page_attachments directory should contain lib/technoweenie/ where the
attachment_fu code lives. I don’t really know the mechanism, but
radiant/rails finds code in the lib directories automatically.
Anyway the technoweenie code is an svn:external wrt page_attachments.
Perhaps it’s just not installed?
OK, I think we’re getting somewhere now.
Sean?
On Feb 8th you edited the Page Attachments Installation page on the
wiki (http://wiki.radiantcms.org/Installing_Extension_-
_Page_Attachments) and changed the subversion URL to
http://dev.radiantcms.org/svn/radiant/trunk/extensions/page_attachments
. But that version of page_attachments doesn’t have the
svn:externals property set in the lib dir so it doesn’t pull down the
technoweenie code.
Now I’ve installed page_attachments from the old svn url, radiant
seems to run the migration properly.
chose
that rev because it contains a page caching fix I wanted.) I was
worried
about stability of the trunk, and prefer to use official releases
where
possible.
I haven’t investigated the shards extension yet, but I’ll install it
if it seems to need it. Same goes for using a different version of
radiant itself.
Thanks again for your time
Jon
Jon,
Thanks. I intend to move the plugin to vendor/plugins anyway. I’ll do
that ASAP.
Sean