Giovanni Intini wrote:
1) Export / Import parts of the tree. I work on customers' websites on
subtrees of the main site, it would be great to be able to export those
subtrees so I could import them into a new installation and have the site
work fine.
Better export and import code is in the
Hi,
I'm having a problem with the FileListBehavior not using the path
attribute specified, only the radiant/public directory...
I have a child of the homepage, 'Images', with the following body part:
--8 --
Here is a list of files in this directory:
r:files:each
2006/9/11, John W. Long [EMAIL PROTECTED]:
Better export and import code is in the pipeline. I'm not sure if itwill be as granular as you suggest above, but I am definitely open tothe possibility.Right now I'm just recreating the structure on the deploy server and cut'n'pasting the content. It's
Wouldn't #2 #3 be essentially the same? One would just filter
through a domain while the other only a folder. That is, if the
multisite setup is the same as the one I saw a while ago, where each
site is a heirarchy of folders.
Just my non-technical .02,
Erik Mallinson
On 9/11/06, John W. Long
Hi,
Following the instructions on
http://theplant.jp/blog/2006/07/27/radiant-virtual-domain-plugin I
have a problem with the patching stage:
$ patch -p0 vendor/plugins/virtual_domain/virtual_domain.patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
Thanks for the suggestion!
I tried reopening PageContext and adding my define_tags in a plugin, but
Rails didn't seem to like that and refused to start. I required
page_context.rb to load the model class during plugin initialization and
extend it properly, but that approach didn't work.
Any
Wolfgang,Instead of changing PageContext, change Behavior::Base, like soBehavior::Base.define_tags do tag mytag do |tag| ... end ...endJust make sure that it loads before anything else,
i.e. make the plugin folder start with 01_ or something.Cheers,Sean Cribbsseancribbs.comOn 9/11/06,
Wolfgang
Sean,
thanks, but that's exactly what I'm doing right now - I just thought
extending PageContext might be the more elegant solution than prefixing
my plugin directories... Anyway - I'll go with what works.
Cheers,
Wolfgang
--
Posted via http://www.ruby-forum.com/.
Did you install radiant using the gem? Because when you do so the radiant
application is actually in your gem directory. You might be able to go to
the radiant gem directory and apply the patch, although that's probably a
bad idea.
I posted a simple plugin a little bit ago that adds multisite
Sean Cribbs wrote:
Yeah, I don't know that it will get you anything, though. At issue is the
order in which the tags are loaded/defined, i.e. if a behavior is defined
before your global tags, those global tags won't work on pages that have
the
behavior.
But if you can define them on
I haven't been a part of this list long, but I've seen several posts
mentioning plugins. Are these plugins referring to some sort of
RadiantCMS plugin API? Or are these just regular Rails plugins?
Thanks in advance!
Justin
On 9/11/06, Dave Crossland [EMAIL PROTECTED] wrote:
On 11/09/06, Paul
Hi Wolfgang and John,It might be worth if it works in production and not in development, I had a similar problem with the PageContext and with a tagging plugin I did. My solution was to put the code in PageContext.rb
- test it in development and then move it to the plugin and test again in
jf wrote:
I haven't been a part of this list long, but I've seen several posts
mentioning plugins. Are these plugins referring to some sort of
RadiantCMS plugin API? Or are these just regular Rails plugins?
Presently they are regular Rails plugins that are written specifically
for Radiant.
On 06/09/06, Sean Santry [EMAIL PROTECTED] wrote:
Here's the corrected version:
If I want to use these behaviours, how do I go about that? :-)
--
Regards,
Dave
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search:
If I want to use these behaviours, how do I go about that? :-)
Oh, and if you were also wondering how you would actually use the
tags once you've got the behavior installed, here's an example:
r:previous by=published_atr:link//r:previous
r:next by=published_atr:link//r:next
- Sean
On Sep 12, 2006, at 3:34 AM, Dave Crossland wrote:
On 11/09/06, Paul Stadig [EMAIL PROTECTED] wrote:
Did you install radiant using the gem?
Yes
Because when you do so the radiant
application is actually in your gem directory. You might be able
to go to
the radiant gem directory and
Sorry about that...my fault entirely. I forgot to update the readme
when I changed the way the attributes worked.
I realized that there was actually no need for the 'path' attribute
at all, so it's all done in the 'glob' attribute now, like this:
r:files:each
In case you missed the announcement on Ruby-Talk or on the Radiant
Weblog, the new Ruby site is now live:
http://ruby-lang.org
The Ruby site is the reason that Radiant exists. Thank you for
supporting me in this endevour by supporting Radiant. You have helped me
work many of the kinks out
18 matches
Mail list logo
