Re: [Radiant] Mailer Extension again
Ah...got it. I wasn't understanding "parts", when you hover over the +/- buttons they're called "tabs", that has fixed my problems. On Feb 10, 2009, at 9:09 PM, Dave Kroondyk wrote: Are you creating page parts? These are different than regular pages. When editing any page, there are + and - icons near the top right... click the + to add a new "page part." On Tue, Feb 10, 2009 at 8:20 PM, Adam Farnsworth >wrote: Thanks- I think this may end up helping me, I have three questions: 1. I want to clarify, the "config" page needs to be named "mailer" and should contain this code (with my specs, of course): subject: From the website of Whatever from: nore...@example.com redirect_to: /contact/thank-you recipients: - o...@one.com - t...@two.com 2. Where do you define SMTP values and such? 3. Does the "mailer" page need to be on the root level of the pages? As in, does it need to spur off of the "Home Page" or can the hierachy looks something like this: HomePage - Contact Us - mailer Thanks again, Adam On Jan 29, 2009, at 8:26 PM, Dave Kroondyk wrote: I just ran into this same problem following this guide: http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension Turns out that you don't need to specify a "Mailer" type. Also, the "config" page part that the How To describes is wrong. Following the readme on the extension's git page - http://github.com/radiant/radiant-mailer-extension - I discovered that the "config" page part should in fact be named "mailer." Moral of the story... make sure to study the current documentation as it seems the How To doc is slightly outdated... Dave On Sat, Jan 10, 2009 at 12:56 PM, Patrick wrote: Hi, as already asked by Andrew Gehring I am also trying to get the mailer extension working. But I am stuck at the same point... I have: - Radiant 0.6.9 - running on Rails 2.0.2 I installed the mailer extension as explained on [1] via git clone into the directory vendor/extensions/mailer. The first problem is, that I have no page type 'Mailer' I could choose in the admin interface when creating the mail form (even after rebooting radiant). So I created a normal page as explained in the how-to but when I access it I just see the error message 'Mailer config is not valid (see Mailer.valid_config?)' Any help about what is wrong in my setup? Thanks Patrick [1] http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension ___ 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] So what doesn't work with 0.7?
Anton Aylward wrote: And that Wiki page should have a few lies for those of us who are not git-gurus on how to use - aka download from - one tag or the other. If you're on Windows, you could take a look at: http://wiki.radiantcms.org/JustEnoughGitOnWindows It was compiled by another Git-Idiot (i.e. me) Cheers, Mohit. 2/11/2009 | 1:19 PM. ___ 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 again
Are you creating page parts? These are different than regular pages. When editing any page, there are + and - icons near the top right... click the + to add a new "page part." On Tue, Feb 10, 2009 at 8:20 PM, Adam Farnsworth wrote: > Thanks- > > I think this may end up helping me, I have three questions: > > 1. I want to clarify, the "config" page needs to be named "mailer" and > should contain this code (with my specs, of course): >subject: From the website of Whatever >from: nore...@example.com >redirect_to: /contact/thank-you >recipients: >- o...@one.com >- t...@two.com > > 2. Where do you define SMTP values and such? > > 3. Does the "mailer" page need to be on the root level of the pages? As in, > does it need to spur off of the "Home Page" or can the hierachy looks > something like this: >HomePage >- Contact Us >- mailer > > Thanks again, > Adam > > > > On Jan 29, 2009, at 8:26 PM, Dave Kroondyk wrote: > > I just ran into this same problem following this guide: >> http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension >> >> Turns out that you don't need to specify a "Mailer" type. Also, the >> "config" >> page part that the How To describes is wrong. Following the readme on the >> extension's git page - http://github.com/radiant/radiant-mailer-extension >> - >> I discovered that the "config" page part should in fact be named "mailer." >> >> Moral of the story... make sure to study the current documentation as it >> seems the How To doc is slightly outdated... >> >> Dave >> >> On Sat, Jan 10, 2009 at 12:56 PM, Patrick wrote: >> >> Hi, >>> >>> >>> as already asked by Andrew Gehring I am also trying to get the >>> mailer extension working. But I am stuck at the same point... >>> >>> I have: >>> >>> - Radiant 0.6.9 >>> - running on Rails 2.0.2 >>> >>> >>> I installed the mailer extension as explained on [1] via git >>> clone into the directory vendor/extensions/mailer. >>> >>> The first problem is, that I have no page type 'Mailer' I >>> could choose in the admin interface when creating the >>> mail form (even after rebooting radiant). >>> >>> So I created a normal page as explained in the how-to but >>> when I access it I just see the error message 'Mailer config is >>> not valid (see Mailer.valid_config?)' >>> >>> Any help about what is wrong in my setup? >>> >>> Thanks >>> >>> Patrick >>> >>> >>> >>> [1] http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension >>> ___ >>> 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] tags extension
Hi, maybe I was drunk. Apparently works fine inside No need for tricks. It will automatically display the tags of that children page. Ciao, Enrico 2009/1/28 Simon Josi : > Maybe this could work: > http://github.com/Aissac/radiant-extensions-extension > > greets > /simon > > On Wed, 28 Jan 2009 12:14:42 +1100 > Enrico Teotti wrote: > >> Hi, >> I need to have the tag list for each page coming out of: >> >> >> I'd use a: >> >> >> but since that's not allowed by radius I am now clueless. How would >> you do it? Is anybody doing such a thing? >> Cheers, >> Enrico > > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > -- Enrico Teotti IT consultant, accessible web sites and web applications Sydney, NSW, Australia enrico.teo...@gmail.com mobile (IT) +393286590765 mobile (AU) +00610416748450 http://www.teotti.com ___ 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: Mailer extension oddities
I concur. I'm getting this error now as well. On Feb 10, 2009, at 10:12 AM, Victor Zuniga wrote: Would you mind sharing the setting? I am experiencing the same redirect issue when testing out the mailer extension. Thanks, Victor On 2/9/09 11:12 AM, "john muhl" wrote: Nevermind I found the esoteric mailer config setting that enforces the correct behavior. Is there any reason why the strange behavior described above is the default one? On Sun, Feb 8, 2009 at 10:32 PM, john muhl wrote: I'm not sure if it has to do with 0.7.0 or the mailer extension in general but I am getting odd redirects. For example, I have a contact page like this http://gist.github.com/60672 When the form submits successfully the user ends gets redirected at http://example.com/contact/thanks#mailer When the form is missing some required fields the user gets redirected to http://example.com/pages/9/mail#mailer Is there something in my configuration causing the #mailer to get tacked on? What is up with that url when the form is missing fields? Are these just side effects of the mailer extension not being completely 0.7.0 compatible? I'm using the latest commit of the mailer extension and the 0.7.0 final release frozen in vendor/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] Mailer Extension again
Thanks- I think this may end up helping me, I have three questions: 1. I want to clarify, the "config" page needs to be named "mailer" and should contain this code (with my specs, of course): subject: From the website of Whatever from: nore...@example.com redirect_to: /contact/thank-you recipients: - o...@one.com - t...@two.com 2. Where do you define SMTP values and such? 3. Does the "mailer" page need to be on the root level of the pages? As in, does it need to spur off of the "Home Page" or can the hierachy looks something like this: HomePage - Contact Us - mailer Thanks again, Adam On Jan 29, 2009, at 8:26 PM, Dave Kroondyk wrote: I just ran into this same problem following this guide: http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension Turns out that you don't need to specify a "Mailer" type. Also, the "config" page part that the How To describes is wrong. Following the readme on the extension's git page - http://github.com/radiant/radiant-mailer-extension - I discovered that the "config" page part should in fact be named "mailer." Moral of the story... make sure to study the current documentation as it seems the How To doc is slightly outdated... Dave On Sat, Jan 10, 2009 at 12:56 PM, Patrick wrote: Hi, as already asked by Andrew Gehring I am also trying to get the mailer extension working. But I am stuck at the same point... I have: - Radiant 0.6.9 - running on Rails 2.0.2 I installed the mailer extension as explained on [1] via git clone into the directory vendor/extensions/mailer. The first problem is, that I have no page type 'Mailer' I could choose in the admin interface when creating the mail form (even after rebooting radiant). So I created a normal page as explained in the how-to but when I access it I just see the error message 'Mailer config is not valid (see Mailer.valid_config?)' Any help about what is wrong in my setup? Thanks Patrick [1] http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension ___ 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 Design Templates (CSS and Images)
On 10 Feb 2009, at 20:51, Tony Davis wrote: I would like to use a design template that consists of a number of image files and a few css files in my radiant project. I am used to regular rails programming and I would add them to the publc/css directory (and similar for images). How do I add them to radiant ? You can put stylesheets in public/stylesheets, and images in public/ images, and they will be available to your Radiant site. If you want to be able to upload new images through the web interface (rather than using ftp, or capistrano deployment), then you would probably want to use an asset management extension. You have a choice: http://github.com/kbingman/paperclipped/tree/master http://github.com/radiant/radiant-page-attachments-extension/tree/master Try them both out, and see which you prefer. If you want to be able to edit your CSS files through the web interface, the simplest way is to create a Page in the sitemap, and use the "Stylesheet" layout. Take a look at the styled blog template for an example of how this is done. An alternative is to install the "styles'n'scripts" extension: http://github.com/SwankInnovations/radiant-sns-extension/tree/master I hope that doesn't leave you paralysed by the choices! Cheers, Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Mailer Extension Instructions, Very Confusing
Can someone please confirm or correct this list of my understanding or
the mailer extension? I'm not understanding at all how this extension
works, and the two tutorials/instructions I found on the subject are
very vague:
I gathered this list by using these two instructions:
http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension
http://github.com/radiant/radiant-mailer-extension/tree/master
- You start out by git cloning the extension into the extension folder
at /vendor/extensions/
- You either do this step now, or at the end of the tutorial. Which
ever one, you remove code in the environment.rb (located in the config
folder) file to make this:
config.frameworks -= [ :action_mailer ] or this: config.frameworks -=
[ :action_web_service, :action_mailer ]
say this:
config.frameworks -= [] or this: config.frameworks -=
[ :action_web_service ]
depending on whether or not the :action_web_service is being ignored
or not.
- You then possibly, or possibly not, add this code to the
environment.rb file, but after a line that doesn't seem to exist
(require "status"):
ActionMailer::Base.smtp_settings = {
:address => "your.smtp.server",
:port => 25,
:domain => "your.domain"
}
obviously changing the setting to match your own.
- Restart your server.
- You then create two new pages, under whatever previous page you'd
prefer, one named "email" the other "email_html" in that file you put
the following code:
subject: From the website of Whatever
from: nore...@example.com
redirect_to: /contact/thank-you
recipients:
- o...@one.com
- t...@two.com
- You then build your contact form with these tags:
...
...
...
...
to make something that looks something like this:
>
Name:
Message:
If someone who has gotten the extension to work please let me know
where I went wrong, it would be very helpful. By doing everything
above I get the following error in a browser:
Mailer config is not valid (see Mailer.valid_config?)
Thanks,
Adam
___
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". activeinactive">Home class="activer:if_ancestor_or_self>inactiver:unless_ancestor_or_self>"> class="activeinactiver:unless_self>"> On Thu, Oct 16, 2008 at 9:56 PM, Joe Van Dyk 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 wrote: Yes. Use 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: 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] tags extension
I'm looking at radius_tags.rb tag "all_tags:each" do |tag| order = tag.attr['order'] || 'name' limit = tag.attr['limit'] || '5' result = [] case order when 'name' all_tags = MetaTag.find(:all, :limit => limit) else all_tags = MetaTag.cloud(:limit => limit) end all_tags.each do |t| tag.locals.meta_tag = t result << tag.expand end result end And for my use it would be better if it had a conditional statement eliminating any tags not used in any of the pages. Does anyone have quick idea how to get at that? Steven On Feb 9, 2009, at 8:53 PM, Steven Southard wrote: seems to list tags even if they're not currently being used. Is there any way to list only tags that are being used? Or is there any way to manage tag or at least remove unused tags? //Steven ___ 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 Design Templates (CSS and Images)
I would like to use a design template that consists of a number of image files and a few css files in my radiant project. I am used to regular rails programming and I would add them to the publc/css directory (and similar for images). How do I add them to 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] So what doesn't work with 0.7?
Philip Hallstrom wrote: Why not make the field available on ext.radiantcms.org? When you edit an extension it asks for the highest version the extension works with. But I don't see that info displayed on the listing/ detail page itself. Just the edit form. That page already lists the github url... That's a great idea. Now we just need all the creators of the extensions on the list to update their extension info. ;^) Heh. Good point. Although in this case if a several trusted folks confirm it works or doesn't work I don't see much difference b/n publishing a wiki page and sending a data file of name:version pairs to someone who could update the extension database directly... Maybe at some point when a new version is released an email should go out to all the authors listed in ext.radiantcms.org? -p ___ 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: Mailer extension oddities
Would you mind sharing the setting? I am experiencing the same redirect issue when testing out the mailer extension. Thanks, Victor On 2/9/09 11:12 AM, "john muhl" wrote: > Nevermind I found the esoteric mailer config setting that enforces the > correct behavior. Is there any reason why the strange behavior described > above is the default one? > > On Sun, Feb 8, 2009 at 10:32 PM, john muhl wrote: > >> I'm not sure if it has to do with 0.7.0 or the mailer extension in general >> but I am getting odd redirects. For example, I have a contact page like this >> http://gist.github.com/60672 >> >> When the form submits successfully the user ends gets redirected at >> http://example.com/contact/thanks#mailer >> >> When the form is missing some required fields the user gets redirected to >> http://example.com/pages/9/mail#mailer >> >> Is there something in my configuration causing the #mailer to get tacked >> on? What is up with that url when the form is missing fields? Are these just >> side effects of the mailer extension not being completely 0.7.0 compatible? >> I'm using the latest commit of the mailer extension and the 0.7.0 final >> release frozen in vendor/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] So what doesn't work with 0.7?
Philip Hallstrom wrote: Why not make the field available on ext.radiantcms.org? When you edit an extension it asks for the highest version the extension works with. But I don't see that info displayed on the listing/detail page itself. Just the edit form. That page already lists the github url... That's a great idea. Now we just need all the creators of the extensions on the list to update their extension info. ;^) ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] So what doesn't work with 0.7?
Mohit Sindhwani wrote: N. Turnage wrote: Since this question is going to be asked a number of times as people begin to move their sites to v0.7 I thought I would begin the thread. What extensions are known not to work with v0.7? Could we make this a page on the wiki instead? May I request that people who have written extensions and have an explicit tag that works for 0.6.9 and below and a trunk that works on 0.7.0 and later make it known there? This will make my job of working through the content for 0.7.0 easier. If someone needs a template, I can try to create the main page on the wiki for this. That's a great idea, Mohit. I would think the following info should be included: - name of extension (of course) - github project url - latest commit known to be working with 0.6.9 if no tag exists Why not make the field available on ext.radiantcms.org? When you edit an extension it asks for the highest version the extension works with. But I don't see that info displayed on the listing/detail page itself. Just the edit form. That page already lists the github url... -philip ___ 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 make your website really, really fast
http://blogs.zdnet.com/weblife/?p=207&tag=nl.e539 Some interesting ideas here, since so many of our sites are interactive. -- The truth of a proposition has nothing to do with its credibility. And vice versa. Excerpt from the notebooks of Lazarus Long, from Robert Heinlein's "Time Enough for Love" ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] So what doesn't work with 0.7?
N. Turnage said the following on 02/09/2009 10:17 PM: > Mohit Sindhwani wrote: >> N. Turnage wrote: >>> Since this question is going to be asked a number of times as people >>> begin to move their sites to v0.7 I thought I would begin the thread. >>> What extensions are known not to work with v0.7? >> Could we make this a page on the wiki instead? May I request that >> people who have written extensions and have an explicit tag that works >> for 0.6.9 and below and a trunk that works on 0.7.0 and later make it >> known there? >> >> This will make my job of working through the content for 0.7.0 >> easier. If someone needs a template, I can try to create the main >> page on the wiki for this. > > That's a great idea, Mohit. I would think the following info should be > included: > > - name of extension (of course) > - github project url > - latest commit known to be working with 0.6.9 if no tag exists And that Wiki page should have a few lies for those of us who are not git-gurus on how to use - aka download from - one tag or the other. Thanks. A git-diot. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rendering pages from a rake task
Remko, As long as your monkey-patch lives only for the scope of your rake task, it should be fine. In the future, this will not be an issue because Rails 2.2(?) made the relative_url_root a property of ActionController::Base rather than the request. Sean Remko Steenstra wrote: Hi all, I am working on an extension that needs to render pages as part of a rake task. This works, but I have run into a problem when using in my content. Because there is no request object, the relative_url_for method in standard_tags.rb throws an Exception. As a workaround, I've monkey-patched my Radiant (see below). Is there a better solution? Am I missing something obvious? Thanks! Remko standard_tags.rb: def relative_url_for(url, request) root = request.relative_url_root rescue '' File.join(root, url) end ___ 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
