Feature Request

I have 1 seemingly minor feature requests.

  • There is a “Clear Cache” button on the “Pages” tab. Is it at all
    possible to duplicate that button the “Snippets” and “Layout” tabs
    also? Very often when one is experimenting with a new snippet or
    layout, there’s a need to clear cache since the changes do not propagate
    through automatically. It’s very distracting to save changes, go to the
    pages tab, clear cache and then do a reload. In fact, I have 2 admin
    windows open with one on Pages just to clear cache. I wonder if others
    would also find this useful.

Thanks,
Mohit.

would also find this useful.
Editing a layout or snippet automatically clears the whole cache -
there’s no manual step needed.

Daniel S. wrote:

would also find this useful.

Editing a layout or snippet automatically clears the whole cache - there’s no manual step needed.

Hi Daniel,

I did not know that!! Thanks!

However, I do seem to notice that when I change a snippet (radiant rev
575), it does not seem to expire the cache. I get the same page when I
do a refresh - I even got the same page when I clicked on ‘expire page
cache’ in that case. In fact, I had to change the page that I was
looking at and save it. Then, the cache was expired.

I wonder if someone else is noticing the same?

Cheers,
Mohit.
11/9/2007 | 3:41 PM.

I usually have two domains for my radiants site, the foo.com and
dev.foo.com, in the case the domain starts with “dev.” no caching
is ever
done.

That sounds like a good solution. Is there a tutorial somewhere on
how to do this?

Do both sites (site.com and dev.site.com) run off the same database,
or do you run site_development on dev.site.com and site_production on
site.com?

Thanks,

A

±Le 09/11/07 15:41 +0800, Mohit S. a dit :
| However, I do seem to notice that when I change a snippet (radiant rev
| 575), it does not seem to expire the cache. I get the same page when I
| do a refresh - I even got the same page when I clicked on ‘expire page
| cache’ in that case. In fact, I had to change the page that I was
| looking at and save it. Then, the cache was expired.

Well, the cache is expired, but your browser got a expires header the
last
time it asked for the page. (Which is 5 minutes in the future by
default.)
If that time has not come, and you don’t force the reload in your
browser,
it won’t.

I usually have two domains for my radiants site, the foo.com and
dev.foo.com, in the case the domain starts with “dev.” no caching is
ever
done.

Regards,

±le 09.11.2007 12:08:47 +0000, Andrew N. a dit :
|
|> I usually have two domains for my radiants site, the foo.com and
|> dev.foo.com, in the case the domain starts with “dev.” no caching
|> is ever
|> done.
|
| That sounds like a good solution. Is there a tutorial somewhere on
| how to do this?
|
| Do both sites (site.com and dev.site.com) run off the same database,
| or do you run site_development on dev.site.com and site_production on
| site.com?

They both go to the same mongrel cluster, they’re just two different
apache
virtualhost so that my going to dev.* don’t bloat the log files.

The development site with de development database is just a single
mongrel
running on another port.

Mathieu A. wrote:

it won’t.

I usually have two domains for my radiants site, the foo.com and
dev.foo.com, in the case the domain starts with “dev.” no caching is ever
done.

Regards,

Hi! Thanks for the explanation - it does make sense. Unfortunately,
the dev.example.com won’t work for me cos Radiant is currently hosted on
a sub-domain for me.

For example, Radiant runs the site on radiant.example.com
I wonder if I created dev.example.com and pointed the dev to the public
of the radiant directory, if it would work… That way, when Radiant
looks at it, it sees dev as the subdomain.

I guess I should try it when I get the time - thanks for the help guys!

Cheers,
Mohit.
11/10/2007 | 2:00 PM.

±Le 10/11/07 16:31 +0900, Mark G. a dit :
| Mohit S. wrote:
|> Hi! Thanks for the explanation - it does make sense. Unfortunately,
|> the dev.example.com won’t work for me cos Radiant is currently hosted on
|> a sub-domain for me.
|>
|
| I thought it was possible to specify the host name for the development
| site in the Radiant config. Can anyone confirm?

Absolutely, the dev.host config directive is for.

Mohit S. wrote:

Hi! Thanks for the explanation - it does make sense. Unfortunately,
the dev.example.com won’t work for me cos Radiant is currently hosted on
a sub-domain for me.

I thought it was possible to specify the host name for the development
site in the Radiant config. Can anyone confirm?

Cheers,
Mark

Mathieu A. wrote:

Absolutely, the dev.host config directive is for.

Hi Everyone,

Sorry to be a bother, but I’ve just spent 20 minutes looking through the
files in
{RADIANT_APP}/config trying to find the setting. I think I’m missing
something.

If someone is using it, could you please let me know which file it goes
into and what it looks like there.

Sorry again & thanks,
Mohit.

Mohit,

Add these lines to the bottom of your config/environment.rb:

require ‘radiant/config’
Radiant::Config[‘dev.host’] = “somehostname.com

Sean

Mathieu A. wrote:

Absolutely, the dev.host config directive is for.

Fantastic! Thanks guys,

Mohit.

Sean C. wrote:

Mohit,

Add these lines to the bottom of your config/environment.rb:

require ‘radiant/config’
Radiant::Config[‘dev.host’] = “somehostname.com

Sean

Thanks a lot, Sean!

Cheers,
Mohit.
11/11/2007 | 3:24 AM.