# Anyone using globalize2\_versioning?

**URL:** <https://www.ruby-forum.com/t/anyone-using-globalize2-versioning/184451>\
**Category:** Rails I18n\
**Created:** [March 2, 2010, 7:12pm UTC](https://www.ruby-forum.com/t/anyone-using-globalize2-versioning/184451 "2010-03-02T19:12:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kyle\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ecd19e/32.png) [@Kyle\_F](https://www.ruby-forum.com/u/Kyle_F)\
**Post date:** [March 2, 2010, 7:12pm UTC](https://www.ruby-forum.com/t/anyone-using-globalize2-versioning/184451/1 "2010-03-02T19:12:23Z")

</div>

Globalize2 looks _awesome_, but our app also requires versioning. I’m  
looking at globalize2\_versioning[1] but it looks fairly out of date,  
and I can’t seem to get it to load properly. (I’m using both as rails  
plugins).

For example, globalize2\_versioning defines its own  
`create_translation_table!` method which, in addition to the normal  
translation columns provided by Globalize2, adds columns for  
versioning (`version` and `current`, specifically). But it appears  
that globalize2\_versioning’s method doesn’t get called – it’s always  
the method from Globalize2, meaning the columns for versioning aren’t  
added. Similarly, the models I specify as versioned do not have the  
`versioned?` method added to them.

I’m wondering if this is simply because I’m loading/using  
globalize2\_versioning wrong, or if the plugin is simply too far  
outdated to be used with the current version of Globalize2.

How is everyone else tackling versioning with Globalize2? Any help  
would be appreciated.

Thanks!

[1] [GitHub - joshmh/globalize2\_versioning: Acts\_as\_versioned style versioning for Globalize2](http://github.com/joshmh/globalize2_versioning)

---

<div class="post-metadata">

**Author:** ![Kyle\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ecd19e/32.png) [@Kyle\_F](https://www.ruby-forum.com/u/Kyle_F)\
**Post date:** [March 2, 2010, 8:43pm UTC](https://www.ruby-forum.com/t/anyone-using-globalize2-versioning/184451/2 "2010-03-02T20:43:44Z")

</div>

I would suggest using any of the more active versioning plugins listed  
in [ruby-toolbox.org](http://ruby-toolbox.org), and also read this discussion for info on model  
translations:

[http://groups.google.com/group/rails-i18n/browse\_thread/thread/76fcfd3bc198c90f#](http://groups.google.com/group/rails-i18n/browse_thread/thread/76fcfd3bc198c90f#)

Grobalize2 never made any sense to me, code smell in my point of view.

grimen

---

<div class="post-metadata">

**Author:** ![Kyle\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ecd19e/32.png) [@Kyle\_F](https://www.ruby-forum.com/u/Kyle_F)\
**Post date:** [March 2, 2010, 10:17pm UTC](https://www.ruby-forum.com/t/anyone-using-globalize2-versioning/184451/3 "2010-03-02T22:17:23Z")

</div>

The libraries mentioned in that other thread are far more outdated  
that Globalize2 is, and offer _no_ solution for versioning.

The problem with doing translatable models AND versioned models is  
that translation and version information can’t be stored in separate  
tables. This makes it nearly impossible to use two different  
libraries for each: at some level, they need to integrate with one  
another.

I’m not sure why you don’t like Globalize2, it works exactly as  
advertised for me (and works well, too). My only extra requirement is  
that I need versioning, and since I don’t expect Globalize2 to support  
this (out of scope), I would like to simply get globalize2\_versioning  
working.

I would be willing to update globalize2\_versioning if I could get an  
idea of where that project is at.

---

<div class="post-metadata">

**Author:** ![Kyle\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ecd19e/32.png) [@Kyle\_F](https://www.ruby-forum.com/u/Kyle_F)\
**Post date:** [March 2, 2010, 11:53pm UTC](https://www.ruby-forum.com/t/anyone-using-globalize2-versioning/184451/4 "2010-03-02T23:53:59Z")

</div>

I believe it’s a very good thing that we have concurring solutions to  
the non-trivial problem of content translations.

On Mar 2, 2010, at 10:16 PM, Kyle F. wrote:

> The libraries mentioned in that other thread are far more outdated  
> that Globalize2 is, and offer _no_ solution for versioning.

I’ve refactored a few things in Globalize2 a while ago to take some  
recurring concerns into account. I actually completely missed to take  
care of globalize2-versioning at that point though.

> I would be willing to update globalize2\_versioning if I could get an  
> idea of where that project is at.

It’s right here and any help is very welcome 🙂 I guess Josh is busy  
with other things but I can take over his role in the meanwhile  
(although I don’t think I actually ever touched the code).

Is there anything you need to get started? You can find me on IRC on  
[irc.freenode.net](http://irc.freenode.net) #rails-i18n or we can discuss things here or through  
private email.

---

<div class="post-metadata">

**Author:** ![Kyle\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ecd19e/32.png) [@Kyle\_F](https://www.ruby-forum.com/u/Kyle_F)\
**Post date:** [March 3, 2010, 12:40am UTC](https://www.ruby-forum.com/t/anyone-using-globalize2-versioning/184451/5 "2010-03-03T00:40:14Z")

</div>

Okay, so the 0.1.1 tag of Globalize2 ([joshmh (Josh Harvey) · GitHub](http://github.com/joshmh/)  
globalize2/tree/v0.1.1) works great with globalize2\_versioning.

(Thanks Sven!)