Thanks for your response. I appreciate it. The error messages were all of
the type "*undefined tag `snippet'*" along with no presence in the admin
panel -- just as if none of the default extensions existed.
Updating the Gemfile was the correct action, since apparently between 1.0.1
and 1.1.1 the default Gemfile was changed to include the extensions as
gems. Which makes sense, but I wasn't expecting it. Or perhaps I had a
bizarre setup that wasn't using Bundler as it was meant to be used.
Whatever the case, I got it all fixed with the following Gemfile, based on
the latest versions available in RubyGems:
# START Gemfile
gem "radiant", "~> 1.1.1"
# SQLite is the default database connection but only suitable for local use
gem "sqlite3", "~> 1.3.4"
# A standard gem extension
# gem "radiant-example-extension", :version => "~> 1.0.0"
gem "radiant-archive-extension", "~> 1.0.7"
gem "radiant-clipped-extension", "~> 1.1.1"
gem "radiant-debug-extension", "~> 1.0.2"
gem "radiant-exporter-extension", "~> 1.1.0"
gem "radiant-markdown_filter-extension", "~> 1.0.2"
gem "radiant-sheets-extension", "~> 1.1.0"
gem "radiant-site_templates-extension", "~> 1.0.6"
gem "radiant-smarty_pants_filter-extension", "~> 1.0.2"
gem "radiant-snippets-extension", "~> 1.1.0"
gem "radiant-textile_filter-extension", "~> 1.0.4"
# END Gemfile
The config/environment.rb file was (and is) stock as generated by the
I do have two other questions though.
1. I'm familiar with using the file-system extension to export from the DB
to the file system; is saturnflyer /
radiant-file-system-resources-extension the best current version of this?
2. I have a client on a Radiant 0.9.1 system with a bunch of extensions
installed via Ray. While I want to migrate them, I'm going to have to do
some extensive development sandboxing to make sure it's seamless. Are
there any (security) steps I should take in the mean time for Radiant
0.9.1? I think I saw that the change to 1.1.1 from 1.1.0 was security
On Tuesday, January 29, 2013 10:32:13 PM UTC-5, Jim Gay wrote:
> The way extensions are listed on http://ext.radiantcms.org/ is that
> they list their minimum requirement.
> That may still be accurate but there have been some changes to
> extensions since that project was created.
> Can you provide your Gemfile and any error messages that you have?
> Can you share your config/environment.rb file?
> It's unlikely that they've disappeared. It may be so, but it's unlikely.
> On Tue, Jan 29, 2013 at 9:02 PM, Derek R. Austin
> > Hi everybody,
> > I updated from Radiant 1.0.1 to Radiant 1.1.1 using Bundler, and now all
> > extensions have disappeared. It's only stock extensions anyway --
> > clipped, debug, exporter, markdown_filter, sheets, site_templates,
> > smarty_pants, & textile -- but they're broken. I tried adding them in
> > Gemfile to no avail.
> > I've been hesitant to use any non-stock extensions with Radiant 1.0 due
> > the fact that the vast majority of them listed at
> > do not list compatibility with the new versions.
> > So, with this Radiant install, it's been straight vanilla. After
> > around, it seems like Radiant is stable at 1.1.1 and will be broken
> until a
> > new version comes out meant only for use with Ruby 1.9. So, I thought I
> > would upgrade since my Radiant 1.0.1 site has random downtimes all the
> > and now I have no website at all.
> > Please help?
> > Thanks!
> > Derek
> > --
> > Derek R. Austin
> > --
> > ---
> > You received this message because you are subscribed to the Google
> > "Radiant CMS" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > For more options, visit https://groups.google.com/groups/opt_out.
> Write intention revealing code #=> http://www.clean-ruby.com
> Jim Gay
> Saturn Flyer LLC
You received this message because you are subscribed to the Google Groups
"Radiant CMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.