It is possible that it was using #{RAILS_ROOT}/public as the cache directory and clearing the cache deleted items in your /public directory. In development mode you should see changes immediately, but even so, I would say put that line back in environment.rb and see what happens.

Cheers,
Sean

Andreas Semt wrote:
@Sean,
@Ruben,

it was not my intent to be inflammatory, really.
Please consider: I've commented out line 44 of
'config/environment.rb' (line 44:
config.action_controller.page_cache_directory = "#{RAILS_ROOT}/cache").
Perhaps that is a subtle distinction to your setup. I made that to see
changes in children of pages without clicking 'Clear page cache' first.

If i have time i will look at the source code (after finishing the client project).


Best regards,
Andreas Semt


Sean Cribbs schrieb:
Andreas,

I have used Radiant in all its released versions and the mental branch, and I can assure you that it DOES NOT delete any files in public/ for any reason, whether in development or production mode. Check your system settings, make sure that some other process, cron job or system tool hasn't "cleaned" the folder. Rather than being inflammatory, it would help more if you could identify offending lines of code or trace the evidence of your problem and submit the results as a trouble ticket on the Trac. I'm sorry you are having difficulty with it, but we can help you better if you provide more information.

Sean Cribbs
seancribbs.com

Andreas Semt wrote:
@Ruben:

Not good.
I've created a new Radiant site 'test_site' and a mysql database
'test_site'. Then i filled the development tables with
'script/setup_database development'. I use the option 3, full
featured blog. Starting: 'mongrel_rails start -e development'.
I use the browser to see the new blog website, all fine.
Then logging in to the admin interface of Radiant and change the
blog title. Save that change ('Save changes') and BANG! All files in
'<test_site-root>/public' (except for 'styles.css', '.htaccess',
'index.yml') are gone ...
In development mode Rails caching (thus Radiant caching) is
general deactivated.
I believe the caching of Radiant needs some improvements.

So: *DON'T USE RADIANT IN DEVELOPMENT MODE FOR WEBSITE CONSTRUCTION!*

 From the presentation of the
'Denver Derailed meeting September 27, 2006' by Nathan Wright:

"Please note that because Radiant is already a complete and tested application, we will NOT be running it in development mode; instead we will be using production mode. Radiant is significantly faster in production mode, and it is only in production mode that page caching takes place."


Greetings,
Andreas Semt

Ruben D. Orduz schrieb:
Andreas,

Can you try ommiting the "-e production" flag when starting either
Mongrel or WEBrick? Or try replacing it with "-e development"? Still I
think it's REALLY weird that your files in public are gone...that's
baffling.

Happy new year to you too!


On 12/31/06, Andreas Semt <[EMAIL PROTECTED]> wrote:
Hi Ruben,

same behavior with Webrick:
My startup command (location: '<Radiant-root>'):
'sudo ruby script/server webrick -e production'.
The only files still in '<Radiant-root>/public'
(after 'Clear page cache') are 'index.yml' and
'.htaccess'.
Wanna try for yourself (i have no Apache-FCGI setup) ;-\ ?

*A happy and healthy new year to all list members!*


Best regards,
Andreas Semt


Ruben D. Orduz schrieb:
Hi Andreas,

I'm at a loss here, cause 1) am not sure why you're losing your files
inside RAILS_ROOT/public and 2)am not too familiar with the
ideocincracies of Mongrel. I run all my apps with Apache/FCGI and
works pretty good--and it has never erased any of my files.

It's a scary thought that a web server (Mongrel) can -- and does --
delete physical files from the file system with a change of settings.
I'd look into Mongrel documentation, instead of Radiant, IMO.



On 12/31/06, Andreas Semt <[EMAIL PROTECTED]> wrote:
@Ruben:

I have to correct something:
My start command for Radiant is:
'sudo mongrel_rails start -e production'.
So I believe i use Radiant in 'production mode'
(unlike 'development mode'), yet i developing
the website (my meaning of 'during
development'). That's not the preferred
way of working with a Rails app, isn't it?

However: If i deactivate the caching (in 'environment.rb')
and then start Radiant with 'sudo mongrel_rails start -e production'
and then click the 'Clear page cache' button in the admin interface
and then loosing most files in '<Radiant-root>/public/' ... looks still
like a malpractice to me.


Best regards,
Andreas Semt


Ruben D. Orduz schrieb:
errr...being in development mode should do nothing to your file
system. That is really, really, really weird.

PS.: You all Radiantists have a happy and safe new year.

On 12/30/06, Andreas Semt <[EMAIL PROTECTED]> wrote:
Thanks!

it works ...
BUT:
After deactivation of the caching mechanism i clicked the
'Clear page cache' button ... oh my!
Only the files '.htaccess' and 'index.yml' are still in
the 'public' directory under the radiant root dir. *All*
other files - inclusive the 'images' subdirectory - are
gone. Is that a feature???


Best regards,
Andreas Semt


Ruben D. Orduz schrieb:
Andreas,

I believe if you comment line 8 of environment.rb and restart your web
server it will, be default, not cache pages.



On 12/29/06, Andreas Semt <[EMAIL PROTECTED]> wrote:
Hello list!

Is it possible to disable the page caching mechanism
during development of a Radiant web site?

Thanks in advance!


Best regards,
Andreas Semt
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

------------------------------------------------------------------------

_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to