Hi!
I'm experiencing some strange behavior using the children:each tag and
the Dynamic Image extension
(http://github.com/narced133/radiant-dynamic-image-extension)
I have a page with, say, 3 subpages and implement the following code
in the main page:
r:children:each
r:image size=13
I had some trouble installing Alex's Settings extension. I had used it
successfully before, but this time, I was getting the following errors:
Could not load extension from file: radiant-settings_extension.
#NameError: uninitialized constant RadiantSettingsExtension
Finally, I realized that
Hi Jay
Jay Levitt wrote:
I had some trouble installing Alex's Settings extension. I had used
it successfully before, but this time, I was getting the following
errors:
Could not load extension from file: radiant-settings_extension.
#NameError: uninitialized constant RadiantSettingsExtension
I'm curious how many of you are keeping your Radiant apps in source
control and deploying it to your server? I'm looking to convert my
ancient radiant installs to such a solution but wanted to get some
feedback on the experiences you've had doing this.
Cheers,
Marty
Sean Cribbs wrote:
[about the problem loading Page subclasses during bootstrap]
http://github.com/radiant/radiant/commit/20d8f44d45f11a0e28231fdf86ded522ed927f6d
This seems to have reappeared in 0.6.9; the above commit is still in place,
but with PostgreSQL on Fedora Core 9, I'm getting:
%
On Sat, Oct 4, 2008 at 12:46 PM, Marty Haught [EMAIL PROTECTED] wrote:
I'm curious how many of you are keeping your Radiant apps in source
control and deploying it to your server? I'm looking to convert my
ancient radiant installs to such a solution but wanted to get some
feedback on the
Christopher Dwan wrote:
Hey, I just saw this on github!
http://github.com/tricycle/radiant-static-caching-extension
Has anyone used it? Is this 'production ready', i.e. safe to use? I
haven't seen any discussion about it..
I'm missing something.. how does this differ from page caching?
Just a thought I had in the shower:
Most attempts at CMS version control end up reinventing large parts of
subversion/git/etc. inside the database. Instead...
Why not use something like FuseFS to implement a filesystem that maps the
Radiant asset tree to paths like