Multilanguage static fields save workaround

[rallisf1]

For anyone still using this and creates multi-language sites, there is a bug when you edit the English version of a block with static fields, it will overwrite all the other languages with the previous English content.

My workaround is a Supabase trigger (on public.symbols, before_update, per row) with the following function content:

DECLARE
  lang_key text;
  keys text[];
  symbol_field jsonb;
BEGIN
  -- Step 1: Get all language keys from NEW.content
  SELECT array_agg(key) INTO keys
  FROM jsonb_object_keys(NEW.content) AS key;

  -- Skip if only one language key exists
  IF array_length(keys, 1) <= 1 THEN
    RETURN NEW;
  END IF;

  -- Step 2: Loop through the fields of the symbol from the symbols table
  FOR symbol_field IN
    SELECT jsonb_array_elements(fields) AS field
    FROM public.symbols
    WHERE id = OLD.id
  LOOP
    -- Step 3a: Check if the symbol field is static (root-level `is_static`)
    IF symbol_field ->> 'is_static' = 'true' THEN
      -- Step 3b: Loop through the language keys
      FOREACH lang_key IN ARRAY keys
      LOOP
        IF lang_key <> 'en' THEN
          -- Step 3c: Update content for the current language key
          NEW.content := jsonb_set(
            NEW.content, 
            ARRAY[lang_key, symbol_field ->> 'key'], 
            COALESCE(OLD.content -> lang_key -> (symbol_field ->> 'key'), 'null'::jsonb), 
            true
          );
        END IF;
      END LOOP;
    END IF;
  END LOOP;

  RETURN NEW;
END;

[rallisf1]

Damn, I missed that with this you can no longer edit the content in the other languages. Sadly all the workarounds I tried fails. I'm closing this for now so people don't see it as a permanent solution.

Personally I'll keep the trigger disabled and enable it whenever I need it.

If you have a better approach let me know.