Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
Chris Salzberg
There are a couple small things with querying which are not yet supported, and some small differences, everything should be documented there in the wiki.
Chris Salzberg
My issue with Globalize is that it goes too far monkey-patching, which leads to strange, hard-to-debug issues, especially when upgrading Rails. And since it's "all or nothing", you can't (say) disable dirty-tracking if you don't need it. This makes it hard to offer a new version until all compatibility issues are completely resolved.
I'm partly responsible for that since I wrote some of that monkey-patching code... :worried:
But once it's there, nobody wants to remove it.
Tim Schmelmer
Wow, thanks for the awesome docs for migrating, @shioyama ! We will definitely check this out!
Chris Salzberg
Great, and let me know if you notice anything missing.
Philip Arndt
Those are my issues with Globalize too :wink:
part of me wonders if we can't just add a shallow layer on top of Mobility and retain all existing globalize functionality that way
Chris Salzberg
Maybe in a separate gem or something
But the problem is that what people now expect Globalize to do is a problem
Philip Arndt
people can always stay on the current version :)
Hello, If i create query(Post.all - for example) can i exclude object if it havent translation in one of the translation language
Matthew Kennedy
Rails 5.2 any progress?
Hi everyone! Does someone know if globalize supports postgres jsonb data type? Or should I better try the json_translate alternative? Any input is appreciated :)
Scott ♛
Hello, I was hoping that someone would be able to help me with something. I have a fairly large production database (1.5M records). I tried using the Model.create_translation_table with {migrate_data: true, remove_source_columns: false}, but it seemed to run all night and then eventually crashed. Luckily no harm was done. However, now I want to run the migration with migrate_data: false, and just run my own rake task to migrate the data. The PROBLEM is that now I dont seem to have any access to the original data attributes. I wrote a task that borrows heavily from you #move_data_to_translation_table method, however I seem to end up with nil values. The problem seems to be that record.read_attribute(attribute_name, {:translated => false}) always returns nil. Even in the console this value is nil. But for some reason in the migration the values are not nil. Can anyone let me know how I can access my original data columns for my translated values? I know the data is still in the database, I just don't know how to access it. Thanks for reading.
Tiago Santos
mmm, ok, this is dead
I have a quick question
Is anyone out there?
What is the necessary of putting gem 'activemodel-serializers-xml' in the Gemfile along with the link to globalize gem?
As per the documentation mentioned in the github
Oleg Bovykin
Hi! Could anybody help with globalizing store_accessor field? I created an issue, but it looks like nobody here globalize/globalize#747
how to implement globelize with jbuider on ruby on rails
ruby 2.4.6
rails 4.2.10
pg 0.21.0
change_column :property_value_translations, :name, :text
cannot alter type of a column used by a view or rule
how to drop related views and regenerate them after ?
change_column :property_value_translations, :name, :text
Becsei David

Hi, I try to upgrade spree 4.2.
globalize 6.0.0
rails 6.1
spree_core 4.2.1

After bundle install run rake db:create, but i give this error:
Unable to connect to a database. Globalize skipped ignoring columns of translated attributes.

Does anyone have any idea about this error?

1 reply
John R. D'Orazio
hello ev1, can Globalize be integrated with tools like Weblate? I have a self-hosted weblate server where I can easily track and translate the yml files generated by the I18n API. Can globalized contents be exported to ruby yaml files, or to i18next JSON files? These are formats that Weblate can read and write (https://docs.weblate.org/en/latest/formats.html#translation-types-capabilities)