I *think* the answer is no but:
Is there an easy way to separate the administrative hierarchy
(parent/children) from the URL hierarchy, without getting into mod_rewrite
or Rails routing?
For instance, I'd like to tuck some of the administrative pages (about,
search, RSS) into a folder so
This is SUPER annoying to me, as well. It has cost me too much time
over the last year of my life.
If you look at the TextMate bundle, you'll see that it looks in the
current working directory for 'vendor/plugins/rspec'. If there, it
will use that rspec to run your code. If not, it will
This has to be a really basic question, but despite reading the
documentation and many mailing list posts, I still don't get it...
For stylesheets which are stored in the database
1) In a layout, what is the recommended way to refer to a stylesheet ?
2) In a page, what is the recommended way to
Another beginner question:
The older (?) Radiant documentation refers to a clear page cache
button on the admin page.
My Radiant 0.6.7 sites don't have this button - I am right in thinking
this is because Radiant now automatically clears the page cache when
something is changed in the
Yes, that's right, John. Clearing of the page cache is done
automatically upon changes.
With regards to your stylesheet question, I tend to just write a
standard link tag, referring to the slug of the stylesheet. For
instance:
link rel=stylesheet href=/css/standard.css type=text/css
Hello,
I have small problem with my Radiant CMS Admin...
When I try unroll list with childrens, it starts to put such
communication:
ActionController::InvalidAuthenticityToken in
Admin/pageController#children
ActionController::InvalidAuthenticityToken
RAILS_ROOT:
One could symlink that directory to the gem or vendor/radiant version.
Sean
Adam Williams wrote:
This is SUPER annoying to me, as well. It has cost me too much time
over the last year of my life.
If you look at the TextMate bundle, you'll see that it looks in the
current working directory
Mohit Sindhwani wrote:
[EMAIL PROTECTED] wrote:
I am new to Radiant and even newer to deploying Radiant sites, and the
documentation I can find helps little. I have two apps running well on
my laptop but it's time to get them up on my shared hosting account at
Railsplayground and I am unsure
Jay Levitt wrote:
At wiki.radiantcms.org, when I try to Sign In, it takes me to
http://wiki.radiantcms.org/login?return_to=/Documentation.
That gives me the Login/Create Account screen, with Username and
Password fields.
When I fill those in (username = JayLevitt), it tells me Username has
On Sun, 2008-06-08 at 01:18 +0800, Mohit Sindhwani wrote:
Has this not helped?
http://wiki.railsplayground.com/railsplayground/show/How+To+Install+RadiantCMS
I realize that the message may sound curt, so I apologize if it does. I
have found that a basic Radiant install is
Still a newbie on git and using github, so please bare with me...
I am trying to pull down the radiant files only, but I only get the
accent folder.
What I do is
1. Go to url http://github.com/seancribbs/radiant/tree/master
2. Click the download button
3. unzip the tar.gz file that is download
On 6 Jun 2008, at 01:01, john muhl wrote:
I'd like to insert part of a random subpage into the sidebar and
figured it'd be a good fit for the r:random tag but so far am
having very little luck. I've tried:
r:random
r:children:each
r:optionr:title//r:option
/r:children:each
/r:random
On Sat, 7 Jun 2008, Jay Levitt wrote:
Jay Levitt wrote:
At wiki.radiantcms.org, when I try to Sign In, it takes me to
http://wiki.radiantcms.org/login?return_to=/Documentation.
That gives me the Login/Create Account screen, with Username and
Password fields.
When I fill those in
I see that Casper already sent a reply but I thought I'd mention the
Styles 'n Scripts extension here since it was made to make things like
this simpler. You would simply use the r:stylesheet or r:javascript
tag in your Page/Layout/Snippet to render the thing you want:
r:stylesheet
This one has always been a mystery to me, however I believe it has to do
with tag blocks versus expands. I imagine, however, we could produce a
failing spec to demonstrate what is unexpected about the behavior. Any
takers?
Sean
john muhl wrote:
On 2008/06/07, at 16:49, Andrew Neil wrote:
Actually, I just answered my own question. We should really be
rendering the contents of r:option at each pass, rather than passing
the block back. The reason is that local context (tag.locals) will be
potentially lost when you render the block after selecting the option.
However, a spec
Thanks guys,
I made a symlink to the rspec in Radiant's gem. It's got me working
but I wish I didn't have to do this. I feel dirty... ;)
Cheers,
Marty
On Sat, Jun 7, 2008 at 10:49 AM, Sean Cribbs [EMAIL PROTECTED] wrote:
One could symlink that directory to the gem or vendor/radiant version.
I guess Sunday is as good a day as any to get to know rspec. Unless
someone beats me to it I send a pull request when I think I have
something useful.
On 2008/06/07, at 20:35, Sean Cribbs wrote:
Actually, I just answered my own question. We should really be
rendering the contents of
18 matches
Mail list logo
