application (500) errors without tmp/cache/entity and/or tmp/cache/meta #12
Comments
|
Verify that the cache directory exists before trying to store a response. Closed by 3682d66 |
rx
pushed a commit
to voomify/radiant
that referenced
this issue
Jul 19, 2011
rx
pushed a commit
to voomify/radiant
that referenced
this issue
Jul 19, 2011
* 'master' of github.com:radiant/radiant: Undefine prototype rake tasks in instance mode. Closes radiant#17 Verify that the cache directory exists before trying to store a response. Closes radiant#12 Fix page-part deletion in JS. Closes radiant#16 Don't cache extension-defined javascripts, but do cache the defaults. Update history. created spec for and implemented fix in development mode behavior when Radiant::Config['dev.host'] is defined Revert "Merge branch 'tab'"
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
often when i'm having trouble with differences between the browser's cache and radiant's cache i just
rm -r tmp/cache, clear the browser cache and reload. up until 0.8.1 this worked fine; radiant would just recreate the necessary folders as needed. now i get an application error until i manually recreate the cache directories; e.g.mkdir -p tmp/cache/entity tmp/cache/metaThe text was updated successfully, but these errors were encountered: