Added support for site with several locales #28
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks, might use this, exactly what I was looking for |
Collaborator
|
@dougal any interest? |
Owner
|
Interesting, but I need to have a play with Globalize to really understand how it works. |
Collaborator
|
Won't merge without test coverage, as this is 11 years old. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am using Globalize3 and noticed that acts_as_indexed didn't work correctly for my multi-lingual site.
The problem was that if I started with locale :en and made a search, it indexed all the translated fields for english. But if I then changed language to :sv and made a different search it didn't re-index and I only got hits for the search phrase on the previously indexed english hits. This fix will add a folder with the locale to each model so that you will be able to index correctly.
Don't know if it should be a merge to the main project (due to the I18n dependency) but might be a nice branch if someone else has the same problem.