Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempted fix for i18n fallback #3998

Closed

Conversation

shubhscoder
Copy link
Contributor

Fixes #3961
I am not sure that this would work, but we can try this.

@plotsbot
Copy link
Collaborator

plotsbot commented Nov 18, 2018

1 Warning
⚠️ It looks like you merged from master in this pull request. Please rebase to get rid of the merge commits – you may want to rewind the master branch and rebase instead of merging in from master, which can cause problems when accepting new code!
1 Message
📖 @shubhscoder Thank you for your pull request! I’m here to help with some tips and recommendations. Please take a look at the list provided and help us review and accept your contribution! And don’t be discouraged if you see errors – we’re here to help.

Generated by 🚫 Danger

config.i18n.fallbacks = true

#config.i18n.fallbacks = true
config.i18n.fallbacks = {:en => [:en, :de], :de => [:de, :en]}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, did this work for you in your local copy?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried setting up the system in production mode on my system and failed terribly. There were multiple failing migrations. I tried skipping them but because of these skipped migrations many later migrations also failed. Could we test it in staging?

@jywarren
Copy link
Member

jywarren commented Nov 26, 2018 via email

@jywarren
Copy link
Member

Hm, well it boots locally for me, but I am not actually not able to reproduce the original bug locally now that I try.

@jywarren
Copy link
Member

Ah, and you should be able to point production at the same database using config/database.yml, i'll try that now...

@jywarren
Copy link
Member

I had to copy the development key from config/secrets.yml to the line for production, too...

@jywarren jywarren force-pushed the Trying_to_fix_I18n_fallbacks branch from 19862a5 to fc766b6 Compare November 28, 2018 02:38
@ghost ghost assigned jywarren Nov 28, 2018
@ghost ghost added the in progress label Nov 28, 2018
@jywarren
Copy link
Member

Ah, hmm, so in production i'm seeing:

image

Plus all through the HTML:

<h3><span class="translation_missing" title="translation missing: de.tag.show.notes_tagged, tag: test">Notes Tagged</span></h3>

However these translations really are missing. But i'm not seeing the complete 500 error as in #3961...

@jywarren
Copy link
Member

jywarren commented Nov 28, 2018

So one way to test this would be to push this to the unstable branch, then go to https://unstable.publiclab.org/change_locale/de, then go to https://unstable.publiclab.org/questions/tag/parent:multispectral-imaging/author/nedhorning --

I'm pushing to unstable now. it'll take some time (10 minutes?) then this should be test-able.

@jywarren
Copy link
Member

Hmm, it seems to have failed? https://jenkins.laboratoriopublico.org/job/Plots-Unstable/348/

@jywarren
Copy link
Member

@jywarren
Copy link
Member

Hmm, i think it needs a push from @icarito - i got an error:

make: *** No rule to make target 'build'.  Stop.
Build step 'Execute shell' marked build as failure
Finished: FAILURE

@jywarren
Copy link
Member

@jywarren
Copy link
Member

jywarren commented Jan 2, 2019

I believe unstable is working again now, and we should be able to test this starting tomorrow if you like!

@jywarren jywarren changed the title Attempted fix for fallback Attempted fix for i18n fallback Jan 2, 2019
@jywarren jywarren added this to the Internationalization milestone Jan 2, 2019
@shubhscoder
Copy link
Contributor Author

Yes sure we can test this on unstable! I am not sure of how we deploy on unstable, but think we have a different link along with a password to test things right @jywarren ? Thank you !

@jywarren
Copy link
Member

jywarren commented Jan 3, 2019

Hi, to test on unstable, we push to the unstable branch, which only some of us have access to. I just did, and will announce in the chatroom that I've done this so we don't conflict with others - there's only one test server to share. Then you can try it out at https://unstable.publiclab.org !

@jywarren
Copy link
Member

jywarren commented Jan 3, 2019

OK, it's on there until someone else uses unstable!

@jywarren
Copy link
Member

Hi @gauravano, should we close this? Thanks!!

@jywarren
Copy link
Member

jywarren commented May 7, 2019

@gauravano just checking if this could be closed, what do you think? Thanks, all!

@jywarren jywarren changed the base branch from master to main June 30, 2020 17:44
@cesswairimu
Copy link
Collaborator

Closing this. Feel free to open if we still need it.Thanks all

@grvsachdeva
Copy link
Member

Hi @jywarren @cesswairimu sorry for missing out on your comments 😞. I went through the issue this PR aim to solve and looks like we had the closure there.

So, maybe we can close the issue too - #3961 . We can ask someone from PL team or from the community from Germany for testing it once more if you folks think it's required.

Thanks!!

@cesswairimu
Copy link
Collaborator

Thanks @gauravano 👍 will ping Liz on the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Site-wide outage for german :de locale -- due to fallback fail
5 participants