Files
grecia/db/pages/welcome_level_two_verified.rb
Javi Martín 647121d13e Allow different locales per tenant
Note that, currently, we take these settings from the database but we
don't provide a way to edit them through the admin interface, so the
locales must be manually introduced through a Rails console.

While we did consider using a comma-separated list, we're using spaces
in order to be consistent with the way we store the allowed content
types settings.

The `enabled_locales` nomenclature, which contrasts with
`available_locales`, is probably subconsciously based on similar
patterns like the one Nginx uses to enable sites.

Note that we aren't using `Setting.enabled_locales` in the globalize
initializer when setting the fallbacks. This means the following test
(which we could add to the shared globalizable examples) would fail:

```
it "Falls back to an enabled locale if the fallback is not enabled" do
  Setting["locales.default"] = "en"
  Setting["locales.enabled"] = "fr en"
  allow(I18n.fallbacks).to receive(:[]).and_return([:fr, :es])
  Globalize.set_fallbacks_to_all_available_locales

  I18n.with_locale(:fr) do
    expect(record.send(attribute)).to eq "In English"
  end
end
```

The reason is that the code making this test pass could be:

```
def Globalize.set_fallbacks_to_all_available_locales
  Globalize.fallbacks = I18n.available_locales.index_with do |locale|
    ((I18n.fallbacks[locale] & Setting.enabled_locales) + Setting.enabled_locales).uniq
  end
end
```

However, this would make it impossible to run `rake db:migrate` on new
applications because the initializer would try to load the `Setting`
model but the `settings` table wouldn't exist at that point.

Besides, this is a really rare case that IMHO we don't need to support.
For this scenario, an installation would have to enable a locale, create
records with contents in that locale, then disable that locale and have
that locale as a fallback for a language where content for that record
wasn't created. If that happened, it would be solved by creating content
for that record in every enabled language.
2024-06-05 16:10:56 +02:00

29 lines
1.2 KiB
Ruby

def generate_content(page)
page.title = I18n.t("welcome.welcome.title")
page.content = "<p>#{I18n.t("welcome.welcome.user_permission_info")}</p>
<ul>
<li>#{I18n.t("verification.user_permission_debates")}</li>
<li>#{I18n.t("verification.user_permission_proposal")}</li>
<li>#{I18n.t("verification.user_permission_support_proposal")}</li>
</ul>
<p>#{I18n.t("welcome.welcome.user_permission_verify")}</p>
<ul>
<li>#{I18n.t("verification.user_permission_votes")}</li>
</ul>
<a href='/verification' class='button success radius expand'>
#{I18n.t("welcome.welcome.user_permission_verify_my_account")}
</a>
<p><a href='/'>#{I18n.t("welcome.welcome.go_to_index")}</a></p>"
page.save!
end
if SiteCustomization::Page.find_by(slug: "welcome_level_two_verified").nil?
page = SiteCustomization::Page.new(slug: "welcome_level_two_verified", status: "published")
Setting.enabled_locales.each do |locale|
I18n.with_locale(locale) { generate_content(page) }
end
end