Re: [Radiant] mailers, which one should I use?
Hey Chris, That is pretty much what I was looking for before I used apache rules to do it. I really can't say how big a problem it is because I don't know how many people need to run production radiant on non-root urls, and I don't know how many of them are as green and part-time as me, and wouldn't be able to tweak the source a bit on their own to do it. There might be a benefit to having something like what you describe (one line of code commented out by default) in the environment.rb for the whole radiant install and its extensions, but I don't know how much cat-herding would be involved in getting that implemented and getting all the extension code to work with it. Nonetheless, thanks for the clarification on that. I didn't know about the custom_settings.rb, so that little bit of information should come in handy sooner or later. --danny Chris Parrish wrote: > Danny, > > I was hoping to include a fix for this issue with v0.4 but did not get > to it yet. But, for now, you can already solve this issue using the > config settings that I have built into the SnS extension (don't know > why I didn't think of this sooner). > > To do this you edit the custom_settings.rb file in the root of the > extension. In there you will find instructions and commented-out > settings for the stylesheet_directory and javascript_directory (lines > 24 & 25 in my latest version). Based on your example, you'd set these > to: > > StylesNScripts::Config[:stylesheet_directory] = 'radiantroot/css' > StylesNScripts::Config[:javascript_directory] = 'radiantroot/js' > > Or if you want to get creative, you could: > > StylesNScripts::Config[:stylesheet_directory] = > 'radiantroot/assets/my-stylesheets' > StylesNScripts::Config[:javascript_directory] = > 'radiantroot/assets/my-javascripts' > > Restart your server and everything should just work for you (unless > I'm misunderstanding your request here). These settings will > automatically adjust caching, rendering, and all the tags. > > -Chris > > danny q. wrote: >> Yes I am using Styles 'n Scripts, >> >> and yes, I did notice most of this was fixed in 0.6.5, but IIRC, there >> were two problems I had to address for the relative link issue. >> First, with the old-fashioned script and style linking, each had to be >> set explicitly in the tag. That is, I had to do > href="/radiantroot/..."> instead of just href="...". That wasn't a big >> deal, because it was in layouts which I only had to think about once >> (but then would have had to remind myself to change before deploying and >> moving to the url root). I'd hardly call this an issue with radiant. >> It's just how the html is supposed to work, right? >> >> Second, the problem was a general gotcha with extensions. Any extension >> based on a path relative to / wouldn't work. This included >> styles-n-scripts, mailer, and, I think calendar. I dug around for a >> definition of a variable that would fix that, but didn't have much luck, >> so decided to just go with the .htaccess hack. It works well enough for >> testing, and I definitely 'get' the whole thing about radiant not being >> defined for sub-urls. >> >> It might be interesting to see how well the root url variable definition >> would work, but it looks like some of the extensions just assume it's >> "/" and hard-code that way (based on my shaky RoR reading), so that >> could limit the mileage a bit. >> >> By the way, great work on both Radiant and the SnS extension. Thank >> you. >> >> --danny >> >> > ___ > 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] mailers, which one should I use?
Danny, I was hoping to include a fix for this issue with v0.4 but did not get to it yet. But, for now, you can already solve this issue using the config settings that I have built into the SnS extension (don't know why I didn't think of this sooner). To do this you edit the custom_settings.rb file in the root of the extension. In there you will find instructions and commented-out settings for the stylesheet_directory and javascript_directory (lines 24 & 25 in my latest version). Based on your example, you'd set these to: StylesNScripts::Config[:stylesheet_directory] = 'radiantroot/css' StylesNScripts::Config[:javascript_directory] = 'radiantroot/js' Or if you want to get creative, you could: StylesNScripts::Config[:stylesheet_directory] = 'radiantroot/assets/my-stylesheets' StylesNScripts::Config[:javascript_directory] = 'radiantroot/assets/my-javascripts' Restart your server and everything should just work for you (unless I'm misunderstanding your request here). These settings will automatically adjust caching, rendering, and all the tags. -Chris danny q. wrote: Yes I am using Styles 'n Scripts, and yes, I did notice most of this was fixed in 0.6.5, but IIRC, there were two problems I had to address for the relative link issue. First, with the old-fashioned script and style linking, each had to be set explicitly in the tag. That is, I had to do instead of just href="...". That wasn't a big deal, because it was in layouts which I only had to think about once (but then would have had to remind myself to change before deploying and moving to the url root). I'd hardly call this an issue with radiant. It's just how the html is supposed to work, right? Second, the problem was a general gotcha with extensions. Any extension based on a path relative to / wouldn't work. This included styles-n-scripts, mailer, and, I think calendar. I dug around for a definition of a variable that would fix that, but didn't have much luck, so decided to just go with the .htaccess hack. It works well enough for testing, and I definitely 'get' the whole thing about radiant not being defined for sub-urls. It might be interesting to see how well the root url variable definition would work, but it looks like some of the extensions just assume it's "/" and hard-code that way (based on my shaky RoR reading), so that could limit the mileage a bit. By the way, great work on both Radiant and the SnS extension. Thank you. --danny ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] mailers, which one should I use?
Yes I am using Styles 'n Scripts,
and yes, I did notice most of this was fixed in 0.6.5, but IIRC, there
were two problems I had to address for the relative link issue.
First, with the old-fashioned script and style linking, each had to be
set explicitly in the tag. That is, I had to do instead of just href="...". That wasn't a big
deal, because it was in layouts which I only had to think about once
(but then would have had to remind myself to change before deploying and
moving to the url root). I'd hardly call this an issue with radiant.
It's just how the html is supposed to work, right?
Second, the problem was a general gotcha with extensions. Any extension
based on a path relative to / wouldn't work. This included
styles-n-scripts, mailer, and, I think calendar. I dug around for a
definition of a variable that would fix that, but didn't have much luck,
so decided to just go with the .htaccess hack. It works well enough for
testing, and I definitely 'get' the whole thing about radiant not being
defined for sub-urls.
It might be interesting to see how well the root url variable definition
would work, but it looks like some of the extensions just assume it's
"/" and hard-code that way (based on my shaky RoR reading), so that
could limit the mileage a bit.
By the way, great work on both Radiant and the SnS extension. Thank you.
--danny
Chris Parrish wrote:
> Danny,
>
> Are you using my new Styles 'n Scripts extension. If so, I'm quite
> sure it isn't doing anything to accommodate a different root than
> plain old '/' and will happily break things for you.
>
> I would be happy to change this (for your need, to play nice with the
> multi_site extension, etc).
>
> Sean (or anyone), is there a preferred way to do this so that I honor
> some Radiant::Config (or some such setting)?
>
> -Chris
>
>
> Sean Cribbs wrote:
>> The relative path issue was resolved as best we could in 0.6.5, that
>> is, links in the admin UI will be generated correctly and links and
>> URLs generated from the standard Radius tags will be correct. Are
>> there links otherwise that aren't working for you?
>>
>> Sean
>>
>> danny q. wrote:
>>> I always seem to figure these things out /after/ I post a big long
>>> question to the public. But I did manage to fix it, and I'll write how
>>> for future reference.
>>>
>>> I'd noticed that there are a lot of problems when running on a
>>> subdirectory (e.g. http://somesite.com/radiantroot/). Setting
>>> DocumentRoot in .htaccess partially addresses this, but still leads to
>>> quite a few 404s, especially in generated links to stylesheets and
>>> scripts, and the mailer. This is because radiant or extensions will
>>> generate links to, for example, http://somesite.com/css/stylesheet.css
>>> when they should be linking to
>>> http://somesite.com/radiantroot/css/stylesheet.css.
>>>
>>> I have a partial solution that uses a few .htaccess lines. You drop
>>> the
>>> following in an .htaccess directory above the radiant root (the
>>> public_html for somesite.com/):
>>>
>>> RewriteEngine on
>>> # if the link originates from the radiant directory,
>>> RewriteCond %{HTTP_REFERER} ^.*somesite\.com.*
>>> # rewrite the request, put a '/radiantroot/' before it
>>> RewriteRule (.*)$ http://somesite.com/radiantroot/$1
>>>
>>> You can generalize or specify this to taste, but the above code is what
>>> worked for me. It probably isn't recommended for public deployment,
>>> but
>>> will work for testing on a subdirectory of a root domain. Anyone who
>>> has referers turned off (a feature when 'private browsing' is turned
>>> on)
>>> will still not catch the links properly. Also, make sure the .htaccess
>>> has permissions set to 755.
>>>
>>> If anyone thinks this is worth it, maybe we could drop this hint in the
>>> wiki somewhere, or some other documentation.
>>>
>>> thanks,
>>> --danny
>>>
>>>
>>>
>>> danny q. wrote:
>>>
Hi Radiant list,
I've been getting ready to migrate my current site to radiant, been
running tests on a subdomain. The last step before I switch over
is to
get a mailer contact form up and running, and I just can't seem to
do it.
I know that there've been a lot of updates in the past few weeks,
and I
think I can list my known unknowns as follows:
1. Which mailer extension should I use for 0.6.7? There's the svn
listed in the radiantcms.org wiki, and there's another one in
github. Are either compatible and working with the current
radiant? I've tried
both with no luck.
2. Assuming one of them is compatible, can anyone give me some
updates
to the documentation? I suspect the non-workingness may be more of a
pebkac phenomenon, but I've spent a good amount of time hacking
around,
and can hardly even get a worthwhile error message (even though I
enabled them in environment.rb).
3. What changes should I have to make to get this wo
Re: [Radiant] mailers, which one should I use?
Chris,
I'll have a brief look at it today and let you know... but if you're
using the standard Rails tools, it should "just work".
Sean
Chris Parrish wrote:
Danny,
Are you using my new Styles 'n Scripts extension. If so, I'm quite
sure it isn't doing anything to accommodate a different root than
plain old '/' and will happily break things for you.
I would be happy to change this (for your need, to play nice with the
multi_site extension, etc).
Sean (or anyone), is there a preferred way to do this so that I honor
some Radiant::Config (or some such setting)?
-Chris
Sean Cribbs wrote:
The relative path issue was resolved as best we could in 0.6.5, that
is, links in the admin UI will be generated correctly and links and
URLs generated from the standard Radius tags will be correct. Are
there links otherwise that aren't working for you?
Sean
danny q. wrote:
I always seem to figure these things out /after/ I post a big long
question to the public. But I did manage to fix it, and I'll write how
for future reference.
I'd noticed that there are a lot of problems when running on a
subdirectory (e.g. http://somesite.com/radiantroot/). Setting
DocumentRoot in .htaccess partially addresses this, but still leads to
quite a few 404s, especially in generated links to stylesheets and
scripts, and the mailer. This is because radiant or extensions will
generate links to, for example, http://somesite.com/css/stylesheet.css
when they should be linking to
http://somesite.com/radiantroot/css/stylesheet.css.
I have a partial solution that uses a few .htaccess lines. You drop
the
following in an .htaccess directory above the radiant root (the
public_html for somesite.com/):
RewriteEngine on
# if the link originates from the radiant directory,
RewriteCond %{HTTP_REFERER} ^.*somesite\.com.*
# rewrite the request, put a '/radiantroot/' before it
RewriteRule (.*)$ http://somesite.com/radiantroot/$1
You can generalize or specify this to taste, but the above code is what
worked for me. It probably isn't recommended for public deployment,
but
will work for testing on a subdirectory of a root domain. Anyone who
has referers turned off (a feature when 'private browsing' is turned
on)
will still not catch the links properly. Also, make sure the .htaccess
has permissions set to 755.
If anyone thinks this is worth it, maybe we could drop this hint in the
wiki somewhere, or some other documentation.
thanks,
--danny
danny q. wrote:
Hi Radiant list,
I've been getting ready to migrate my current site to radiant, been
running tests on a subdomain. The last step before I switch over
is to
get a mailer contact form up and running, and I just can't seem to
do it.
I know that there've been a lot of updates in the past few weeks,
and I
think I can list my known unknowns as follows:
1. Which mailer extension should I use for 0.6.7? There's the svn
listed in the radiantcms.org wiki, and there's another one in
github. Are either compatible and working with the current
radiant? I've tried
both with no luck.
2. Assuming one of them is compatible, can anyone give me some
updates
to the documentation? I suspect the non-workingness may be more of a
pebkac phenomenon, but I've spent a good amount of time hacking
around,
and can hardly even get a worthwhile error message (even though I
enabled them in environment.rb).
3. What changes should I have to make to get this working in a
subdirectory of the URL root. The radiant root url is on something
like
http://mysite.com/testing/, which has caused me a little trouble
before,
and might be the source of all my problems here. Is there a site root
variable I should change or define, or perhaps an .htaccess line I
should drop somewhere?
I'd really appreciate some pointers on this. I've been really
impressed
with the community involvement and active development around here, and
it's a big part of why I'm switching to Radiant.
Thanks,
--danny
___
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
Re: [Radiant] mailers, which one should I use?
Danny,
Are you using my new Styles 'n Scripts extension. If so, I'm quite sure
it isn't doing anything to accommodate a different root than plain old
'/' and will happily break things for you.
I would be happy to change this (for your need, to play nice with the
multi_site extension, etc).
Sean (or anyone), is there a preferred way to do this so that I honor
some Radiant::Config (or some such setting)?
-Chris
Sean Cribbs wrote:
The relative path issue was resolved as best we could in 0.6.5, that
is, links in the admin UI will be generated correctly and links and
URLs generated from the standard Radius tags will be correct. Are
there links otherwise that aren't working for you?
Sean
danny q. wrote:
I always seem to figure these things out /after/ I post a big long
question to the public. But I did manage to fix it, and I'll write how
for future reference.
I'd noticed that there are a lot of problems when running on a
subdirectory (e.g. http://somesite.com/radiantroot/). Setting
DocumentRoot in .htaccess partially addresses this, but still leads to
quite a few 404s, especially in generated links to stylesheets and
scripts, and the mailer. This is because radiant or extensions will
generate links to, for example, http://somesite.com/css/stylesheet.css
when they should be linking to
http://somesite.com/radiantroot/css/stylesheet.css.
I have a partial solution that uses a few .htaccess lines. You drop the
following in an .htaccess directory above the radiant root (the
public_html for somesite.com/):
RewriteEngine on
# if the link originates from the radiant directory,
RewriteCond %{HTTP_REFERER} ^.*somesite\.com.*
# rewrite the request, put a '/radiantroot/' before it
RewriteRule (.*)$ http://somesite.com/radiantroot/$1
You can generalize or specify this to taste, but the above code is what
worked for me. It probably isn't recommended for public deployment, but
will work for testing on a subdirectory of a root domain. Anyone who
has referers turned off (a feature when 'private browsing' is turned on)
will still not catch the links properly. Also, make sure the .htaccess
has permissions set to 755.
If anyone thinks this is worth it, maybe we could drop this hint in the
wiki somewhere, or some other documentation.
thanks,
--danny
danny q. wrote:
Hi Radiant list,
I've been getting ready to migrate my current site to radiant, been
running tests on a subdomain. The last step before I switch over is to
get a mailer contact form up and running, and I just can't seem to
do it.
I know that there've been a lot of updates in the past few weeks, and I
think I can list my known unknowns as follows:
1. Which mailer extension should I use for 0.6.7? There's the svn
listed in the radiantcms.org wiki, and there's another one in
github. Are either compatible and working with the current radiant?
I've tried
both with no luck.
2. Assuming one of them is compatible, can anyone give me some updates
to the documentation? I suspect the non-workingness may be more of a
pebkac phenomenon, but I've spent a good amount of time hacking around,
and can hardly even get a worthwhile error message (even though I
enabled them in environment.rb).
3. What changes should I have to make to get this working in a
subdirectory of the URL root. The radiant root url is on something
like
http://mysite.com/testing/, which has caused me a little trouble
before,
and might be the source of all my problems here. Is there a site root
variable I should change or define, or perhaps an .htaccess line I
should drop somewhere?
I'd really appreciate some pointers on this. I've been really
impressed
with the community involvement and active development around here, and
it's a big part of why I'm switching to Radiant.
Thanks,
--danny
___
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] mailers, which one should I use?
The relative path issue was resolved as best we could in 0.6.5, that is,
links in the admin UI will be generated correctly and links and URLs
generated from the standard Radius tags will be correct. Are there
links otherwise that aren't working for you?
Sean
danny q. wrote:
I always seem to figure these things out /after/ I post a big long
question to the public. But I did manage to fix it, and I'll write how
for future reference.
I'd noticed that there are a lot of problems when running on a
subdirectory (e.g. http://somesite.com/radiantroot/). Setting
DocumentRoot in .htaccess partially addresses this, but still leads to
quite a few 404s, especially in generated links to stylesheets and
scripts, and the mailer. This is because radiant or extensions will
generate links to, for example, http://somesite.com/css/stylesheet.css
when they should be linking to
http://somesite.com/radiantroot/css/stylesheet.css.
I have a partial solution that uses a few .htaccess lines. You drop the
following in an .htaccess directory above the radiant root (the
public_html for somesite.com/):
RewriteEngine on
# if the link originates from the radiant directory,
RewriteCond %{HTTP_REFERER} ^.*somesite\.com.*
# rewrite the request, put a '/radiantroot/' before it
RewriteRule (.*)$ http://somesite.com/radiantroot/$1
You can generalize or specify this to taste, but the above code is what
worked for me. It probably isn't recommended for public deployment, but
will work for testing on a subdirectory of a root domain. Anyone who
has referers turned off (a feature when 'private browsing' is turned on)
will still not catch the links properly. Also, make sure the .htaccess
has permissions set to 755.
If anyone thinks this is worth it, maybe we could drop this hint in the
wiki somewhere, or some other documentation.
thanks,
--danny
danny q. wrote:
Hi Radiant list,
I've been getting ready to migrate my current site to radiant, been
running tests on a subdomain. The last step before I switch over is to
get a mailer contact form up and running, and I just can't seem to do it.
I know that there've been a lot of updates in the past few weeks, and I
think I can list my known unknowns as follows:
1. Which mailer extension should I use for 0.6.7? There's the svn
listed in the radiantcms.org wiki, and there's another one in github.
Are either compatible and working with the current radiant? I've tried
both with no luck.
2. Assuming one of them is compatible, can anyone give me some updates
to the documentation? I suspect the non-workingness may be more of a
pebkac phenomenon, but I've spent a good amount of time hacking around,
and can hardly even get a worthwhile error message (even though I
enabled them in environment.rb).
3. What changes should I have to make to get this working in a
subdirectory of the URL root. The radiant root url is on something like
http://mysite.com/testing/, which has caused me a little trouble before,
and might be the source of all my problems here. Is there a site root
variable I should change or define, or perhaps an .htaccess line I
should drop somewhere?
I'd really appreciate some pointers on this. I've been really impressed
with the community involvement and active development around here, and
it's a big part of why I'm switching to Radiant.
Thanks,
--danny
___
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] mailers, which one should I use?
I always seem to figure these things out /after/ I post a big long
question to the public. But I did manage to fix it, and I'll write how
for future reference.
I'd noticed that there are a lot of problems when running on a
subdirectory (e.g. http://somesite.com/radiantroot/). Setting
DocumentRoot in .htaccess partially addresses this, but still leads to
quite a few 404s, especially in generated links to stylesheets and
scripts, and the mailer. This is because radiant or extensions will
generate links to, for example, http://somesite.com/css/stylesheet.css
when they should be linking to
http://somesite.com/radiantroot/css/stylesheet.css.
I have a partial solution that uses a few .htaccess lines. You drop the
following in an .htaccess directory above the radiant root (the
public_html for somesite.com/):
RewriteEngine on
# if the link originates from the radiant directory,
RewriteCond %{HTTP_REFERER} ^.*somesite\.com.*
# rewrite the request, put a '/radiantroot/' before it
RewriteRule (.*)$ http://somesite.com/radiantroot/$1
You can generalize or specify this to taste, but the above code is what
worked for me. It probably isn't recommended for public deployment, but
will work for testing on a subdirectory of a root domain. Anyone who
has referers turned off (a feature when 'private browsing' is turned on)
will still not catch the links properly. Also, make sure the .htaccess
has permissions set to 755.
If anyone thinks this is worth it, maybe we could drop this hint in the
wiki somewhere, or some other documentation.
thanks,
--danny
danny q. wrote:
> Hi Radiant list,
>
> I've been getting ready to migrate my current site to radiant, been
> running tests on a subdomain. The last step before I switch over is to
> get a mailer contact form up and running, and I just can't seem to do it.
>
> I know that there've been a lot of updates in the past few weeks, and I
> think I can list my known unknowns as follows:
>
> 1. Which mailer extension should I use for 0.6.7? There's the svn
> listed in the radiantcms.org wiki, and there's another one in github.
> Are either compatible and working with the current radiant? I've tried
> both with no luck.
>
> 2. Assuming one of them is compatible, can anyone give me some updates
> to the documentation? I suspect the non-workingness may be more of a
> pebkac phenomenon, but I've spent a good amount of time hacking around,
> and can hardly even get a worthwhile error message (even though I
> enabled them in environment.rb).
>
> 3. What changes should I have to make to get this working in a
> subdirectory of the URL root. The radiant root url is on something like
> http://mysite.com/testing/, which has caused me a little trouble before,
> and might be the source of all my problems here. Is there a site root
> variable I should change or define, or perhaps an .htaccess line I
> should drop somewhere?
>
> I'd really appreciate some pointers on this. I've been really impressed
> with the community involvement and active development around here, and
> it's a big part of why I'm switching to Radiant.
>
> Thanks,
> --danny
>
> ___
> 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] mailers, which one should I use?
Hi Radiant list, I've been getting ready to migrate my current site to radiant, been running tests on a subdomain. The last step before I switch over is to get a mailer contact form up and running, and I just can't seem to do it. I know that there've been a lot of updates in the past few weeks, and I think I can list my known unknowns as follows: 1. Which mailer extension should I use for 0.6.7? There's the svn listed in the radiantcms.org wiki, and there's another one in github. Are either compatible and working with the current radiant? I've tried both with no luck. 2. Assuming one of them is compatible, can anyone give me some updates to the documentation? I suspect the non-workingness may be more of a pebkac phenomenon, but I've spent a good amount of time hacking around, and can hardly even get a worthwhile error message (even though I enabled them in environment.rb). 3. What changes should I have to make to get this working in a subdirectory of the URL root. The radiant root url is on something like http://mysite.com/testing/, which has caused me a little trouble before, and might be the source of all my problems here. Is there a site root variable I should change or define, or perhaps an .htaccess line I should drop somewhere? I'd really appreciate some pointers on this. I've been really impressed with the community involvement and active development around here, and it's a big part of why I'm switching to Radiant. Thanks, --danny ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
