[Radiant] Mailer extension not working, but doesn't give much clues why not
Hi!
I've been spending half night and half day trying to figure out why my
mailer extension isn't working properly. When I hosted the site at a
Dreamhost PS (using passenger) everything worked just fine. Now when
hosting on a Ubuntu Hardy server running Ruby Enterprise Edition +
passenger it just redirects from the form at http://xhtml.fi/contact
to http://xhtml.fi/pages/12/mail#mailer, no mail is being sent and the
production.log says:
Processing MailController#create (for 85.134.8.172 at 2009-10-15
15:06:39) [POST]
Session ID:
BAh7BiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo
SGFzaHsABjoKQHVzZWR7AA==--fa092d73a8aac022a2e6f97c79ffacf9ac27df32
Parameters: {page_id=12, action=create, mailer=
{message=Test message, name=Simon, email=si...@iki.fi},
controller=mail}
Sent mail to i...@xhtml.fi
Completed in 0.19994 (5 reqs/sec) | Rendering: 0.00032 (0%) | DB:
0.00402 (2%) | 200 OK [http://xhtml.fi/pages/12/mail]
I've tried different smtp-settings in environment.rb primarily:
ActionMailer::Base.smtp_settings = {
:address = smtp.MY-HOSTING-COMPANY
}
...at Dreamhost it worked without that setting deafulting to localhost
I guess.
You are free to test at http://xhtml.fi/contact and compare to how it
works at http://old.xhtml.fi/contact when hosted at Dreamhost.
Might there be some gem that I'm missing? Otherwise I don't know what
I might be missing, since I'm using Radiant 0.7.1 checked out right
from the repo (with Rails in vendor). I'm using these extensions:
archive enkoder_tags multi_sitetextile_filter
archive_page_order mailer page_attachments
drag_order markdown_filter textile_editor
(Multi site is this version, that hides other sites than their own
from normal users. http://github.com/sniemela/radiant-multi-site-extension
) Anyways... all of this works on Dreamhost. One funny thing though
is that sometime the http://xhtml.fi/pages/12/mail#mailer page throws
in some content from another of my multi_site sites.
And here's a list of the gems that I've got installed at the new server:
actionmailer (2.3.4, 2.3.3, 2.3.2)
actionpack (2.3.4, 2.3.3, 2.3.2)
activerecord (2.3.4, 2.3.3, 2.3.2)
activeresource (2.3.4, 2.3.3, 2.3.2)
activesupport (2.3.4, 2.3.3, 2.3.2)
fastthread (1.0.7)
mysql (2.7)
passenger (2.2.5)
postgres (0.7.9.2008.01.28)
rack (1.0.0)
radiant (0.8.1, 0.8.0, 0.7.1)
rails (2.3.4, 2.3.3, 2.3.2)
rake (0.8.7, 0.8.4)
RedCloth (4.2.2, 4.1.9)
rmagick (2.11.0, 2.10.0)
rspec (1.2.9, 1.2.8, 1.2.6)
rspec-rails (1.2.7.1, 1.2.6)
rubygems-update (1.3.5)
sqlite3-ruby (1.2.5, 1.2.4)
Just let me know if you want me to provide any more info, since I'm
pretty clueless and don't really know what hints could be useful. Any
help is very much appreciated!
cheers, Simon
PS. I tried using just the mail-function in php and that didn't get
the mail delivered either (that is without using any other smtp-server).
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mailer extension not working, but doesn't give much clues why not
Hi!
Thanks for your answer!
Configuring postfix on the Ubuntu machine would of course be an option.
But what I'm trying to do is to use a smtp-server that does not
require autentication when contacted from it's local network.
cheers, Simon
On Oct 15, 2009, at 23:26 , qutic development wrote:
Do you send the mail directly with the Ubuntu machine? Is postfix or
whatever you use running?
If you try to deliver the mail not over the Ubuntu machine, you need
to specify an account (to prevent an open relay...):
ActionMailer::Base.smtp_settings = {
:address= my.mailserver.com,
:domain = example.com,
:port = 25,
:authentication = :plain, # or whatever you need
:user_name = my.usern...@example.com,
:password = abcdefg
}
jerry
On 15.10.2009, at 14:36, Simon Rönnqvist wrote:
Hi!
I've been spending half night and half day trying to figure out why
my mailer extension isn't working properly. When I hosted the site
at a Dreamhost PS (using passenger) everything worked just fine.
Now when hosting on a Ubuntu Hardy server running Ruby Enterprise
Edition + passenger it just redirects from the form at http://xhtml.fi/contact
to http://xhtml.fi/pages/12/mail#mailer, no mail is being sent and
the production.log says:
Processing MailController#create (for 85.134.8.172 at 2009-10-15
15:06:39) [POST]
Session ID:
BAh7BiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo
SGFzaHsABjoKQHVzZWR7AA==--fa092d73a8aac022a2e6f97c79ffacf9ac27df32
Parameters: {page_id=12, action=create, mailer=
{message=Test message, name=Simon,
email=si...@iki.fi}, controller=mail}
Sent mail to i...@xhtml.fi
Completed in 0.19994 (5 reqs/sec) | Rendering: 0.00032 (0%) | DB:
0.00402 (2%) | 200 OK [http://xhtml.fi/pages/12/mail]
I've tried different smtp-settings in environment.rb primarily:
ActionMailer::Base.smtp_settings = {
:address = smtp.MY-HOSTING-COMPANY
}
...at Dreamhost it worked without that setting deafulting to
localhost I guess.
You are free to test at http://xhtml.fi/contact and compare to how
it works at http://old.xhtml.fi/contact when hosted at Dreamhost.
Might there be some gem that I'm missing? Otherwise I don't know
what I might be missing, since I'm using Radiant 0.7.1 checked out
right from the repo (with Rails in vendor). I'm using these
extensions:
archive enkoder_tags multi_sitetextile_filter
archive_page_order mailer page_attachments
drag_order markdown_filter textile_editor
(Multi site is this version, that hides other sites than their own
from normal users. http://github.com/sniemela/radiant-multi-site-extension
) Anyways... all of this works on Dreamhost. One funny thing
though is that sometime the http://xhtml.fi/pages/12/mail#mailer
page throws in some content from another of my multi_site sites.
And here's a list of the gems that I've got installed at the new
server:
actionmailer (2.3.4, 2.3.3, 2.3.2)
actionpack (2.3.4, 2.3.3, 2.3.2)
activerecord (2.3.4, 2.3.3, 2.3.2)
activeresource (2.3.4, 2.3.3, 2.3.2)
activesupport (2.3.4, 2.3.3, 2.3.2)
fastthread (1.0.7)
mysql (2.7)
passenger (2.2.5)
postgres (0.7.9.2008.01.28)
rack (1.0.0)
radiant (0.8.1, 0.8.0, 0.7.1)
rails (2.3.4, 2.3.3, 2.3.2)
rake (0.8.7, 0.8.4)
RedCloth (4.2.2, 4.1.9)
rmagick (2.11.0, 2.10.0)
rspec (1.2.9, 1.2.8, 1.2.6)
rspec-rails (1.2.7.1, 1.2.6)
rubygems-update (1.3.5)
sqlite3-ruby (1.2.5, 1.2.4)
Just let me know if you want me to provide any more info, since I'm
pretty clueless and don't really know what hints could be useful.
Any help is very much appreciated!
cheers, Simon
PS. I tried using just the mail-function in php and that didn't get
the mail delivered either (that is without using any other smtp-
server).
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant 0.8.0 Asterism Release
OK, I'll check it out when I have time... I'll try and take care of Swedish (my mother's thongue) and Finnish (which I know fluently), possibly with help from one or a couple of my friends who have Finnish as their mother's thongue. cheers, Simon On Jun 16, 2009, at 15:50 , Sean Cribbs wrote: FYI, the major features I have planned for 0.9 are thus: * John's new blade UI * i18n/l10n/etc Both of these are going on in branches, although I'm afraid portions of Keith's work will be dependent on the new UI. If you've contributed a translation, please be aware that we may call on your services again in the near future to adjust for the UI changes. Cheers, Sean Keith Bingman wrote: Working on it: http://github.com/kbingman/radiant/tree/master I will be moving this to the official i18n branch ASAP, but I have been pretty busy lately. It is mostly done, we have the views translated for German, Russian, French and Japanese. Any help is appreciated. Keith On Jun 16, 2009, at 8:58 AM, Simon Rönnqvist wrote: Hi! Now since we're in Rails 2.3.2, would it then be time to localize Radiant? The first step towards this would of course be to move all strings from the views into config/locales/en.yml. If I or someone at some point (when I or someone has time) would make a fork in order to apply this change, would you then accept a pull request for those changes? cheers, Simon On Jun 14, 2009, at 22:40 , Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.8.0 Asterism features a brand new and more compliant caching mechanism based on Rack::Cache, and numerous bugfixes and small enhancements. Also included are: * An extensive integration suite using Cucumber and Webrat * Rails 2.3.2 (previously 2.1.2) * Highline 1.5.1 * Haml 2.0.9 Many thanks to our contributors and committers for their contributions. WHAT IS RADIANT CMS? Radiant is a no-fluff content management system made for designers and programmers and is ideal for use on small teams. It is similar to Movable Type or Textpattern, but is much more than a blogging engine. Radiant features: * An elegant user interface * The ability to arrange pages in a hierarchy * Flexible templating with layouts, snippets, page parts, and a custom tagging language (Radius: http://radius.rubyforge.org) * A dynamic extension system * A simple user management/permissions system * Support for Markdown and Textile as well as traditional HTML (it's easy to create other filters) * Operates in two modes: dev and production depending on the URL * A caching system which expires pages every 5 minutes * Built using Ruby on Rails (which means that extending Radiant is as easy as any other Rails application) * Licensed under the MIT-License * And much more... There's even a live demo over on the project Web site: http://radiantcms.org/demo/ WHAT'S NEW IN THIS RELEASE? * Warn about using the RedCloth 3 fallback. [Sean Cribbs, Jason Garber] * Prevent stty errors on JRuby while running bootstrap. [Sean Cribbs] * Moved template_name to ApplicationController [Jim Gay, Michael Kessler] * Remove vizres plugin. [Sean Cribbs] * Update instance config/environments to remove ResponseCache [Jim Gay] * Remove :order option from r:children:count /, which causes errors on postgresql. [Sean Cribbs] * Prevent recursion via the r:content / tag. [Sean Cribbs] * Update Highline. [Sean Cribbs] * Update Cucumber and RSpec, clean up some features and fix specs. [Sean Cribbs] * Set the protected attributes for users in User.protected_attributes [Jim Gay] * Don't allow a nil ETag in SiteController. [David Cato] * Prevent failed login message from sticking around. [Kunal Shah] * Fix failing test regarding extension order. [Brett McHargue] * Catch ActiveRecord::RecordNotFound in Admin::ResourceController [Jim Gay] * Catch missing template errors for show routes [Jim Gay] * Fix with_error in render_matcher not causing the spec to fail when no exception raised. [Jason Garber] * Make features task run in instance mode. [Sean Cribbs] * Remove Admin::AbstractModelController. [Sean Cribbs] * Cleanup deprecated Gem::manage_gems. [Sean Cribbs] * Add begin...rescue blocks to rspec.rake [Sean Cribbs] * Add begin...rescue blocks for requiring cucumber. [Matt Henry] * Deprecate ResponseCache, add Radiant::Cache based on Rack::Cache. [Sean Cribbs] * Use app name for session cookie. [Josh French] * Upgrade to Rails 2.3.2. [Sean Cribbs, Rick DeNatale, Josh French, Kunal Shah] * Populate config.extensions so extensions can be disabled easily. [Jason Garber] * Convert integration specs to Cucumber stories and update RSpec. [Sean Cribbs] * Use ActionView::PathSet instead of normal arrays for view paths. [Pat Allan] * Don't raise exception on unauthenticated request to /admin/ logout. [Josh French] * Reverse view paths order in extension loader. [Sean Cribbs, Brent Kroeker
Re: [Radiant] Radiant 0.8.0 Asterism Release
Yes, this sounds like a good idea... I don't think sending patches separately would make sense in this case. cheers, Simon On Jun 17, 2009, at 11:55 , kranthi reddy wrote: creating a different fork for a few files dint seem to be a very good idea to me. Currently I have cloned Keith's repository and created a local branch for my work.Once I'm done and I have tested the instance on this local branch I will diff the this branch with master and make a patch file out of it. I was planning to E-mail this patch to Keith. Incase Keith would be okay to create a remote branch on his repository for these translation files I guess we can push these files to that remote branch from where keith can merge them into master. What do you think? 2009/6/17 Simon Rönnqvist si...@iki.fi That's OK, I wasn't going to take Spanish anyways only Swedish and Finnish. :) BTW. How would you prefer that we do the contribution... by forking the project and doing pull requests (only for one file, or two in my case)? Or should we just mail someone the file when it's done, or do you have any other suggestion? Of course keeping the action within GitHub would be great, in order to track what different people do. cheers, Simon On Jun 17, 2009, at 09:37 , kranthi reddy wrote: Hey.. I want to take up spanish first. Thank you, kranthi 2009/6/17 Simon Rönnqvist si...@iki.fi OK, I'll check it out when I have time... I'll try and take care of Swedish (my mother's thongue) and Finnish (which I know fluently), possibly with help from one or a couple of my friends who have Finnish as their mother's thongue. cheers, Simon On Jun 16, 2009, at 15:50 , Sean Cribbs wrote: FYI, the major features I have planned for 0.9 are thus: * John's new blade UI * i18n/l10n/etc Both of these are going on in branches, although I'm afraid portions of Keith's work will be dependent on the new UI. If you've contributed a translation, please be aware that we may call on your services again in the near future to adjust for the UI changes. Cheers, Sean Keith Bingman wrote: Working on it: http://github.com/kbingman/radiant/tree/master I will be moving this to the official i18n branch ASAP, but I have been pretty busy lately. It is mostly done, we have the views translated for German, Russian, French and Japanese. Any help is appreciated. Keith On Jun 16, 2009, at 8:58 AM, Simon Rönnqvist wrote: Hi! Now since we're in Rails 2.3.2, would it then be time to localize Radiant? The first step towards this would of course be to move all strings from the views into config/locales/en.yml. If I or someone at some point (when I or someone has time) would make a fork in order to apply this change, would you then accept a pull request for those changes? cheers, Simon On Jun 14, 2009, at 22:40 , Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.8.0 Asterism features a brand new and more compliant caching mechanism based on Rack::Cache, and numerous bugfixes and small enhancements. Also included are: * An extensive integration suite using Cucumber and Webrat * Rails 2.3.2 (previously 2.1.2) * Highline 1.5.1 * Haml 2.0.9 Many thanks to our contributors and committers for their contributions. WHAT IS RADIANT CMS? Radiant is a no-fluff content management system made for designers and programmers and is ideal for use on small teams. It is similar to Movable Type or Textpattern, but is much more than a blogging engine. Radiant features: * An elegant user interface * The ability to arrange pages in a hierarchy * Flexible templating with layouts, snippets, page parts, and a custom tagging language (Radius: http://radius.rubyforge.org) * A dynamic extension system * A simple user management/permissions system * Support for Markdown and Textile as well as traditional HTML (it's easy to create other filters) * Operates in two modes: dev and production depending on the URL * A caching system which expires pages every 5 minutes * Built using Ruby on Rails (which means that extending Radiant is as easy as any other Rails application) * Licensed under the MIT-License * And much more... There's even a live demo over on the project Web site: http://radiantcms.org/demo/ WHAT'S NEW IN THIS RELEASE? * Warn about using the RedCloth 3 fallback. [Sean Cribbs, Jason Garber] * Prevent stty errors on JRuby while running bootstrap. [Sean Cribbs] * Moved template_name to ApplicationController [Jim Gay, Michael Kessler] * Remove vizres plugin. [Sean Cribbs] * Update instance config/environments to remove ResponseCache [Jim Gay] * Remove :order option from r:children:count /, which causes errors on postgresql. [Sean Cribbs] * Prevent recursion via the r:content / tag. [Sean Cribbs] * Update Highline. [Sean Cribbs] * Update Cucumber and RSpec, clean up some features and fix specs. [Sean Cribbs] * Set
Re: [Radiant] Radiant 0.8.0 Asterism Release
Hi! Now since we're in Rails 2.3.2, would it then be time to localize Radiant? The first step towards this would of course be to move all strings from the views into config/locales/en.yml. If I or someone at some point (when I or someone has time) would make a fork in order to apply this change, would you then accept a pull request for those changes? cheers, Simon On Jun 14, 2009, at 22:40 , Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.8.0 Asterism features a brand new and more compliant caching mechanism based on Rack::Cache, and numerous bugfixes and small enhancements. Also included are: * An extensive integration suite using Cucumber and Webrat * Rails 2.3.2 (previously 2.1.2) * Highline 1.5.1 * Haml 2.0.9 Many thanks to our contributors and committers for their contributions. WHAT IS RADIANT CMS? Radiant is a no-fluff content management system made for designers and programmers and is ideal for use on small teams. It is similar to Movable Type or Textpattern, but is much more than a blogging engine. Radiant features: * An elegant user interface * The ability to arrange pages in a hierarchy * Flexible templating with layouts, snippets, page parts, and a custom tagging language (Radius: http://radius.rubyforge.org) * A dynamic extension system * A simple user management/permissions system * Support for Markdown and Textile as well as traditional HTML (it's easy to create other filters) * Operates in two modes: dev and production depending on the URL * A caching system which expires pages every 5 minutes * Built using Ruby on Rails (which means that extending Radiant is as easy as any other Rails application) * Licensed under the MIT-License * And much more... There's even a live demo over on the project Web site: http://radiantcms.org/demo/ WHAT'S NEW IN THIS RELEASE? * Warn about using the RedCloth 3 fallback. [Sean Cribbs, Jason Garber] * Prevent stty errors on JRuby while running bootstrap. [Sean Cribbs] * Moved template_name to ApplicationController [Jim Gay, Michael Kessler] * Remove vizres plugin. [Sean Cribbs] * Update instance config/environments to remove ResponseCache [Jim Gay] * Remove :order option from r:children:count /, which causes errors on postgresql. [Sean Cribbs] * Prevent recursion via the r:content / tag. [Sean Cribbs] * Update Highline. [Sean Cribbs] * Update Cucumber and RSpec, clean up some features and fix specs. [Sean Cribbs] * Set the protected attributes for users in User.protected_attributes [Jim Gay] * Don't allow a nil ETag in SiteController. [David Cato] * Prevent failed login message from sticking around. [Kunal Shah] * Fix failing test regarding extension order. [Brett McHargue] * Catch ActiveRecord::RecordNotFound in Admin::ResourceController [Jim Gay] * Catch missing template errors for show routes [Jim Gay] * Fix with_error in render_matcher not causing the spec to fail when no exception raised. [Jason Garber] * Make features task run in instance mode. [Sean Cribbs] * Remove Admin::AbstractModelController. [Sean Cribbs] * Cleanup deprecated Gem::manage_gems. [Sean Cribbs] * Add begin...rescue blocks to rspec.rake [Sean Cribbs] * Add begin...rescue blocks for requiring cucumber. [Matt Henry] * Deprecate ResponseCache, add Radiant::Cache based on Rack::Cache. [Sean Cribbs] * Use app name for session cookie. [Josh French] * Upgrade to Rails 2.3.2. [Sean Cribbs, Rick DeNatale, Josh French, Kunal Shah] * Populate config.extensions so extensions can be disabled easily. [Jason Garber] * Convert integration specs to Cucumber stories and update RSpec. [Sean Cribbs] * Use ActionView::PathSet instead of normal arrays for view paths. [Pat Allan] * Don't raise exception on unauthenticated request to /admin/logout. [Josh French] * Reverse view paths order in extension loader. [Sean Cribbs, Brent Kroeker] * Remove obviated Ruby 1.8.7 compatibility patch. [Sean Cribbs] * Adjust StandardTags#relative_url_for for case when relative_url_root is nil. [Sean Cribbs] * Correct rendering error in extensions controller. [Sean Cribbs] * Correct typo in config/boot.rb. [Sean Cribbs] * Major refactoring and simplification of LoginSystem. [Sean Cribbs] * Update Haml to 2.0.7. [Sean Cribbs] * Upgrade to Rails 2.2.2. [Sean Cribbs] * Cleanup the config class a little, add some more documentation. [Sean Cribbs] * Avoid bootstrap errors related to Radiant::Config by checking for table existence. [Sean Cribbs] * Correct status code typo in Admin::ResourceController. [Sean Cribbs] INSTALLATION We've worked hard to make it easy to install Radiant. For starters you can download it with Ruby Gems: % gem install radiant Once the Radiant gem is installed you have access to the `radiant` command. The `radiant` command is similar to the `rails` command (if you are from the Rails world. It's how you generate a new Radiant project for a
Re: [Radiant] Volunteers Needed! Radiant Wiki Migration
Hi! Are we really 100% sure that we want to keep the project forever at GitHub? I mean not so long ago SVN was the standard for Rails projects, now Git is in five years something else might be. And even though we'd stick to using Git are we sure that we want to host our things at GitHub forever? I'm not holding anything against this move, I just thought that other options should be considered too... since we don't want to make this wiki move very often. cheers, Simon On Apr 7, 2009, at 19:58 , John W. Long wrote: Hello Radiant Users, The software that we are using to run the Radiant Wiki seems to constantly have problems. We've decided that it would be better to move to another solution. Right now we are looking at just putting the content in the GitHub project. Every project on GitHub has a wiki so this seems like the ideal solution. Would anyone have time to volunteer to help make this happen? The import could actually be broken down into two parts done by two separate people, or by the same person. 1. Crawling the current wiki (http://wiki.radiantcms.org) and grabing the Textile content for each of the pages. Shoving it into text files with the page name in them (e.g. Using Radiant.textile). You can get a list of all pages here: http://wiki.radiantcms.org/all/list Access the edit action for a page to get at the page content: http://wiki.radiantcms.org/Accessing_Radiants_User_Model/1/edit 2. Taking the content from the text files, munging the content for GitHub, and creating wiki pages on GitHub: http://wiki.github.com/radiant/radiant Once everything is in order we can flip the switch and start directing visitors to the Web site to the new wiki. So can I see a show of hands from people who would like to work on this? Seems like a fun project. It's a great way to give back to the community if you have been looking for way to contribute. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Volunteers Needed! Radiant Wiki Migration
On Apr 8, 2009, at 10:49 , michael starke wrote: On 08.04.2009, at 09:33, Mohit Sindhwani wrote: Simon Rönnqvist wrote: Hi! Are we really 100% sure that we want to keep the project forever at GitHub? I mean not so long ago SVN was the standard for Rails projects, now Git is in five years something else might be. And even though we'd stick to using Git are we sure that we want to host our things at GitHub forever? I'm not holding anything against this move, I just thought that other options should be considered too... since we don't want to make this wiki move very often. Unfortunately, Radiant doesn't have a wiki mode :( otherwise, I'd like to have a Radiant site for the documentation :( Just my 2 cents, but i think it's not the best solution tu use radiant as a wiki engine. There're so many other solution out there, maybe we just should stick to a mature wiki engine and host it for ourselves? Or not ;) Greetings, michael Exactly, I wasn't thinking about any wiki system in particular. If nothing good easily easy to integrate into the rest of the site is around then maybe just MediaWiki or something would do, at least people are familiar with it. And remember... GitHub's wiki might not be a bad idea either... I just thought now is a good time to consider the options, to avoid having to move again any time soon. :) (It's actually strange how seldom project's use their wiki, but maybe people preffer using GitHub as a repo only... having a site of their own for the other stuff.) cheers, Simon___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How to specify which site a user can edit, when using newer versions of the multi-site extension?
Hi! I just upgraded my Multi-site installation of Radiant to 0.7.1 från 0.6.9, and of course upgraded all of the extensions too. Now all of my clients can see and edit each others' sites. In the older version of the multi-site extension I could specify which site a user would see... now that's not possible the way I did before. Is there a way, or do I need to move back to where I came from? cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] navigation tag question
Hi! I just remembered seeing this some months ago, now that I needed something like it. Great snippet, thanks! ;) Just one small comment... if someone wants to use this for CSS- dropdowns (like me), just remove the if_ancestor_or_self-tags. cheers, Simon On Oct 17, 2008, at 18:44 , Manuel Meurer wrote: I found the r:navigation tag become too limited to do that kind of stuff. See below for an example of how to do your navigation by hand. div id=navigation ul class=navi li id=Home class=r:if_url matches=^/$active/r:if_urlr:unless_url matches=^/$inactive/r:unless_urla href=/Home/a/li r:find url=/ r:children:each li id=r:slug / class=r:if_ancestor_or_selfactive/ r:if_ancestor_or_selfr:unless_ancestor_or_selfinactive/ r:unless_ancestor_or_self r:link / r:if_ancestor_or_self r:if_children ul class=navi_sub r:children:each li id=r:slug / class=r:if_selfactive/r:if_selfr:unless_selfinactive/ r:unless_selfr:link//li /r:children:each /ul /r:if_children /r:if_ancestor_or_self /li /r:children:each /r:find /ul /div On Thu, Oct 16, 2008 at 9:56 PM, Joe Van Dyk j...@pinkpucker.net wrote: In the below case, I would want the About link to be highlighted, since that's the closest match to the current page. Is there a good way to do that? Joe On Thu, Oct 16, 2008 at 12:39 PM, Sean Cribbs seancri...@gmail.com wrote: Yes. Use r:here if you want exact matches. However, often I just break out the navigation special cases (Home is a typical one). Sean Joe Van Dyk wrote: ul class=sidemenu r:navigation urls=Home: / | About: /about r:normallia href=r:url/r:title //a/li/r:normal r:selectedli class='selected'a href=r:url /r:title //a/li/r:selected /r:navigation /ul Say I'm on the page /about/page. Won't both the Home and the About links have the 'selected' class specified? Since /about/page is a child of both those pages? Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: Drop down menus?
Hi! Yes, if you want it made up automatically then go with Sean's code... and to make that into a drop-down use this: http://www.alistapart.com/articles/dropdowns (the article has nothing to do with Radiant, it's just about CSS... but Sean's code does the Radiant part) Don't know how much experience you have with CSS, but I guess you'll be fine with that article. Good luck! cheers, Simon On Jan 11, 2009, at 24:24 , Kelly Torian wrote: I don't know exactly what you're looking for... The navigation that you describe below is only one level (with no sub categories), for that using a dropdown menu isn't all that common. Anyways dropdowns are most commonly achieved using CSS (see http://www.alistapart.com/articles/dropdowns) to style a unordered list (just like the code Sean Cribbs gave you would have done). However, it seems like you'd rather specify the menu items manually (Sean's code would automatically have created the navigation based on your site three). cheers, Simon Sounds like I'm making this harder than need be. I would prefer to have it created dynamically based on the site tree. I have all the pages in order and parent/child relationships are correct. If I understand you correctly, I should swamp my existing code with Sean's and that should get me moving in the right direction? Thanks for the input, Simon -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Forcing Rails prioritize local gems on Dreamhost?
Hi! It seems like we have different problems. Passenger *does* recognize my gems. I've tried Radiant from a gem and that works. And the error message is different if I haven't included the reference to my own gem directory in envirenment.rb, now it just complains that version 3.0.4 got loaded first. I use Dreamhost PS, so that might affect the situation. What Dreamhost answered me was that my own gems *should* be loaded first, but apparently this is not the case. I don't know, maybe the way the redcloth4 extension is written affects this. If Passenger would be the problem I could of course run Mongrel, cause I'm anyways using the multi-site extension, ie. using Radiant for many sites, so it could be worth the investment. I did add a request into their system about installing RedCloth 4.x, so please go vote for it once it's shown up there everyone!!! :) I'll let you know when it has, or you could speed the process up by screening suggestions and maybe getting to approve mine. cheers, Simon PS. The first page load normally takes at least 15seconds for me using Passenger at my Dreamhost PS, which is about double as much as would be acceptable. Do you know any host that would do much better than this at a reasonable price (I mean I can probably not afford dedicated hosting)? On Dec 12, 2008, at 03:34 , Anton J Aylward wrote: Simon Rönnqvist said the following on 12/11/2008 07:09 PM: Hi! I'm trying to use the redcloth4 extension and have installed RedCloth 4.1.1 locally installed gem in my home directory on Dreamhost. Then Passenger gives me this: can't activate RedCloth (= 4.0.3, runtime), already activated RedCloth-3.0.4 It seems like it's loading the gem version that Dreamhost have provided before loading my locally installed gem. Is there any way in which I could prioritize my own gems or at least in this case force version 4.1.1 to be used? I had a long and marginally frustrating discussion with Dreamhost support over this. It sees Passenger a) ignores the local GEMS in your GEM_PATH because it ignores ENV[GEM_PATH] even if you set it in config/environment.rb b) Passenger _forces_ Production mode, again ignoring any setting in the environment or config/environment.rb c) What it says in the Wiki about this is *WRONG* d) Dreamhost have no plans to install 4.1.1 in /usr/lib/ruby/gems which would be the only other solution. So, what it comes down to is that if you want to use RedCloth 4.1.1 so as to use the Textile editor or the address encryption you are S.O.L. Unless you give up on Passenger and use fcgi. I tried that but it broke other stuff. Is what Dreamhost support told me about Passenger the absolute and whole truth? In context, it doesn't matter because that's what they believe and that's how they are responding to what's going on. Yes I'm frustrated by this. -- Men never do evil so completely and cheerfully as when they do it from religious conviction. --Blaise Pascal (Pensees, 1670) ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Forcing Rails prioritize local gems on Dreamhost?
Hi! I'm trying to use the redcloth4 extension and have installed RedCloth 4.1.1 locally installed gem in my home directory on Dreamhost. Then Passenger gives me this: can't activate RedCloth (= 4.0.3, runtime), already activated RedCloth-3.0.4 It seems like it's loading the gem version that Dreamhost have provided before loading my locally installed gem. Is there any way in which I could prioritize my own gems or at least in this case force version 4.1.1 to be used? cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Dreamhost says Passenger ignores ENV
I ran into the same problem when trying out the RedCloth4 extension. It seemed like Rails grabbed the RedCloth-gem that Dreamhost provides instead of the version that I installed in my local directory. However, earlier on I did get Radiant working, using the Radiant gem that I had installed in my local gems directory. I don't know if that worked cause Dreamhost doesn't provide any Radiant-gem or why... cheers, Simon On Nov 26, 2008, at 16:43 , Anton J Aylward wrote: I've been trying to get Jason Garber's RedClot4 extension to work on my Dreamhost account. Dreamhost support tell me that Passenger ignores environment variables. IS THIS REALLY SO ? OK, so having GEM_PATH set in my .bash_profile would be ignored, then and so all the stuff about local gems would be pointless. So what I did instead was put the ENV settings in config/ environment.rb This makes them inside and not imported from the environment. That didn't work either. Dreamhost support told me That still doesn't work, unfortunately, ANY environment variables do not work within passenger. It's not possible to get custom environment settings within passenger working. This does not make sense to me. This isn't within Passenger, this should be the ruby code itself. I'm now at a complete loss. Dreamhost suggest using fcgi instead of Passenger. Can anyone confirm this shortcoming of Passenger? Can anyone account for why ? I find it hard to beleive that Passenger ignores all of ENV. This http://craigjolicoeur.com/blog/2008/11/set-rails_env-for-phusion-passenger-on-dreamhost/ seems to imply that settings in config/environment.rb work. I also note that Dreamhost's own documentation at http://wiki.dreamhost.com/Passenger seems to contradict what support tells me: A couple of technical notes ... * You can use your local gem repository if you set ENV['GEM_PATH'] = 'path-to-your-gem-repository' in the config/environment.rb file. The same path should be set in shell's environment variables GEM_HOME and GEM_PATH so you can use the gem program to install/upgrade your own gems. You can reload the config file by typing touch tmp/restart.txt in your base directory. Refs:? http://groups.google.com/group/phusion-passenger/browse_thread/thread/79474d37028f2a03 http://groups.google.com/group/phusion-passenger/browse_thread/thread/8fe8222e5f9eeef1 -- shin (n): A device for finding furniture in the dark. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] If you love radiant but need ecommerce what's the best solution
Hi! I've found the shopping module Übercart for Drupal really good. Of course Drupal is PHP-based and all... but really flexible and has a lot of other modules, so very seldom I find myself coding PHP when using Drupal anyways. Generally speaking I use Drupal for more advanced sites, with lots of features, although pretty standard ones (so that you can find ready made modules for them)... while as Radiant CMS again is more appropriate for simpler sites when you want things working your way without much hassle and configuration. http://www.ubercart.org/ cheers, Simon PS. There's also the Drupal E-commerce module, but I find Übercart more ready out of the box.. and its community seems more active too. On Nov 26, 2008, at 22:17 , Steven Southard wrote: Radiant is such a nice platform to develop on that it really pains me to choose another CMS for an upcoming website. It's mainly a brochure site but they also sell about 50 products. They currently have an outdated CMS and a yahoo shopping cart. They want to move forward with an integrated approach. I've been trying out Substruct which has both of these features. The Cart is great but the CMS just fall short of what I've gotten accustom to. Mainly, there's no control of the layout or CSS from the back-end. It might be possible to fix that but I'm not sure how much work it would be. I've also looked at Spree. It looks okay for a cart but doesn't seem to have any other CMS type functions. Maybe it would work well side by side with Radiant or as sub domain but I don't see any way it could be integrated. What are some other approach people have taken to give this type of client what they need? Steven http://www.stevensouthard.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] easier way to do links?
Hi! textile_editor + page_attachments allows you to easily link to files that you've uploaded. In the mail you forwarded below that's the only thing that they asked for, but of course they might want to link to other pages too. cheers, Simon On Nov 21, 2008, at 21:11 , Joe Van Dyk wrote: I got the following message from a client who's using Radiant. Anything like that out there? Hi. We're finding that linking is more difficult in the CMS than under our old system. We have to type in the link by hand, which is more time consuming and more error prone. Is there a way to: * select text that we want to be a link * Then be offered a new window that would allow us to select the correct file we're linking to * then have that path/file name be inserted That's how it works in our current editing program. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Problems installing page_attachments on multisite-installation
Hi! Since I'm intending to try out textile_filter on my Radiant- installation, that uses the multi_site extension (don't know if that one causes trouble, but on my local gem-installation I got everything working). To begin with I tried to install the dependency, page_attachments... but ran into trouble immediately, any ideas about what might have gone wrong? [webben]$ git submodule add git://github.com/radiant/radiant-page- attachments-extension.git vendor/extensions/page_attachments [git output cut out, everything went fine] [webben]$ rake production db:migrate:extensions (in /home/.soes/ronnqvist/radiant) rake aborted! undefined method `has_attachment' for PageAttachment(Table doesn't exist):Class (See full trace by running task with --trace) [webben]$ Cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problems installing page_attachments on multisite-installation (New problem: page_attachments_xsendfile)
Hi! Thanks! Actually that was a RTFM thing. http://wiki.radiantcms.org/Installing_Extension_-_Page_Attachments Sorry about that. :) Ok, now I got everything working apart from one thing, page_attachments_xsendfile just gives me broken images, but no File not found if I try to open the URL of the image file. I also tried it locally on a rather fresh Radiant installation, but the same thing there. cheers, Simon On Nov 21, 2008, at 16:27 , john wrote: You need to git add submodule git://github.com/technoweenie/attachment_fu.git vendor/plugins/attachment_fu before trying to migrate page_attachments On 2008/11/21, at 04:36, Simon Rönnqvist wrote: Hi! Since I'm intending to try out textile_filter on my Radiant- installation, that uses the multi_site extension (don't know if that one causes trouble, but on my local gem-installation I got everything working). To begin with I tried to install the dependency, page_attachments... but ran into trouble immediately, any ideas about what might have gone wrong? [webben]$ git submodule add git://github.com/radiant/radiant-page- attachments-extension.git vendor/extensions/page_attachments [git output cut out, everything went fine] [webben]$ rake production db:migrate:extensions (in /home/.soes/ronnqvist/radiant) rake aborted! undefined method `has_attachment' for PageAttachment(Table doesn't exist):Class (See full trace by running task with --trace) [webben]$ Cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can Radiant be really easy to use for non-technical content editors? (OT: About tight TinyMCE configuration)
Hi!
Just a short note about note about how you can make TinyMCE into
something pretty close to WymEditor: As I mentioned earlier I've tried
a tightly configured TinyMCE, by that I mean that I made available
only the few things that I felt that my customer needed... and those
pieces of functionality were also rather well behaved.
That being said, the customer of course managed to make the page look
inconsistent, even though the code remained valid. (The same kind of
problems are discussed in my thesis.) Up until now I haven't really
found a flexible solution that wouldn't require you to go cleaning up
a bit after the customer, at least in the beginning. (I also made the
bold-button produce strong instead of b and the italic-button em
instead of i, which some would argue is not quite accurate... but in
practise I think it more often produces sensible results that way,
since in most cases the semantics will be OK then.)
Here's the configuration that I used:
script type=text/javascript src=tinymce/jscripts/tiny_mce/
tiny_mce.js/script
script type=text/javascript
function mceToggle(id, linkid) {
element = document.getElementById(id);
link = document.getElementById(linkid);
img_assist = document.getElementById('img_assist-link-'+ id);
if (tinyMCE.getEditorId(element.id) == null) {
tinyMCE.addMCEControl(element, element.id);
element.togg = 'on';
link.innerHTML = 'disable rich-text';
link.href = javascript:mceToggle(' +id+ ', ' +linkid+ ');;
if (img_assist)
img_assist.innerHTML = '';
link.blur();
}
else {
tinyMCE.removeMCEControl(tinyMCE.getEditorId(element.id));
element.togg = 'off';
link.innerHTML = 'enable rich-text';
link.href = javascript:mceToggle(' +id+ ', ' +linkid+ ');;
if (img_assist)
img_assist.innerHTML = img_assist_default_link;
link.blur();
}
}
/script
script type=text/javascript
tinyMCE.init({
mode : exact,
theme : advanced,
relative_urls : false,
document_base_url : /,
language : en,
safari_warning : false,
entity_encoding : raw,
verify_html : true,
preformatted : false,
convert_fonts_to_spans : true,
remove_linebreaks : true,
apply_source_formatting : true,
theme_advanced_resize_horizontal : false,
theme_advanced_resizing_use_cookie : false,
plugins : advimage,contextmenu,fullscreen,
theme_advanced_toolbar_location : top,
theme_advanced_toolbar_align : center,
theme_advanced_path_location : bottom,
theme_advanced_resizing : true,
theme_advanced_blockformats : h2,h3,p,
theme_advanced_buttons1 :
undo
,redo
,separator
,formatselect
,bold
,italic
,numlist,bullist,separator,link,unlink,separator,fullscreen,code,
theme_advanced_buttons2 : ,
theme_advanced_buttons3 : ,
extended_valid_elements : img[class|src|alt|title|hspace|vspace|
width|height|align|onmouseover|onmouseout|name],strong/b,em/i,
theme_advanced_styles : ,
elements : updatedfile
});
/script
cheers, Simon
On Nov 19, 2008, at 20:21 , Casper Fabricius wrote:
I am happy my frustrations resulted in some discussion and good
ideas. The ideas for extensions for a scratch pad, filter toolbars
and som WymEditor + paperclipped would all be highly usable to me,
but I don't have the time to build any of them right now.
I have used TinyMCE filter for some projects, but it has - amongst
other things - resulted in me having to say to the customer: No,
you have to let me edit the frontpage, if you edit it, it will get
messed up (Because TinyMCE has a habit of messing HTML up). But
WymEditor might be more clean at that, so I think I'll try and use it.
The template extension can do many of the things you mention, such
as providing custom forms for different templates, and allowing the
user to select the appropriate template when clicking Add Child.
I'll let you know if I make any interesting discoveries along the way.
Med venlig hilsen / Best regards,
Casper Fabricius
http://casperfabricius.com
On 19/11/2008, at 10.19, Simon Rönnqvist wrote:
Hi!
Yes some WymEditor + paperclipped combination could be really cool.
I've never really used WymEditor for any of my clients.. but I've
tried both Markdown and a tightly configured TinyMCE (which would
be pretty close to WymEditor). With Markdown I've seen that the
content remains largely unstyled, the client eg. just used
UPPERCASE-letters for headings and so on... maybe a Markdown-
toolbar would help stimulate the usage of Markdown-code? With the
TinyMCE solution again stuff got marked up a bit inconsistently,
and often using strong for some headings, even though it didn't
cause quite the mess that a normal 'liberal' WYSIWYG would have.
My guess is that using WymEditor would be a good way to give your
customer a way to try and express what she's looking for, but
chances are that you'll have
Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?
Hi! Personally I feel that Markdown is easier to learn for noobs, and would really have liked to see your extension done with Markdown. However, maybe your toolbar makes the reduces the differences in ease of use between Markdown and Textile. Maybe even Textile is better in conection to buttons, since you can have a H2-button produce h2.Something, but what would you call a button that produces ##Something? Ok, both could be called the more explanatory Heading 2, but you get my point... in general the button name could look more like the textile code that it produces, than it could look like to markdown code that's produced... which could ease up the learning process, when learning to actually write the code. And the rest of your implementation sounds really promising, I'll definitely give it a shot. Thanx! ;) cheers, Simon On Nov 20, 2008, at 15:50 , Jason Garber wrote: I'm catching up to this interesting thread a couple days late, but I can't believe no one's mentioned my textile_editor extension yet! I'm hurt! (jk!) It would have helped if I'd have announced it to the list when I released it in September, huh? :-) [ANN] radiant-textile_editor-extension makes Radiant really easy to use for non-technical content editors! We have a lot (50-ish?) of technology-impared people working on our university website. We haven't rolled the CMS out to all of them yet but so far in my testing I've found that the Textile editor toolbar helps them a bunch. It seems silly because pushing the H1 button inserts h1. and pressing B adds asterisks, but it works because it overcomes their fear and uncertainty about Textile. They pretty quickly get to the point where it's faster to just type h3. than to click the button, but for getting over the initial hump of staring at a blank textbox, it's a huge psychological boost! The part of the toolbar I find myself using all the time is the link and image buttons. The way I designed it, not only can you add Textile links and images, but also enkoded email links, attached images, and attached files. Speaking of attachments, the concept is genius for file management. Buckets and asset libraries and all that are too confusing for my users (I tried paperclipped for a while), but they're used to attaching files in webmail, so the page_attachments extension works out great. I use the page_attachments_xsendfile extension to make the attached file available at a friendly URL (the page's URL + filename). That seems to match people's expectations better. You just tell them they can use an attachment on that page or any page under it and they get it. I'm a strong believer in the non-technical user being able to see what's going on. Even if they can't write r:children:each tags, when they encounter them they'll know what's going on and are less likely to mess up Radius or HTML tags than if they're hidden behind a WYSIWYG editor. Training up front is really the key—and preparing their expectations. So you say, Textile is going to make your life a whole lot easier. Here are a few things it does and here's a toolbar in case you forget. HTML tags [Radius tags in reality] are mostly for the web team. You're not expected to know how to use them, but I'm glad to show you a few so you know what they do. If you're using Textile, make sure you're using version = 4.0. A lot of the hate on RedCloth was rooted in how buggy it was for a few years. You'll need the redcloth4 extension to make it work in Radiant 0.9.6. Jason On Nov 18, 2008, at 3:08 PM, Chris Parrish wrote: 1. I think the textareas need to come with a toolbar above them (page parts, snippets, layouts). These toolbars would be filter specific. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?
Hi! I installed your extension along with the other extensions that you made + page_attachments. I ran rake migrate:db:extensions and everything seemed to go fine... I also saw them show up under Extensions in Radiant. However, no toolbar ever showed up for me, and below the content field I can see the green plus and Attachments (0), but nothing happeneds when i click the plus-symbol. What did I do wrong, or miss? cheers, Simon On Nov 20, 2008, at 15:50 , Jason Garber wrote: I'm catching up to this interesting thread a couple days late, but I can't believe no one's mentioned my textile_editor extension yet! I'm hurt! (jk!) It would have helped if I'd have announced it to the list when I released it in September, huh? :-) [ANN] radiant-textile_editor-extension makes Radiant really easy to use for non-technical content editors! We have a lot (50-ish?) of technology-impared people working on our university website. We haven't rolled the CMS out to all of them yet but so far in my testing I've found that the Textile editor toolbar helps them a bunch. It seems silly because pushing the H1 button inserts h1. and pressing B adds asterisks, but it works because it overcomes their fear and uncertainty about Textile. They pretty quickly get to the point where it's faster to just type h3. than to click the button, but for getting over the initial hump of staring at a blank textbox, it's a huge psychological boost! The part of the toolbar I find myself using all the time is the link and image buttons. The way I designed it, not only can you add Textile links and images, but also enkoded email links, attached images, and attached files. Speaking of attachments, the concept is genius for file management. Buckets and asset libraries and all that are too confusing for my users (I tried paperclipped for a while), but they're used to attaching files in webmail, so the page_attachments extension works out great. I use the page_attachments_xsendfile extension to make the attached file available at a friendly URL (the page's URL + filename). That seems to match people's expectations better. You just tell them they can use an attachment on that page or any page under it and they get it. I'm a strong believer in the non-technical user being able to see what's going on. Even if they can't write r:children:each tags, when they encounter them they'll know what's going on and are less likely to mess up Radius or HTML tags than if they're hidden behind a WYSIWYG editor. Training up front is really the key—and preparing their expectations. So you say, Textile is going to make your life a whole lot easier. Here are a few things it does and here's a toolbar in case you forget. HTML tags [Radius tags in reality] are mostly for the web team. You're not expected to know how to use them, but I'm glad to show you a few so you know what they do. If you're using Textile, make sure you're using version = 4.0. A lot of the hate on RedCloth was rooted in how buggy it was for a few years. You'll need the redcloth4 extension to make it work in Radiant 0.9.6. Jason On Nov 18, 2008, at 3:08 PM, Chris Parrish wrote: 1. I think the textareas need to come with a toolbar above them (page parts, snippets, layouts). These toolbars would be filter specific. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?
OK, sounds like you did a pretty thorough comparison of the two. Personally I just picked Markdown cause it seemed easier to teach my clients doing ## than h2. And also a few other things seemed more simple to learn, and all of the tags that I needed to get done were doable using Markdown, even definition lists using Markdown Extra http://michelf.com/projects/php-markdown/extra/ ...however that was using Drupal (which has Markdown Extra). That being said I hate you for converting from Markdown to Textile, umm... sorry... no filter war. :) No, actually after looking at your extension I can confirm what I just said in the last mail, that your extensions are probably reason enough for me to give Textile a try. (Thanks for the hint on getting 'em installed, I'm a bit of a Radiant noob.) cheers, Simon On Nov 20, 2008, at 18:34 , Jason Garber wrote: I have a little different take: I really like Markdown for plain text documents that are to be read as plain text and might be converted to HTML, but Textile works better for me when I'm using it as a shortcut to HTML (and it won't be published plain-text). I tried Markdown before I'd ever heard of Textile, but these things got to me: Links: I find it easier to write links this way:http://radiantcms.org rather than [this way](http://radiantcms.org) when you're writing them all day, every day. Guess it's just personal preference. Maybe it's because quotes and a colon are easier to type than square brackets and parentheses? Numbered lists: I'm a little OCD, so I found myself re-numbering Markdown numbered lists when I added an item in the middle, even though it technically doesn't matter. Textile's use of the number sign is intuitive and saves me trips to the therapist. :-) Textile supports nested lists and, in RedCloth at least, definition lists, but I haven't found a way to do either in Markdown. Blockquotes: Here again, you only technically need one at the beginning, but there's plenty of room to be obsessive and spend time fixing hard-wrapped blockquotes. Code blocks: Yeah right, like I really want to indent every line of my code by four spaces! Headings: I don't want to have to count how many times I use the pound sign. h4 is less ambiguous than , though My heading looks a lot prettier (esp. when the pound signs are balanced!). Okay, so this is turning into an obsessive-compulsive confession! Now, I don't mean to start a filter war! Just had to defend my choice. I'm glad that Radiant offers both and I wish that I had liked Markdown better than Textile initially because when I started using them a couple years ago, the Ruby Markdown libraries were a lot better than the Textile one! I'd love to see a toolbar for Markdown. I had dreamed of having the same buttons always be on the toolbar and then the output change depending on the filter currently selected (e.g. h2., ##, or h2). Unfortunately, textile_editor is meeting my needs, so I don't have time or motivation to make that happen, but I'd welcome a fork that would! Jason On Nov 20, 2008, at 10:21 AM, Simon Rönnqvist wrote: Hi! Personally I feel that Markdown is easier to learn for noobs, and would really have liked to see your extension done with Markdown. However, maybe your toolbar makes the reduces the differences in ease of use between Markdown and Textile. Maybe even Textile is better in conection to buttons, since you can have a H2-button produce h2.Something, but what would you call a button that produces ##Something? Ok, both could be called the more explanatory Heading 2, but you get my point... in general the button name could look more like the textile code that it produces, than it could look like to markdown code that's produced... which could ease up the learning process, when learning to actually write the code. And the rest of your implementation sounds really promising, I'll definitely give it a shot. Thanx! ;) cheers, Simon On Nov 20, 2008, at 15:50 , Jason Garber wrote: I'm catching up to this interesting thread a couple days late, but I can't believe no one's mentioned my textile_editor extension yet! I'm hurt! (jk!) It would have helped if I'd have announced it to the list when I released it in September, huh? :-) [ANN] radiant-textile_editor-extension makes Radiant really easy to use for non-technical content editors! We have a lot (50-ish?) of technology-impared people working on our university website. We haven't rolled the CMS out to all of them yet but so far in my testing I've found that the Textile editor toolbar helps them a bunch. It seems silly because pushing the H1 button inserts h1. and pressing B adds asterisks, but it works because it overcomes their fear and uncertainty about Textile. They pretty quickly get to the point where it's faster to just type h3. than to click the button
Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?
Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: Casper Fabricius wrote: However, I have a client whose content editor is very frustrated with the system. She can only just tolerate using Markup, and she refuses to write any kind of HTML - Radius tags falls into this category from her point of view. According to her, a proper CMS would hide all this technical stuff and provide custom forms for all types of content. Casper, my solution would be to find a slightly more technical client :P No, I'm joking (of course!) Here's what I would recommend: 1. First, factor out as far as possible so that whatever is not page specific is in snippets. 2. If all she needs is a few styles of pages, I would create different page types or layouts. 3. Then tell her that the different parts that she wants need to go into different page parts. It would be cool if you could modify the Add Child behavior to allow you to select the kind of child page you want and then give you a blank page with all the different tabs created (page parts)... or it could be done with a bit of Javascript that detects when you change the Layout/ page and automatically adds in the different page parts? It could even be a special drop down box next to the Page Type that triggers the actions? 4. The problem: she still needs to use textile for some of the things, such as images. I'm not sure if the Textile Helper will help? It's been a while since I looked at it, but there's a hello world guide on my blog: http://notepad.onghu.com/2007/3/28/using-textile-editor-plugin-and-acts_as_textiled It could make some things easier for her, I hope... without going down the path of WYSIWIG. If you do go down WYSIWIG, I hear good things about WymEditor - and Benny's on the list! Of course, Casper, you are more experienced than I am. Do let us know what you eventually settle on :) Cheers, Mohit. 11/19/2008 | 2:45 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using Radiant unpacked?
Hi! Could it be that when using Passenger you'd save a little on the memory usage by having more common code in betweeen the apps? Anyhow, with Passenger 2 however even running vendor-Rails shouldn't be a big sin (from what I read somewhere). I tried running two gem-based installations and one repo-based, I can't say I saw any significant difference in memory consumption or performance. Quite ironically I didn't see any great difference in memory consumption and performance between Radiant and an freshly made Rails app only displaying a view (with static content), so maybe I just looked in the wrong place... or Radiant is really light-weight. :) cheers, Simon On Nov 11, 2008, at 06:36 , Joe Van Dyk wrote: Personally, I don't know why you'd want to use a gem for radiant, but the option is there. Any time any of my applications depends on a 3rd party library, I try to package up that library with my application. Joe On Mon, Nov 10, 2008 at 2:19 PM, Simon Rönnqvist [EMAIL PROTECTED] wrote: OK, so for what purpose was Radiant made a gem then? :) And is there any easy way to move an installation from/to being a repo-version to/from an installation pointing to a gem? cheers, Simon On Nov 10, 2008, at 23:32 , Joe Van Dyk wrote: I'd keep as much as you can in the repository. What happens if you need to upgrade Radiant for one of your applications, but need to keep another application on an older Radiant version? It's no problem if Radiant (and the rest of the libraries you use) are bundled up with the application. Joe On Mon, Nov 10, 2008 at 4:15 AM, Simon Rönnqvist [EMAIL PROTECTED] wrote: Hi! I just dug up this old post. :) I found that I can also install gems in my home-directory at Dreamhost, I tested installing Radiant that way and it worked. Would you still recommend cloning from the repo or is using a gem just as good, what pros and cons do you see? I'm guessing that the gem version might be more stable, and also easier to maintain if I want to have several installations. While using the repo-version again would give me more flexibility to use newer code, or maybe even switch to some branch. Is it easy to move an installation from using a gem to using a repo-version or the other way around? cheers, Simon On Oct 8, 2008, at 16:57 , Casper Fabricius wrote: Hi Simon, I'd recommend to do a git clone git://github.com/radiant/radiant.git my_radiant_app instead. Remember to create a database.yml file and to create the mysql database on DH. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 08/10/2008, at 15:44, Simon Rönnqvist wrote: Hi! I've been trying to use Radiant unpacked with Dreamhost. But I fail to get it working, maybe I'm doing something wrong... but I failed to find any good howto. I unpacked Radiant into my Radiant app's vendor/gems/ folder using gem unpack radiant. (I'm not 100% sure where I should put it actually.) Then I uploaded the whole thing to Dreamhost and tried the following: $ rake production db:bootstrap (in /home/.soes/ronnqvist/radiant) Missing the Radiant gem. Please `gem install -v= radiant`, update your RADIANT_GEM_VERSION setting in config/environment.rb for the Radiant version you do have installed, or comment out RADIANT_GEM_VERSION to use the latest version installed. So it seems that Rake doesn't know where to look for the Radiant gem. Any ideas on how I do this very basic thing? :) cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org
[Radiant] What mailer extension to use?
Hi! If I'd like to make a simple order form in Radiant, what extension should I use? I found this one that seems to be at a pretty early stage in development, or at least it's not listed at ext.radiantcms.org yet: http://github.com/radiant/radiant-mailer-extension/tree/master I also found some probably obsolete solutions... This is such a basic thing, that most sites need... that it could probably be included into the Radiant core, without bloating it. cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using Radiant unpacked?
Hi! I just dug up this old post. :) I found that I can also install gems in my home-directory at Dreamhost, I tested installing Radiant that way and it worked. Would you still recommend cloning from the repo or is using a gem just as good, what pros and cons do you see? I'm guessing that the gem version might be more stable, and also easier to maintain if I want to have several installations. While using the repo-version again would give me more flexibility to use newer code, or maybe even switch to some branch. Is it easy to move an installation from using a gem to using a repo- version or the other way around? cheers, Simon On Oct 8, 2008, at 16:57 , Casper Fabricius wrote: Hi Simon, I'd recommend to do a git clone git://github.com/radiant/radiant.git my_radiant_app instead. Remember to create a database.yml file and to create the mysql database on DH. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 08/10/2008, at 15:44, Simon Rönnqvist wrote: Hi! I've been trying to use Radiant unpacked with Dreamhost. But I fail to get it working, maybe I'm doing something wrong... but I failed to find any good howto. I unpacked Radiant into my Radiant app's vendor/gems/ folder using gem unpack radiant. (I'm not 100% sure where I should put it actually.) Then I uploaded the whole thing to Dreamhost and tried the following: $ rake production db:bootstrap (in /home/.soes/ronnqvist/radiant) Missing the Radiant gem. Please `gem install -v= radiant`, update your RADIANT_GEM_VERSION setting in config/environment.rb for the Radiant version you do have installed, or comment out RADIANT_GEM_VERSION to use the latest version installed. So it seems that Rake doesn't know where to look for the Radiant gem. Any ideas on how I do this very basic thing? :) cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using Radiant unpacked?
OK, so for what purpose was Radiant made a gem then? :) And is there any easy way to move an installation from/to being a repo- version to/from an installation pointing to a gem? cheers, Simon On Nov 10, 2008, at 23:32 , Joe Van Dyk wrote: I'd keep as much as you can in the repository. What happens if you need to upgrade Radiant for one of your applications, but need to keep another application on an older Radiant version? It's no problem if Radiant (and the rest of the libraries you use) are bundled up with the application. Joe On Mon, Nov 10, 2008 at 4:15 AM, Simon Rönnqvist [EMAIL PROTECTED] wrote: Hi! I just dug up this old post. :) I found that I can also install gems in my home-directory at Dreamhost, I tested installing Radiant that way and it worked. Would you still recommend cloning from the repo or is using a gem just as good, what pros and cons do you see? I'm guessing that the gem version might be more stable, and also easier to maintain if I want to have several installations. While using the repo-version again would give me more flexibility to use newer code, or maybe even switch to some branch. Is it easy to move an installation from using a gem to using a repo- version or the other way around? cheers, Simon On Oct 8, 2008, at 16:57 , Casper Fabricius wrote: Hi Simon, I'd recommend to do a git clone git://github.com/radiant/radiant.git my_radiant_app instead. Remember to create a database.yml file and to create the mysql database on DH. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 08/10/2008, at 15:44, Simon Rönnqvist wrote: Hi! I've been trying to use Radiant unpacked with Dreamhost. But I fail to get it working, maybe I'm doing something wrong... but I failed to find any good howto. I unpacked Radiant into my Radiant app's vendor/gems/ folder using gem unpack radiant. (I'm not 100% sure where I should put it actually.) Then I uploaded the whole thing to Dreamhost and tried the following: $ rake production db:bootstrap (in /home/.soes/ronnqvist/radiant) Missing the Radiant gem. Please `gem install -v= radiant`, update your RADIANT_GEM_VERSION setting in config/environment.rb for the Radiant version you do have installed, or comment out RADIANT_GEM_VERSION to use the latest version installed. So it seems that Rake doesn't know where to look for the Radiant gem. Any ideas on how I do this very basic thing? :) cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Any easy way to extract sites from multi-site installation?
Hi! OK, so I'm talking to myself here. :) Anyways, one solution that occurred to me was to simply copy the whole database+radiant-installation, and then just remove all of the stuff that doesn't relate to the site that you wanted to extract. Haven't tried it yet... but I don't see why it wouldn't work, do you see any problems with this approach? cheers, Simon On Oct 27, 2008, at 03:21 , Simon Rönnqvist wrote: Hi! I've been doing a bit of testing I've found that an instance of Radiant+Rails easily eats up up to 80MB of memory for a while when using mod_rails, after a while one of the processes dies and about half of the memory usage is left hanging for quite some time. (I'm using Dreamhost so I don't think I can configure the timeout periods in any ways.) So this leaves me with the conclusion that the only sensible way to host small Radiant-sites is using the multi-site extension, even when using mod_rails (at least at Dreamhost where you can't shorten the timeout periods for things). So because of this I might want to jam all of the small sites that I've made for my customers into a single multi-site installation of Radiant. But what do I do then if I for some reason later would have to move one site out of that installation? Do I just copy paste all of the material? No that can't be the case, can it? :) cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Any easy way to extract sites from multi-site installation?
Hi! I've been doing a bit of testing I've found that an instance of Radiant +Rails easily eats up up to 80MB of memory for a while when using mod_rails, after a while one of the processes dies and about half of the memory usage is left hanging for quite some time. (I'm using Dreamhost so I don't think I can configure the timeout periods in any ways.) So this leaves me with the conclusion that the only sensible way to host small Radiant-sites is using the multi-site extension, even when using mod_rails (at least at Dreamhost where you can't shorten the timeout periods for things). So because of this I might want to jam all of the small sites that I've made for my customers into a single multi-site installation of Radiant. But what do I do then if I for some reason later would have to move one site out of that installation? Do I just copy paste all of the material? No that can't be the case, can it? :) cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Hide stylesheets and RSS-templates from user? (+ multi_site editing for users)
On Oct 14, 2008, at 23:16 , Chris Parrish wrote: Hi! Thanks for the hints! My Styles 'n Scripts extension moves your CSS and JS out of the Pages view and are only accessible by admins and developers so that could work for you. Thankyou I might check it out, although using static files is pretty alright too. In fact, with them I can use a proper CSS editor. As to RSS feeds, if you only have a few, I would just create a Layout for each (you have to create at least one layout to set the Content-Type anyway). But instead of creating a blank layout and putting all your markup in a page, do the reverse. Put your markup in the layout and use a blank page to give it a url. (You can probably even get away with not putting any r:content tag in your layout but you'd have to test that.). Not perfect (a user could still delete the page, rename it, and maybe add content) but it's a good way towards the goal in my book. Yes, I actually figured this one out myself right after I sent my last post. However, it'd really be cool to avoid this problem. Not mostly because the user could delete the whole thing, but because it'd from a usability perspective should be moved out of sight. Maybe adding it as a feature to your Styles 'n Scripts extension could make sense, since it probably could use the same technique to move the RSS- template out of sight from the user. (Although RSS-templates aren't styles or scripts, strictly speaking.) cheers, Simon Simon Rönnqvist wrote: Hi! I'd like to hide the RSS-template and stylesheets from the ordinary user (ie. not developer or administrator), how do I do this? For the stylesheets I can just put them as hard-coded files in public/ stylesheets/site.ltd/ but the RSS-template can't really be placed there. Another configuration option that I'd like to have (or figure out) is to enable an ordinary user to edit more than one site (or all sites if individual sites can't be picked), when using the multi_site extension. cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Using Radiant unpacked?
Hi! I've been trying to use Radiant unpacked with Dreamhost. But I fail to get it working, maybe I'm doing something wrong... but I failed to find any good howto. I unpacked Radiant into my Radiant app's vendor/gems/ folder using gem unpack radiant. (I'm not 100% sure where I should put it actually.) Then I uploaded the whole thing to Dreamhost and tried the following: $ rake production db:bootstrap (in /home/.soes/ronnqvist/radiant) Missing the Radiant gem. Please `gem install -v= radiant`, update your RADIANT_GEM_VERSION setting in config/environment.rb for the Radiant version you do have installed, or comment out RADIANT_GEM_VERSION to use the latest version installed. So it seems that Rake doesn't know where to look for the Radiant gem. Any ideas on how I do this very basic thing? :) cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] multiple domains under Phusion Passenger
Hi! I tried playing around a bit with the multi_site extension. Two questions came to me: 1. Are you in any way able to give an ordinary user access to edit all sites? (Checkboxes instead of a dropdown menu would be better when granting access sites, then you could pick exactly which sites the ordinary user should be able to edit.) 2. Is there any easy way to move/extract a single site from a multi_site installation to another... or maybe even to a separate installation without the multi_site extension installed? cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] multiple domains under Phusion Passenger
Hi! I'm actually looking the very same thing. I found this howto http://casperfabricius.com/site/2008/05/24/radiant-cms-on-dreamhost-with-phusion-passenger/ , but I got stuck trying to get Capistrano at different stages of the process (didn't succeed nor give in yet). Anyhow, Capistrano isn't needed at all... so I might as well try doing without it... it's just that the howto involved it, and I was curious about trying it. :) cheers, Simon On Oct 7, 2008, at 23:46 , Bill Barnard wrote: I'm working on a pair of sites for a client that will be on two subdomains and hosted on a shared host (Dreamhost). I thought the multi-site extension would be ideal for that but have not yet figured out how to do this under Phusion Passenger, the preferred Rails deployment method at DH. I did a similar thing for another client using the FastCGI method; I created a mirror public directory for the dev host; the dev subdomain points to that mirrored directory. The mirror dir contains mostly links back into the public dir, except for the .htaccess which has different mod_rewrite rules. I tried doing the same thing under Passenger without success. Has anyone done anything similar under Passenger? I'm searching the Passenger groups docs but have not yet found anything useful. Thanks! Bill ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] multiple domains under Phusion Passenger
On Oct 8, 2008, at 24:56 , Adam van den Hoven wrote: I have never really grokked Capistrano. Casper's tutorial had too many Log into your shell account and run this rake task for my liking too, which seems to negate the value of Capistrano. In addition, most installations are fundamentally just creating the radiant app, configuring the database connections and installing extensions. It seems to me that you can just install that directly into your DH account. Yeah... but I think Casper's tutorial is pretty much based on (or the other way around) http://wiki.radiantcms.org/How_To_Deploy_on_Dreamhost (to which he has linked at the bottom of his blog post). There they say: You can either deploy using Capistrano, which is highly recommended if you plan to add extensions and make changes to the default Radiant code, or you can deploy using SFTP, if you just want to upload and use Radiant without touching any Ruby code. From that I kind of got the picture that you were recommended to use Capistrano if you wanted to add extensions... but maybe I should pay more attention to the AND make changes to the default Radiant code. :) However, I'm pretty likely to write my own extensions once I get more into using Radiant. Another thing that struck me while trying to get capistrano work was: Basically what cap deploy does for me is ssh [EMAIL PROTECTED] cd path/to/app svn up rake something touch tmp/restart.txt And for that alone, with a single server to do it on, Capistrano seems like a bit of an overkill. Sometimes we Rails folks seem to try and be just too clever and find ourselves getting all caught up with nifty tools. :) cheers, Simon I am thinking of putting together a the bare minimum installation for DreamHost using Phusion for the wiki but real work always seems to take precedence. Adam On 7-Oct-08, at 2:47 PM, Simon Rönnqvist wrote: On Oct 8, 2008, at 24:34 , Bill Barnard wrote: On Wed, Oct 08, 2008 at 12:29:04AM +0300, Simon Rönnqvist wrote: Hi! I'm actually looking the very same thing. I found this howto http://casperfabricius.com/site/2008/05/24/radiant-cms-on-dreamhost-with-phusion-passenger/ , but I got stuck trying to get Capistrano at different stages of the process (didn't succeed nor give in yet). Anyhow, Capistrano isn't needed at all... so I might as well try doing without it... it's just that the howto involved it, and I was curious about trying it. :) cheers, Simon I've used the same howto. It looks as though Capistrano is not available on Dreamhost any longer, though you can install it as a local gem. I think it's probably a good tool and want to learn about it but I try not to learn *too* many new things on any one project... Bill Aha... so does Capistrano need to be installed on the server? I thought it just had to run on my computer. Even though I've had several issues with it, it has indeed done at least some stuff on the server for me. cheers, Simon___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] multiple domains under Phusion Passenger
On Oct 8, 2008, at 01:10 , Josh French wrote: I'm working on a pair of sites for a client that will be on two subdomains and hosted on a shared host (Dreamhost). I thought the multi-site extension would be ideal for that but have not yet figured out how to do this under Phusion Passenger, the preferred Rails deployment method at DH. To allow mod_rewrite, add this to your apache conf: RailsAllowModRewrite on SInce we're talking Dreamhost here... editing apache.conf can't be done (unless they provide some kind of smart Dreamhostish workaround for it that I am unaware of). Not even with the Dreamhost PS (Private Server) service you have root access to your server. Passenger's issue with mod_rewrite is that the default .htaccess supplied with Rails tries to funnel all requests through one of the dispatchers, so be sure to remove either the entire .htaccess file from /public, or remove everything but those parts you know you need (e.g. static caching, as Jay Levitt mentioned.) However, we've successfully served multiple subdomains without resorting to mod_rewrite by defining each subdomain from within the multisite extension -- main.tld and sub.main.tld, both being served from a single Radiant instance. Is that your use case? Your question implies you've got a dev or preview domain that may need additional http authentication -- that's also possible, but I don't want to confuse the issue if that's not your scenario. From one thing to another. A couple of questions occurred to me: Does using the multisite extension provide any benefit when it comes to performance, when using mod_rails? Or does it just affect how you maintain the site? And the same thing about this: Does deploying several 'unpacked' Radiant installations performancewise have any downsides as opposed to using Radiant as a gem (sharing more code in between the installations), here too using mod_rails. I guess the same kind of logic applies for using Rails from the vendor-directory vs. not doing that, too. cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to order articles by date in the back-end?
On Sep 26, 2008, at 09:47 , Mohit Sindhwani wrote: Simon Rönnqvist wrote: Hi and thanks for the quick answer! On Sep 26, 2008, at 07:14 , Jim Gay wrote: Just to prevent any confusion, its the 'default_order' plugin, not extension And take a look at http://github.com/avonderluft/radiant-page_list_view-extension/tree/master for another way to do it I think ordering by title is great for a CMS. For a blog it makes less sense, but Radiant was built first to be a CMS. OK, so this means that the order of all of the things in the three would be according to date? That's not exactly what I was looking for, the best option would be if only the articles (ie. blog posts/news articles) would be ordered by date, the rest may well be ordered alphabetically. (Or in fact ordering by weight would be useful, so that the user could for example define the order in which the normal (static) pages should appear in the menu by dragging and dropping them into the right order in the back-end three. But that's a different story.) If I'm not wrong, the reorder plugin would help you with that part - however, it doesn't affect only the admin, it affects the display of articles on the site also. If you're after that ability, it's exactly what you should consider using. We have a page in the Summer Reboot documentation project about the Reorder extension: http://wiki.radiantcms.org/Reorder - there are some screenshots there that may give you an idea of what it looks like (in the front-end and the admin area). Hope this helps. Cheers, Mohit. 9/26/2008 | 2:46 PM. Yes, that's what I was looking for (in my comment within the parenthesis). Thanks! Hope this plays well together with having articles ordered by date. I'll try playing around with these as soon as I have time, you'll probably hear from me. :) cheers, Simon___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How to order articles by date in the back-end?
Hi! I'm really new to Radiant, so I might have missed something basic.. however I was unable to find the answer when looking around for a while. I find it a bit strange that Radiant shows article ordered by title in the admin back-end by default. Is there at least an easy way to change this behavior so that they'd be ordered by date there too (and not only on the actual web page)? cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
