# BUG/WORKAROUND: rake radiant:update in 0.6.5

**URL:** <https://www.ruby-forum.com/t/bug-workaround-rake-radiant-update-in-0-6-5/135252>\
**Category:** Radiant CMS\
**Created:** [April 20, 2008, 12:44am UTC](https://www.ruby-forum.com/t/bug-workaround-rake-radiant-update-in-0-6-5/135252 "2008-04-20T00:44:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\
**Post date:** [April 20, 2008, 12:44am UTC](https://www.ruby-forum.com/t/bug-workaround-rake-radiant-update-in-0-6-5/135252/1 "2008-04-20T00:44:03Z")

</div>

I hate to be the bearer of bad news after such a big release, but there  
is a minor problem with the “radiant:update” rake task for users that  
are upgrading their existing projects. I have fixed the problem in the  
git repository, but here’s the workaround in the meantime:

In your project directory, create the public/javascripts/admin/  
subdirectory, like so on \*nix or Mac OS:

mkdir -p public/javascripts/admin

Then run “rake radiant:update” to get the new javascript (and other)  
files. Thanks to Andrew Vonderluft for helping me find this bug when  
upgrading the Radiant servers.

Sean