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.
25 lines
329 B
PL/PgSQL
25 lines
329 B
PL/PgSQL
-- Test extension_citext
|
|
set client_min_messages to warning;
|
|
create extension if not exists pgtap;
|
|
reset client_min_messages;
|
|
|
|
begin;
|
|
|
|
select plan(1);
|
|
|
|
select extensions_are(array [
|
|
'btree_gist'
|
|
, 'citext'
|
|
, 'pgcrypto'
|
|
, 'pg_libphonenumber'
|
|
, 'pgtap'
|
|
, 'plpgsql'
|
|
, 'uri'
|
|
, 'vat'
|
|
]);
|
|
|
|
select *
|
|
from finish();
|
|
|
|
rollback;
|