Forgive me if this is a stupid or already covered question - i did
the radiant site and mailing list, but did not see any conclusive
In a nutshell:
I see that the path to the plugins lib directory is properly added to
load_paths by railties/initializer.rb load_plugins().
But then the path is completely overwritten in
I am trying use a regular rails plugin “acts_as_taggable_on_steroids”,
would like to use several others.
I dont need to use it as an extension in Radiant - it will be used
in the same application. (My app mixes Radiant with a rails app through
lovely “radiant_on_rails”, "share_layouts, and “record_tags”
It is probably possible to create an extension that wraps it - but I
prefer not too. It’s nicest (and easiest) if I can just load existing
plugins and also keep them up to date as people release new versions.
The problem that I am having is that this plugin has several modules in
lib directory that cannot be discovered by rails
Dependencies.load_missing_constant because the path has been removed
the Dependencies.load_paths array by Radiant.
So when I try to use this Plugin I get a
NameError in TesterController#tagtest
So, are plugins basically not supported in Radiant?
Is there a reason for that… and is there a reason for totally
the Dependencies.load_paths array? Or is this something that could be
changed, for example that radiant/extension_loader.rb
appends the paths to load_paths instead of overwriting it?
Thanks for any insight into this!!!