[Radiant] Admin hierarchy vs. URL hierarchy?
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 they don't dirty up my main Pages display. But I still want them to be at http://example.com/search and http://example.com/rss. Are there any extensions that let me specify where the slug is rooted? This is purely out of laziness and aesthetic sensibility; it's not worth me hard-coding stuff into routes. Jay ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Rspec version error
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 use the gem. Of course, then the gem will not match rspec_on_rails, unless of course it does. The only way to fix this is to get a 'vendor/plugins/rspec' in your project directory, and then go to the command line and 'mate that/directory'. adam On Jun 7, 2008, at 12:49 AM, Marty Haught wrote: Does anyone else get the incompatible version error when running rspec for their extensions? I can get it to run fine from command line but if I run it through Textmate, I get the error. I do have rspec installed as a gem which is why the version is off. If I uninstall rspec then Textmate has issues (can't find spec). Part of the problem could be that I'm running radiant through the gem and Textmate isn't looking in radiant for the rspec plugins. Before diving any deeper into the issue I figured I'd ask the list to see if others already have a solution. Also, does anyone else find this check a bit over the top? I mean do the builds really need to be identical? Shouldn't a newer version of rspec be okay? It just feel too brittle. Maybe they should just combine rspec and rspec on rails into the same plugin so they have to be the same. Cheers, Marty ___ 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] Best way to refer to a stylesheet?
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 refer to a stylesheet ? My stylesheets work fine when I refer to them as files in the filesystem, but not when they are in the database. John -- John Allen Bofferdange, Luxembourg [EMAIL PROTECTED] http://allenlux.dyndns.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] And what happened to the clear page cache button?
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 database? John -- John Allen Bofferdange, Luxembourg [EMAIL PROTECTED] http://allenlux.dyndns.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] And what happened to the clear page cache button?
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 media=screen / Here I have a hidden page with the slug of css, and below that, I have a stylesheet page with the slug set to standard.css. Cheers, Casper Fabricius http://casperfabricius.com On 07/06/2008, at 15:35, John and Catherine Allen wrote: 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 database? John -- John Allen Bofferdange, Luxembourg [EMAIL PROTECTED] http://allenlux.dyndns.org ___ 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] ActionController::InvalidAuthenticityToken in Radiant Admin
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: /home/inf_sto_2/frycu/public_html/aniol_radiant
Application Trace | Framework Trace | Full Trace
Request
Parameters:
{level=2,
id=5}
Show session dump
---
:return_to:
user_id: 1
flash: !map:ActionController::Flash::FlashHash {}
Response
Headers:
{cookie=[],
Cache-Control=no-cache}
and when I refresh admin site its showing childrens...
but I want to work it right, any ideas?
--
Posted via http://www.ruby-forum.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] Rspec version error
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 for 'vendor/plugins/rspec'. If there, it will use that rspec to run your code. If not, it will use the gem. Of course, then the gem will not match rspec_on_rails, unless of course it does. The only way to fix this is to get a 'vendor/plugins/rspec' in your project directory, and then go to the command line and 'mate that/directory'. adam On Jun 7, 2008, at 12:49 AM, Marty Haught wrote: Does anyone else get the incompatible version error when running rspec for their extensions? I can get it to run fine from command line but if I run it through Textmate, I get the error. I do have rspec installed as a gem which is why the version is off. If I uninstall rspec then Textmate has issues (can't find spec). Part of the problem could be that I'm running radiant through the gem and Textmate isn't looking in radiant for the rspec plugins. Before diving any deeper into the issue I figured I'd ask the list to see if others already have a solution. Also, does anyone else find this check a bit over the top? I mean do the builds really need to be identical? Shouldn't a newer version of rspec be okay? It just feel too brittle. Maybe they should just combine rspec and rspec on rails into the same plugin so they have to be the same. Cheers, Marty ___ 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] Questions about deployment
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 about the best way to do that. Railsplayground's stellar [cough] documentation has, once again, not failed to disappoint. 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 easy... and as long as you use the same database, it's easy to migrate/ manage the databases also. I'm going to probably try to deploy to Railsplayground in a few days myself (I've currently got 2 sites working on HostingRails - and it works great). Cheers, Mohit. 6/8/2008 | 1:18 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can't log into wiki?
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 already been taken. Well, yes - by me, when I logged in yesterday... I'm still seeing this, on both Firefox 3.0 nightly and Safari 3.1... ideas? Jay ___ 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] Questions about deployment
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 easy. Actually it doesn't help much. That page on the railsplayground wiki describes the process to *install* Radiant CMS, not how to deploy it. Casper's tutorial gets me most of the way there, and I'll just modify my old Cap recipe to get it working with RP. I was just curious how everybody was managing their projects. It seems that Radiant is close enough to a normal Rails project that it can be managed the same way with svn or git. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] downloading radiant from github
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 4. look at the folder and there is only the accent folder Anybody know of a possible problem here? Is it me? GitHub? Also, I can do a git clone and pull everything down just fine. Thanks, Jason ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] any way to dynamically populate r:random?
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
I had a go at this too, but couldn't get it to work either. I had a
look at the code and the specs (both pasted below), but couldn't
figure out why this wouldn't work. It seems to me like this is a
perfect example of where the r:random tag would be useful, but the
spec doesn't currently test such a scenario.
I thought of an alternative approach which might be easier to
implement. Here is an example:
r:find url=/quotations
r:children:each limit=1 order=rand
r:content part=body/
/r:children:each
/r:find
This doesn't work at the moment, because the order attribute can only
be asc or desc. I think it would be pretty easy to add the option for
random order though.
Cheers,
Drew
---
app//models/standard_tags.rb
desc %{
Randomly renders one of the options specified by the @option@ tags.
*Usage:*
precoder:random
r:option.../r:option
r:option.../r:option
...
r:random
/code/pre
}
tag 'random' do |tag|
tag.locals.random = []
tag.expand
options = tag.locals.random
option = options[rand(options.size)]
option.call if option
end
tag 'random:option' do |tag|
items = tag.locals.random
items tag.block
end
---
spec/models/standard_tags_spec.rb
it 'r:random should render a randomly selected contained
r:option' do
page.should render(r:random r:option1/r:option
r:option2/r:option r:option3/r:option /r:random).matching(/
^(1|2|3)$/)
end
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can't log into wiki?
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 (username = JayLevitt), it tells me Username has already been taken. Well, yes - by me, when I logged in yesterday... I'm still seeing this, on both Firefox 3.0 nightly and Safari 3.1... ideas? You'll get the error message Username has already been taken if the password you provide is incorrect. So my guess is that you're simply entering the wrong password. -- Sincerely, Bjorn Michelsen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Best way to refer to a stylesheet?
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 name=my_stylesheet.css as=link / generates: link rel=stylesheet href=/css/my_stylesheet.css type=text/css / while... r:stylesheet name=my_stylesheet.css as=url / generates: /css/my_stylesheet.css Of course the /css directory in the examples is the extension's default but you can change that to whatever you want. You can also use these tags to pull the content from a stylesheet of javascript into your document's head section. -Chris John and Catherine Allen wrote: 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 refer to a stylesheet ? My stylesheets work fine when I refer to them as files in the filesystem, but not when they are in the database. John ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] any way to dynamically populate r:random?
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: 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 I thought of an alternative approach which might be easier to implement. Here is an example: r:find url=/quotations r:children:each limit=1 order=rand r:content part=body/ /r:children:each /r:find This doesn't work at the moment, because the order attribute can only be asc or desc. I think it would be pretty easy to add the option for random order though. I was going to try putting together a patch to add rand as an order option, but as far as I can tell the ASC and DESC ordering is part of ActiveRecord and that seems like the wrong place to apply a patch for Radiant. Am I way off base here or are the ordering options, in fact, part of ActiveRecord? ___ 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] any way to dynamically populate r:random?
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 that demonstrates the difference would be appreciated! Sean Sean Cribbs wrote: 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: 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 I thought of an alternative approach which might be easier to implement. Here is an example: r:find url=/quotations r:children:each limit=1 order=rand r:content part=body/ /r:children:each /r:find This doesn't work at the moment, because the order attribute can only be asc or desc. I think it would be pretty easy to add the option for random order though. I was going to try putting together a patch to add rand as an order option, but as far as I can tell the ASC and DESC ordering is part of ActiveRecord and that seems like the wrong place to apply a patch for Radiant. Am I way off base here or are the ordering options, in fact, part of ActiveRecord? ___ 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] Rspec version error
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. 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 for 'vendor/plugins/rspec'. If there, it will use that rspec to run your code. If not, it will use the gem. Of course, then the gem will not match rspec_on_rails, unless of course it does. The only way to fix this is to get a 'vendor/plugins/rspec' in your project directory, and then go to the command line and 'mate that/directory'. adam On Jun 7, 2008, at 12:49 AM, Marty Haught wrote: Does anyone else get the incompatible version error when running rspec for their extensions? I can get it to run fine from command line but if I run it through Textmate, I get the error. I do have rspec installed as a gem which is why the version is off. If I uninstall rspec then Textmate has issues (can't find spec). Part of the problem could be that I'm running radiant through the gem and Textmate isn't looking in radiant for the rspec plugins. Before diving any deeper into the issue I figured I'd ask the list to see if others already have a solution. Also, does anyone else find this check a bit over the top? I mean do the builds really need to be identical? Shouldn't a newer version of rspec be okay? It just feel too brittle. Maybe they should just combine rspec and rspec on rails into the same plugin so they have to be the same. Cheers, Marty ___ 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] any way to dynamically populate r:random?
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 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 that demonstrates the difference would be appreciated! Sean Sean Cribbs wrote: 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: 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 I thought of an alternative approach which might be easier to implement. Here is an example: r:find url=/quotations r:children:each limit=1 order=rand r:content part=body/ /r:children:each /r:find This doesn't work at the moment, because the order attribute can only be asc or desc. I think it would be pretty easy to add the option for random order though. I was going to try putting together a patch to add rand as an order option, but as far as I can tell the ASC and DESC ordering is part of ActiveRecord and that seems like the wrong place to apply a patch for Radiant. Am I way off base here or are the ordering options, in fact, part of ActiveRecord? ___ 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
