Migrating to 1.0

41 views
Skip to first unread message

Brian Gernhardt

unread,
Feb 1, 2012, 4:24:23 PM2/1/12
to radia...@googlegroups.com
I'm rebuilting my web-server and in the process migrating an old Radiant install to 1.0rc4. I'm having a hard time finding extensions, however. I was hoping that the community could help me out a bit. Here's a list of the non-standard extensions I'm currently using:

- multi_site
- Aggregation
- Copy Move
- reorder

There are more features that I was looking to add, but aren't vital:

- site-scoped assets
- access controls
- versioning

If anyone has any tips about which extensions (and which forks of them) I should be looking at, it would be much appreciated.

~~ Brian

john

unread,
Feb 1, 2012, 7:51:20 PM2/1/12
to radia...@googlegroups.com
aggregation is built in now so you can get rid of that extension.
benny's reorder_children gem works well with rc4.

could you open issues against these extension with any additional information you have (stack traces, logs etc.). anything under the radiant organization should definitely be fixed or clearly marked as abandoned/incompatible/whatever.

Benny Degezelle

unread,
Feb 2, 2012, 9:03:49 AM2/2/12
to Radiant CMS
For copy_move and reorder, these should work in rc4

gem "radiant-copy_move-extension", "~> 2.4.3"
gem "radiant-reorder_children-extension", "~> 1.0.5"

For versioning, I did some updates to the chronicle extension a while
ago.
I think it will still work with rc4, but I am not using it in
production anywhere, so there may be bugs..
Also, it's lacking a gemspec, so you will have to vendor it;

git submodule add https://github.com/jomz/radiant-chronicle-extension
vendor/extensions/chronicle && rake
radiant:extensions:chronicle:migrate && rake
radiant:extensions:chronicle:update

Please open issues on github if you encounter any. Thanks!

Brian Gernhardt

unread,
Feb 2, 2012, 11:08:18 AM2/2/12
to radia...@googlegroups.com

On Feb 1, 2012, at 7:51 PM, john wrote:

> could you open issues against these extension with any additional information you have (stack traces, logs etc.). anything under the radiant organization should definitely be fixed or clearly marked as abandoned/incompatible/whatever.

Once I get going, I definitely will. But digging through the extensions site and Google results often gives me things that haven't been updated in a while. I'm trying to rebuild my entire infrastructure so trying piles of extensions trying to find which ones are current isn't high on my TODO list. ;-)

Thanks for your advice, John and Benny. I'll report my experiences to both list and issue trackers, as appropriate.

~~ Brian

Reply all
Reply to author
Forward
0 new messages