On Jun 21, 2009, at 7:30 PM, Jeff Casimir wrote:
Wow, great info. I was actually fighting with "comments" among others
for a few hours, but I'm sure I made it more work than necessary. Now
everything is going great and I have a lot better understanding of how
the extensions are managed and work.
I'm maintaining comments so it's probably my fault. But let me know
what you ran into, I made a few commits to the main repository that I
shouldn't have pushed until I had the fixes in so you may have pulled
it down in that window. Also, I'm integrating built-in spam filtering
and other things, so the code is getting a lot of updates.
It would be pretty awesome if some kind, free-time having soul were to
implement "isitradiant.com" like "isitjruby.com". Especially with
Radiant being at 0.8 and, at least from the version number, reserving
the right to break compatibility at will, it would be awesome if there
were a site that did nightly integration tests of all the extensions
in the registry. It would be tougher to do "Radiant + Extension A +
Extension B" combinations, but at least "Radiant + A" singles would be
really useful information.
I would personally love to see that. I've been meaning to contact the
folks at http://runcoderun.com/ to see if they'd have a way to do it.
The way I think we'll need to address it for now is to have people
from the community help test. I, for example, use PostgreSQL so I try
to make sure that the Radiant core will pass all of those tests,
wheras others use MySQL or SQLite and test there.
On Sun, Jun 21, 2009 at 7:20 PM, Jim Gay<j...@saturnflyer.com> wrote:
On Jun 21, 2009, at 3:33 PM, Jeff Casimir wrote:
Is the expectation that unless the GitHub page specifically says
an extension works with 0.8, that it WON'T work?
Maybe. It depends. Some extensions might not require an update.
I've tried and failed to install a few extensions, and now there's
much non-working cruft that I'm thinking it'd be easier to start a
instance and transfer all my content then debug what's wrong with
different rake tasks, migrations, etc.
Different pages have different suggestions for installation process,
is it "more preferred" to use:
script/extension install extension_name
These are entirely different things.
Using "script/extension install extension_name" will get
the extension registry http://ext.radiantcms.org/, pull down the
run the migrate task, and run the update task.
The command "rake radiant:extensions:extension_name:install" would
some command to perform the "install" rake task (assuming it
exists) in the
To see what rake tasks your extensions provide, you may do "rake -
the root of the project.
I've had better luck with the former, but many of the github pages
suggest the latter.
Using "script/extension" will pull down the information. This is
the same as
a download, git clone, svn checkout, or whatever else. "script/
install" assumes the presence of "migrate" and "update" tasks for
extension and runs them.
If you were to use some other process for getting the code
clone, etc) you'd still need to run whatever tasks are necessary to
"install" the extension. Some extensions need a database migration,
need to put files in the public directory (the "update" rake task)
others need nothing.
Help (http://ext.radiantcms.org/extensions/5-help), for example,
to just be a drop-in extension (no migrate or update tasks) where
put it in your project and start up the server. Dashboard
update task to be run but no migration. RBAC Base
(http://ext.radiantcms.org/extensions/87-rbac-base) requires both
and update to be run.
Apologies if I'm missing something obvious,
Not obvious, but Josh French has committed changes for the next
will allow extension developers to configure dependencies from the
which might help with the installation process as far as things
messages go. There will be more development on this in the future.
And the Ray extension (http://ext.radiantcms.org/extensions/36-ray)
way to manage dependencies from within an extension (as well as min/
versions of Radiant), but I'm not sure how many take advantage of
You might be able to get a lot of help by simply emailing the list
something like "I want to upgrade to Radiant 0.8.0 and I have
Y and Z. Are all of those extensions ready?"
You're likely to get replies from the extension authors, or other
those extensions who might know.
So... what extensions do you have?
I personally have many extensions which I wrote and manage and
is not my full-time job, so some may not work yet. If it's a simple
I know somebody needs it, I'm happy to address the changes.
This is a pretty helpful community, so just ask away.
Radiant mailing list
Radiant mailing list
Radiant mailing list