The Radiant layout is the default. I found it was active immediately.
Perhaps it works when you do not write a layout yourself?
Regards,
Erik.
Raphael Bauduin wrote:
- you can't use a radiant layout for your extension views
--
Erik van Oosten
http://2007.rubyenrails.nl/
On 29/05/07 05:48 AM, Keith Bingman was heard to say:
This isn't really a radiant problem, but maybe one of you can help
me. I have been forced to use iframes because the client wants music
on the site. Now he wants links to specific pages, which of course
poses a problem. Does anyone
Yes. That is clear. I am trying to link directly to a page with an
iFrame from an external link. Basically a bookmark. I think I know
how to do it, but thought I see if there was something I was
overlooking. Doesn't seem to be.
Keith Bingman
Tel: +49-7731-79838380
[EMAIL PROTECTED]
This is what I was thinking of doing, though perhaps as a Virtual
page. My Ruby is better than my javascript... But I will give it a
thought. Thanks!
Keith Bingman
Tel: +49-7731-79838380
[EMAIL PROTECTED]
http://keithbingman.com
On May 29, 2007, at 4:47 PM, Oliver Baltzer wrote:
Keith
Basically, it sounds to me as if you are trying to load a page which
contains an iFrame, and then programmatically direct that iFrame to
load a different source than its default. If I were doing it in PHP
(sorry) I would script the iFrame to load a sanitized version of a
querystring variable.
Yes, this is exactly what I am trying to do.
My basic plan at the moment is to make a Virtual Page type for the
mian pae (with the iFrame) and grab the query string. Then I can just
reset the source of the iFrame or redirect the page. Hopefully, that
will work.
You guys have helped a lot,
Ok, so I think I tracked down something a little bit more useful...
After going through the trace, I opened up
#{RADIANT_ROOT}/test/test_helper.rb. After commenting a couple of
lines I suspected, I found that commenting line #13 ( require
'test_help' ) allowed my tests to run. (These are the
Ok, I think I finally figured it out: there's a missing file in the
Rails distribution packaged in Radiant. It's present in the
repository, but not in the gem or tgz on Rubyforge.
Not sure how it got excluded, but when I copied the code from
Ok, I can't find the solution to this problem. I have implemented the
suggestion from Oliver [http://lists.radiantcms.org/pipermail/radiant/
2007-May/004927.html] to control extension load order, but my
customized render call isn't overwriting the default SearchPage one.
When I look at the
Francesco,
It will help if you can post the code snippet with the nested
r:children:each ... tags in it to look at. If I am understanding
what you're describing correctly, yes I'd expect it to work as well.
If you're still stuck post that section of code and maybe I can help
more.
Loren
10 matches
Mail list logo
