Ruby Forum Radiant CMS > Installing extensions

I recently set up a new site using the 0.6.9 gem.

I wanted to install the Reorder extension so I:

1. copied the source to vendor/extensions/reorder
2. ran "rake production db:migrate:extensions"
3. ran "rake production radiant:extensions:reorder:update"

Everything appears to have gone swimmingly, but the reorder extension
isn't showing up in the admin ui. Upon checking the "Extensions" page in
the admin panel, it looks like it is not installed.

Does this have something to do with the script/extension install(or
uninstall) commands added in the 0.6.8 release? (...and how do I use
those commands anyway? If I run that do I have to run the two rake
tasks?)

Cheers!
Ben

Ben Morrow wrote:
> the admin panel, it looks like it is not installed.
>
> Does this have something to do with the script/extension install(or
> uninstall) commands added in the 0.6.8 release? (...and how do I use
> those commands anyway? If I run that do I have to run the two rake
> tasks?)
>
> Cheers!
> Ben
>   

Hi Ben

Sorry for the late reply.  Your post made me finally take the plunge and
set up reorder on my side.  I followed the extension's readme file and
it worked for me quite fine.  There are a few things that come to mind:

1. Which version did you use?  I used the one that I downloaded from the
Git page.
2. Your step #3 seems to be wrong.
3. Any extensions that might conflict?

Rather than type everything into this thread, I used my installation
experience to add to the 'Summer Reboot' documentation.  The steps I
followed and the results I got (with screenshots) are now online at:
http://wiki.radiantcms.org/Reorder

Please see if that helps you.

Also, I noticed 1 thing (unrelated to your problem) that seems to be
there with the extension (I've noted this on the Summer Reboot also) and
am just asking for confirmation:   It seems that at this stage, if you
change the order of the children, the cache of the parent page is not
expired. This means that your change may not be propagated to the
website immediately. If you must force it, open the parent page and do a
save on it again (without any changes is also fine) so that the cache
for that page expires.

That's all for now!  Hope this helps you, Ben.

Cheers,
Mohit.
8/13/2008 | 12:11 AM.