Re: [Radiant] One more page launched on Radiant CMS! :)
Nope :( I used Photoshop droplet to get the right size and uploaded files myself. Then they put the pictures onto pages following my example. At least the lightbox ajax gallery is very easy to use as you know. T. You said that your non-tech customers edit the pages themselves. How are > you managing the images? With an extension? > > /AITOR > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] One more page launched on Radiant CMS! :)
* John W. Long <[EMAIL PROTECTED]> [2007-12-04 11:40:10 -0500]: > > On Dec 4, 2007, at 2:44 AM, Tõnu Runnel wrote: > > > I tried to leave all html code in the layout and snippets. So I gave > > the > > girls the pages tab where they entered all the content themselves (I > > only > > made some small examples). They had to use only textile + some few > > snippets > > and it was surprisingly easy and understandable for them -- without > > any > > knowledge of anything beyond office, browsers etc. So I guess in > > most cases > > there is no need for wysiwyg. And -- Word tables are more complex than > > > > | this | is | > > | a | table | > > So true! With a little training most people can grok basic HTML or > Textile. So if you have time to invest in your people you will be much > better off than resorting a clunky wysiwyg. Mostly true, except for tables like | This is a very very long long table zz mmm | kk kk another long cell | Otherwise, most things are quite easy and intuitive to do with wiki markup. saji .. -- APEC Climate Center +82 51 668 7470 National Pension Corporation Busan Building 12F Yeonsan 2-dong, Yeonje-gu, BUSAN 611705 [EMAIL PROTECTED] KOREA ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Factory
> http://soxbox.no-ip.org/radiant/svn/extensions/x_groggy/lib/gr > oggy_filter.rb > > > > It also filters out a bunch of common characters from > people cutting/pasting from word, the key bit is a > page.attachments.each > > This is nice and I would like to try it. Sorry for my dumb > question. > Where exactly should I add this code? I have installed Radiant using > the 'gem'med version. Do I have to get into > sub-directories under /usr/lib/ruby/gems ? No, you'll need to write and install a radiant extension that includes that code. (too busy to go into detail right now - have a look over the extension writing doco on the radiant site). Dan. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard rails plugins not supported in Radiant?
Andrew, i tried your suggestion:
and added the following to environment.rb
config.load_paths << "#{RAILS_ROOT}/vendor/plugins/mypluginname/lib"
and that works!
I see that it is added to the path array properly.
Thanks!
-topher
On Dec 4, 2007 3:01 PM, Christopher Zimmermann <[EMAIL PROTECTED]> wrote:
> Thanks alot for your feedback guys.
>
> My plugin exists in the path:
> myappname\vendor\plugins\myplugin
>
> My environments.rb file looks like:
> # Make sure plugins are loaded from lib and vendor
> config.plugin_paths = [
> "#{RAILS_ROOT}/vendor/plugins",
> "#{RADIANT_ROOT}/lib/plugins",
> "#{RADIANT_ROOT}/vendor/plugins"
> ]
>
> ***
>
> When I trace through the application - I see that my plugins are properly
> added to the Dependencies.load_path array in the initializer.rbload_plugins()
> method.
>
> But Dependencies.load_path gets overwritten here:
> extension_loader.rb discover_extensions() method.
> lines 78-88, actually on the last line... ( initializer.set_autoload_paths
> )
>
> extension_roots.each do |ext_path|
> load_paths = %w(lib app/models app/controllers app/helpers
> test/helpers).collect { |p| "#{ext_path}/#{p}" }
> load_paths << ext_path
> load_paths.each { |p| configuration.load_paths << p; $LOAD_PATH
> << p; }
> configuration.controller_paths << "#{ext_path}/app/controllers"
> configuration.view_paths << "#{ext_path}/app/views"
> @extension_roots << ext_path
> end
> initializer.set_autoload_paths
>
> *
>
> Here is a fix that I have just tried, and seems to work...
> Just in front of the "initializer.set_autoload_paths"
> I added the line:
> configuration.load_paths.concat(Dependencies.load_paths) #CLZ so that
> rails plugins still work??
>
> The set_autoload_paths function basically sets Dependencies.load_paths to
> configuration.load_paths.
>
>
>
> Does this seem sensible? So far it seems to work - but ive just done a bit
> of testing.
>
> ps. same issue on 0.6.3 and 0.6.4
> pps. I did just try putting the plugin inside of an extensions plugin
> directory - and that works just fine. The problem is just when i put it in
> the plugin directory of the main RAILS_ROOT app.
>
> -topher
>
>
>
>
>
>
> On Dec 4, 2007 2:35 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote:
>
> > The original reason is so that Radiant can be run from the gem or
> > vendor/radiant. Notice line 17-22 of config/environment.rb. However,
> > that should not affect plugin paths which are set later on in the file.
> > However, you may be onto something here.
> >
> > Sean
> >
> > Andrew O'Brien wrote:
> > > IIRC correctly, what Chris is describing is the reason I had to
> > > explicitly load the rspec and rspec_on_rails plugins in
> > > config/environments/test.rb. Somewhere along the line (and Chris may
> > > have identified it), the plugin load paths are getting blown away.
> > >
> > > Chris: try adding something like
> > >
> > > config.load_paths << "#{RADIANT_ROOT}/vendor/plugins/rspec/lib"
> > >
> > > (but the path for your plugin) to config/environment.rb in the
> > > Radiant::Initializer block.
> > >
> > > What was the original reason for clearing out the load_paths? Is it
> > > something that should be re-examined?
> > >
> > > -Andrew
> > >
> > > On Dec 4, 2007 4:48 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote:
> > >
> > >> It should be loaded. Are you storing it in
> > RAILS_ROOT/vendor/plugins?
> > >> Have you modified the config.plugin_paths in config/environment.rb?
> > >>
> > >> Sean
> > >>
> > >>
> > >> Christopher Zimmermann wrote:
> > >>
> > >>> Hello,
> > >>> Forgive me if this is a stupid or already covered question - i did
> > search on
> > >>> the radiant site and mailing list, but did not see any conclusive
> > answers.
> > >>>
> > >>> 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
> > radiant/extension_loader.rb
> > >>> discover_extensions()
> > >>>
> > >>> Context:
> > >>> I am trying use a regular rails plugin
> > "acts_as_taggable_on_steroids", and
> > >>> would like to use several others.
> > >>> I dont need to use it as an extension in Radiant - it will be used
> > elsewhere
> > >>> in the same application. (My app mixes Radiant with a rails app
> > through the
> > >>> lovely "radiant_on_rails", "share_layouts, and "record_tags"
> > extensions.)
> > >>> It is probably possible to create an extension that wraps it - but I
> > would
> > >>> prefer not too. It's nicest (and easiest) if I can just load
> > existing rails
> > >>> 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 it's
> > >>> lib directory that cannot be discovered by rails
> > >>> Dependencies.load_missing_constant because the path has been removed
> >
Re: [Radiant] Standard rails plugins not supported in Radiant?
Thanks alot for your feedback guys.
My plugin exists in the path:
myappname\vendor\plugins\myplugin
My environments.rb file looks like:
# Make sure plugins are loaded from lib and vendor
config.plugin_paths = [
"#{RAILS_ROOT}/vendor/plugins",
"#{RADIANT_ROOT}/lib/plugins",
"#{RADIANT_ROOT}/vendor/plugins"
]
***
When I trace through the application - I see that my plugins are properly
added to the Dependencies.load_path array in the
initializer.rbload_plugins() method.
But Dependencies.load_path gets overwritten here:
extension_loader.rb discover_extensions() method.
lines 78-88, actually on the last line... (initializer.set_autoload_paths)
extension_roots.each do |ext_path|
load_paths = %w(lib app/models app/controllers app/helpers
test/helpers).collect { |p| "#{ext_path}/#{p}" }
load_paths << ext_path
load_paths.each { |p| configuration.load_paths << p; $LOAD_PATH <<
p; }
configuration.controller_paths << "#{ext_path}/app/controllers"
configuration.view_paths << "#{ext_path}/app/views"
@extension_roots << ext_path
end
initializer.set_autoload_paths
*
Here is a fix that I have just tried, and seems to work...
Just in front of the "initializer.set_autoload_paths"
I added the line:
configuration.load_paths.concat(Dependencies.load_paths) #CLZ so that rails
plugins still work??
The set_autoload_paths function basically sets Dependencies.load_paths to
configuration.load_paths.
Does this seem sensible? So far it seems to work - but ive just done a bit
of testing.
ps. same issue on 0.6.3 and 0.6.4
pps. I did just try putting the plugin inside of an extensions plugin
directory - and that works just fine. The problem is just when i put it in
the plugin directory of the main RAILS_ROOT app.
-topher
On Dec 4, 2007 2:35 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote:
> The original reason is so that Radiant can be run from the gem or
> vendor/radiant. Notice line 17-22 of config/environment.rb. However,
> that should not affect plugin paths which are set later on in the file.
> However, you may be onto something here.
>
> Sean
>
> Andrew O'Brien wrote:
> > IIRC correctly, what Chris is describing is the reason I had to
> > explicitly load the rspec and rspec_on_rails plugins in
> > config/environments/test.rb. Somewhere along the line (and Chris may
> > have identified it), the plugin load paths are getting blown away.
> >
> > Chris: try adding something like
> >
> > config.load_paths << "#{RADIANT_ROOT}/vendor/plugins/rspec/lib"
> >
> > (but the path for your plugin) to config/environment.rb in the
> > Radiant::Initializer block.
> >
> > What was the original reason for clearing out the load_paths? Is it
> > something that should be re-examined?
> >
> > -Andrew
> >
> > On Dec 4, 2007 4:48 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote:
> >
> >> It should be loaded. Are you storing it in RAILS_ROOT/vendor/plugins?
> >> Have you modified the config.plugin_paths in config/environment.rb?
> >>
> >> Sean
> >>
> >>
> >> Christopher Zimmermann wrote:
> >>
> >>> Hello,
> >>> Forgive me if this is a stupid or already covered question - i did
> search on
> >>> the radiant site and mailing list, but did not see any conclusive
> answers.
> >>>
> >>> 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
> radiant/extension_loader.rb
> >>> discover_extensions()
> >>>
> >>> Context:
> >>> I am trying use a regular rails plugin "acts_as_taggable_on_steroids",
> and
> >>> would like to use several others.
> >>> I dont need to use it as an extension in Radiant - it will be used
> elsewhere
> >>> in the same application. (My app mixes Radiant with a rails app
> through the
> >>> lovely "radiant_on_rails", "share_layouts, and "record_tags"
> extensions.)
> >>> It is probably possible to create an extension that wraps it - but I
> would
> >>> prefer not too. It's nicest (and easiest) if I can just load existing
> rails
> >>> 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 it's
> >>> lib directory that cannot be discovered by rails
> >>> Dependencies.load_missing_constant because the path has been removed
> from
> >>> the Dependencies.load_paths array by Radiant.
> >>>
> >>> So when I try to use this Plugin I get a
> >>> "
> >>> NameError in TesterController#tagtest
> >>>
> >>> Uninitialized constant
> >>> ActiveRecord::Acts::Taggable::InstanceMethods::TagList
> >>> "
> >>>
> >>> Questions:
> >>> So, are plugins basically not supported in Radiant?
> >>> Is there a reason for that... and is there a reason for totally
> overwritting
> >>> the Dependencies.load_paths array? Or is this something that could be
> >>> changed, for example that radiant/extension_loader.rb
> d
[Radiant] script/generate extension_migration ?
Does Radiant support the "script/generate extension_migration" command or some variant to help create extension migrations, or do we roll our own? Thanks, - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard rails plugins not supported in Radiant?
The original reason is so that Radiant can be run from the gem or
vendor/radiant. Notice line 17-22 of config/environment.rb. However,
that should not affect plugin paths which are set later on in the file.
However, you may be onto something here.
Sean
Andrew O'Brien wrote:
> IIRC correctly, what Chris is describing is the reason I had to
> explicitly load the rspec and rspec_on_rails plugins in
> config/environments/test.rb. Somewhere along the line (and Chris may
> have identified it), the plugin load paths are getting blown away.
>
> Chris: try adding something like
>
> config.load_paths << "#{RADIANT_ROOT}/vendor/plugins/rspec/lib"
>
> (but the path for your plugin) to config/environment.rb in the
> Radiant::Initializer block.
>
> What was the original reason for clearing out the load_paths? Is it
> something that should be re-examined?
>
> -Andrew
>
> On Dec 4, 2007 4:48 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote:
>
>> It should be loaded. Are you storing it in RAILS_ROOT/vendor/plugins?
>> Have you modified the config.plugin_paths in config/environment.rb?
>>
>> Sean
>>
>>
>> Christopher Zimmermann wrote:
>>
>>> Hello,
>>> Forgive me if this is a stupid or already covered question - i did search on
>>> the radiant site and mailing list, but did not see any conclusive answers.
>>>
>>> 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 radiant/extension_loader.rb
>>> discover_extensions()
>>>
>>> Context:
>>> I am trying use a regular rails plugin "acts_as_taggable_on_steroids", and
>>> would like to use several others.
>>> I dont need to use it as an extension in Radiant - it will be used elsewhere
>>> in the same application. (My app mixes Radiant with a rails app through the
>>> lovely "radiant_on_rails", "share_layouts, and "record_tags" extensions.)
>>> It is probably possible to create an extension that wraps it - but I would
>>> prefer not too. It's nicest (and easiest) if I can just load existing rails
>>> 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 it's
>>> lib directory that cannot be discovered by rails
>>> Dependencies.load_missing_constant because the path has been removed from
>>> the Dependencies.load_paths array by Radiant.
>>>
>>> So when I try to use this Plugin I get a
>>> "
>>> NameError in TesterController#tagtest
>>>
>>> Uninitialized constant
>>> ActiveRecord::Acts::Taggable::InstanceMethods::TagList
>>> "
>>>
>>> Questions:
>>> So, are plugins basically not supported in Radiant?
>>> Is there a reason for that... and is there a reason for totally overwritting
>>> the Dependencies.load_paths array? Or is this something that could be
>>> changed, for example that radiant/extension_loader.rb discover_extensions()
>>> appends the paths to load_paths instead of overwriting it?
>>>
>>>
>>> Thanks for any insight into this!!!
>>> cheers, topher
>>>
>>>
>>>
>>>
>> ___
>> Radiant mailing list
>> Post: Radiant@lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>>
> ___
> Radiant mailing list
> Post: Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
>
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard rails plugins not supported in Radiant?
IIRC correctly, what Chris is describing is the reason I had to
explicitly load the rspec and rspec_on_rails plugins in
config/environments/test.rb. Somewhere along the line (and Chris may
have identified it), the plugin load paths are getting blown away.
Chris: try adding something like
config.load_paths << "#{RADIANT_ROOT}/vendor/plugins/rspec/lib"
(but the path for your plugin) to config/environment.rb in the
Radiant::Initializer block.
What was the original reason for clearing out the load_paths? Is it
something that should be re-examined?
-Andrew
On Dec 4, 2007 4:48 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote:
> It should be loaded. Are you storing it in RAILS_ROOT/vendor/plugins?
> Have you modified the config.plugin_paths in config/environment.rb?
>
> Sean
>
>
> Christopher Zimmermann wrote:
> > Hello,
> > Forgive me if this is a stupid or already covered question - i did search on
> > the radiant site and mailing list, but did not see any conclusive answers.
> >
> > 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 radiant/extension_loader.rb
> > discover_extensions()
> >
> > Context:
> > I am trying use a regular rails plugin "acts_as_taggable_on_steroids", and
> > would like to use several others.
> > I dont need to use it as an extension in Radiant - it will be used elsewhere
> > in the same application. (My app mixes Radiant with a rails app through the
> > lovely "radiant_on_rails", "share_layouts, and "record_tags" extensions.)
> > It is probably possible to create an extension that wraps it - but I would
> > prefer not too. It's nicest (and easiest) if I can just load existing rails
> > 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 it's
> > lib directory that cannot be discovered by rails
> > Dependencies.load_missing_constant because the path has been removed from
> > the Dependencies.load_paths array by Radiant.
> >
> > So when I try to use this Plugin I get a
> > "
> > NameError in TesterController#tagtest
> >
> > Uninitialized constant
> > ActiveRecord::Acts::Taggable::InstanceMethods::TagList
> > "
> >
> > Questions:
> > So, are plugins basically not supported in Radiant?
> > Is there a reason for that... and is there a reason for totally overwritting
> > the Dependencies.load_paths array? Or is this something that could be
> > changed, for example that radiant/extension_loader.rb discover_extensions()
> > appends the paths to load_paths instead of overwriting it?
> >
> >
> > Thanks for any insight into this!!!
> > cheers, topher
> >
> >
> >
>
>
> ___
> Radiant mailing list
> Post: Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard rails plugins not supported in Radiant?
It should be loaded. Are you storing it in RAILS_ROOT/vendor/plugins? Have you modified the config.plugin_paths in config/environment.rb? Sean Christopher Zimmermann wrote: > Hello, > Forgive me if this is a stupid or already covered question - i did search on > the radiant site and mailing list, but did not see any conclusive answers. > > 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 radiant/extension_loader.rb > discover_extensions() > > Context: > I am trying use a regular rails plugin "acts_as_taggable_on_steroids", and > would like to use several others. > I dont need to use it as an extension in Radiant - it will be used elsewhere > in the same application. (My app mixes Radiant with a rails app through the > lovely "radiant_on_rails", "share_layouts, and "record_tags" extensions.) > It is probably possible to create an extension that wraps it - but I would > prefer not too. It's nicest (and easiest) if I can just load existing rails > 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 it's > lib directory that cannot be discovered by rails > Dependencies.load_missing_constant because the path has been removed from > the Dependencies.load_paths array by Radiant. > > So when I try to use this Plugin I get a > " > NameError in TesterController#tagtest > > Uninitialized constant > ActiveRecord::Acts::Taggable::InstanceMethods::TagList > " > > Questions: > So, are plugins basically not supported in Radiant? > Is there a reason for that... and is there a reason for totally overwritting > the Dependencies.load_paths array? Or is this something that could be > changed, for example that radiant/extension_loader.rb discover_extensions() > appends the paths to load_paths instead of overwriting it? > > > Thanks for any insight into this!!! > cheers, topher > > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Standard rails plugins not supported in Radiant?
Hello, Forgive me if this is a stupid or already covered question - i did search on the radiant site and mailing list, but did not see any conclusive answers. 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 radiant/extension_loader.rb discover_extensions() Context: I am trying use a regular rails plugin "acts_as_taggable_on_steroids", and would like to use several others. I dont need to use it as an extension in Radiant - it will be used elsewhere in the same application. (My app mixes Radiant with a rails app through the lovely "radiant_on_rails", "share_layouts, and "record_tags" extensions.) It is probably possible to create an extension that wraps it - but I would prefer not too. It's nicest (and easiest) if I can just load existing rails 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 it's lib directory that cannot be discovered by rails Dependencies.load_missing_constant because the path has been removed from the Dependencies.load_paths array by Radiant. So when I try to use this Plugin I get a " NameError in TesterController#tagtest Uninitialized constant ActiveRecord::Acts::Taggable::InstanceMethods::TagList " Questions: So, are plugins basically not supported in Radiant? Is there a reason for that... and is there a reason for totally overwritting the Dependencies.load_paths array? Or is this something that could be changed, for example that radiant/extension_loader.rb discover_extensions() appends the paths to load_paths instead of overwriting it? Thanks for any insight into this!!! cheers, topher -- Christopher Zimmermann [EMAIL PROTECTED] 604-484-9279 ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] One more page launched on Radiant CMS! :)
On Dec 4, 2007, at 2:44 AM, Tõnu Runnel wrote: > I tried to leave all html code in the layout and snippets. So I gave > the > girls the pages tab where they entered all the content themselves (I > only > made some small examples). They had to use only textile + some few > snippets > and it was surprisingly easy and understandable for them -- without > any > knowledge of anything beyond office, browsers etc. So I guess in > most cases > there is no need for wysiwyg. And -- Word tables are more complex than > > | this | is | > | a | table | So true! With a little training most people can grok basic HTML or Textile. So if you have time to invest in your people you will be much better off than resorting a clunky wysiwyg. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] One more page launched on Radiant CMS! :)
Nice and simple design, congrats! You said that your non-tech customers edit the pages themselves. How are you managing the images? With an extension? /AITOR On Dec 4, 2007 8:44 AM, Tõnu Runnel <[EMAIL PROTECTED]> wrote: > I tried to leave all html code in the layout and snippets. So I gave the > girls the pages tab where they entered all the content themselves (I only > made some small examples). They had to use only textile + some few > snippets > and it was surprisingly easy and understandable for them -- without any > knowledge of anything beyond office, browsers etc. So I guess in most > cases > there is no need for wysiwyg. And -- Word tables are more complex than > > | this | is | > | a | table | > > :) > > Tõnu > > 2007/12/4, Mark Gallop <[EMAIL PROTECTED]>: > > > Did you enter the content yourself in Textile? I would like my users to > > enter content with Textile but I think they will be very reluctant. The > > most technical they have ever got is creating a table in Word. > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Difficulties with a navigation menu and selectively showing children
Lou Brothers wrote: > I want to display all of the children of the parent page, and then > display the children of the current page only. In this example, Child > Page 2 has children, but I am not showing them. > I haven't tried it but this might work (or something like this): <-- switch the context to the parent of this page <-- for each child (of the page's parent) <-- sorry, I can't remember how to match this <--- for each child of this page <-- or whatever you want to do Maybe, these will help: 1. http://lists.radiantcms.org/pipermail/radiant/2006-July/000888.html 2. http://www.ruby-forum.com/topic/125811 Based on #1 above, you may need to match using: because that works at the level of the current page, not the level of the current context (which in a nested scheme will be the child/ parent page). Hope this helps. Cheers, Mohit. 12/5/2007 | 12:14 AM. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Difficulties with a navigation menu and selectively showing children
Hi. I recently started using Radiant to host http://www.vfct.com/ . I'm not using many of the more sophisticated features (nearly everything is hard-coded in some way). I'd like to get away from having to hard-code my sidebar navigation (see http://www.vfct.com/counterterrorism/odin-uldris/ for a good example of what I'm doing. Example: Counterterrorism Child Page 1 Child of Child Page 1 Child Page 2 I want to display all of the children of the parent page, and then display the children of the current page only. In this example, Child Page 2 has children, but I am not showing them. I've gotten close using But then I get all second level children including those under Child Page 2. I attempted to use ... but it looks like isn't executing or at least isn't matching (it does work if I type the url in manually instead of using the tag). An attempt to do this with r:navigation, feeding it the results of r:children:each failed as well, as r:children:each didn't seem to execute within http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] One more page launched on Radiant CMS! :)
> Are you using mongrel or fastcgi? How many instances in your > cluster? Try reducing the number of mongrel instances /fastcgi > processes. Most of my Radiant sites only require one Mongrel process. Typically, with a shared host you won't have enough memory available to run more than one. On Dec 3, 2007, at 6:55 PM, Daniel Sheppard wrote: > >> (I managed to build everything while being a designer not a >> programmer. So >> it really works, even without proper guidance. The only thing >> that is over >> my head is that on Mediatemple Radiant dies out after every >> 3-4 hours -- it > > Most likely cause is that you've got more processes running than > your shared hosting can handle. > > Are you using mongrel or fastcgi? How many instances in your > cluster? Try reducing the number of mongrel instances / fastcgi > processes. > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Factory
Dan, > > o It would be nice to have a convenient way to access > >images through the Admin interface and to easily > >(less typing, yet intuitive) 'markup' the images in > >the associated pages. > > On my site, I've written my own text filter that replaces textile > image references with links to the image, so that: > > !image.jpg! > > would get replaced with > > !/attachments/monkey.jpg! > > before getting handed off to textile for regular processing. > > Look at: > > http://soxbox.no-ip.org/radiant/svn/extensions/x_groggy/lib/groggy_filter.rb > > It also filters out a bunch of common characters from people cutting/pasting > from word, the key bit is a page.attachments.each This is nice and I would like to try it. Sorry for my dumb question. Where exactly should I add this code? I have installed Radiant using the 'gem'med version. Do I have to get into sub-directories under /usr/lib/ruby/gems ? saji -- Saji N. Hameed APEC Climate Center +82 51 668 7470 National Pension Corporation Busan Building 12F Yeonsan 2-dong, Yeonje-gu, BUSAN 611705 [EMAIL PROTECTED] KOREA ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
