jordi fita mas
ff6e9497b5
Customer does not want a contact page, but a page where they can write the direction on how to reach the campground, with a Google map embed instead of using Leaflet, because Google Maps shows the reviews right in the map. That means i had to replace the GPS locations with XML fields for the customer to write. In all four languages. This time i tried a translation approach inspired by PrestaShop: instead of opening a new page for each language, i have all languages in the same page and use AlpineJS to show just a single language. It is far easier to write the translations, even though you do not have the source text visible, specially in this section that there is no place for me to put the language links.
24 lines
565 B
PL/PgSQL
24 lines
565 B
PL/PgSQL
-- Deploy camper:location_i18n to pg
|
|
-- requires: roles
|
|
-- requires: schema_camper
|
|
-- requires: location
|
|
-- requires: language
|
|
|
|
begin;
|
|
|
|
set search_path to camper, public;
|
|
|
|
create table location_i18n (
|
|
company_id integer not null references location,
|
|
lang_tag text not null references language,
|
|
directions xml not null,
|
|
opening_dates xml not null,
|
|
primary key (company_id, lang_tag)
|
|
);
|
|
|
|
grant select on table location_i18n to guest;
|
|
grant select on table location_i18n to employee;
|
|
grant select, insert, update, delete on table location_i18n to admin;
|
|
|
|
commit;
|