Thanks Sean!
Does it mean that each time in update my copy of Radiant, I'll have to edit
and modify mailer_behavior.rb?
On 1/14/07, Sean Cribbs [EMAIL PROTECTED] wrote:
When I converted the Mailer behavior into an extension, I had to deal
with that. The code is pretty straightforward, just
Jonathan Métillon wrote:
Thanks Sean!
Does it mean that each time in update my copy of Radiant, I'll have to
edit and modify mailer_behavior.rb?
Yes. Basically you can search for POST and replace that pretty
easily. There are some other bugs in it, though, that I had to fix
(like
Sorry if it's a newbie reply, but why is this not fixed definitely, so we
don't have to fix it at each update?
On 1/24/07, Sean Cribbs [EMAIL PROTECTED] wrote:
Jonathan Métillon wrote:
Thanks Sean!
Does it mean that each time in update my copy of Radiant, I'll have to
edit and modify
Boris wrote:
John W. Long [EMAIL PROTECTED] writes:
The Radiant admin will probably always require Javascript.
So I will probably never be able to use radiant :-(
While it saddens me that you can't find a Ruby solution to meet your
needs, I'm afraid I have to fall back on the old excuse
Hi there,
I wanted to ask if it's possible to run Radiant with the Relative Path
Plugin?
Regards,
Christof
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:
Did not think about that. But according to
http://www.nabble.com/help/Answer.jtp?id=21 it seems pretty easy.
Sorry I don't have the time for it today. Perhaps on Saturday.
Erik.
John W. Long wrote:
Erik van Oosten wrote:
For all forum fans out there: the three radiant lists have been
I came as far as what is copied below here.
A big problem is that the background should really be white as the
Nabble images have a white background. The footer is not correct yet,
perhaps a missing /div.
Feel free to continue where I left off.
Regards,
Erik.
The admin pages should work with the relative path plugin, but the
actual site itself might be an issue because it doesn't actually use
url_for, which is what the relative path plugin hooks into. Oh, and by
the way, you'd be using a ReverseProxy directive in apache, not an
Alias.
The problem