#Payload 3.0 + Supabase Localization

2 messages · Page 1 of 1 (latest)

obsidian bronze
#

I have a Payload 3.0 instance set up from the official template with Supabase, and have turned on the localized property for the title field in the Posts collection. After I add my locales to the nextjs config file and run the dev server, I get these warnings:

· You're about to delete version_meta_title column in _pages_v table with 2 items
· You're about to delete version_meta_image_id column in _pages_v table with 2 items
· You're about to delete version_meta_description column in _pages_v table with 2 items
· You're about to delete subject column in forms_emails table with 1 items
· You're about to delete message column in forms_emails table with 1 items
· You're about to delete submit_button_label column in forms table with 1 items
· You're about to delete confirmation_message column in forms table with 1 items
· You're about to delete title column in posts table with 3 items
· You're about to delete meta_title column in posts table with 3 items
· You're about to delete meta_image_id column in posts table with 3 items
· You're about to delete meta_description column in posts table with 3 items

I understand it has to restructure the database models/instances for enabling localization, but the way it modifies the Supabase instance ends up breaking the functionality of the app.

For example, in my deployed instance (Vercel), the Posts collection view in the admin page breaks because the columns are missing. If I update a post (in dev) and go back to the collection view in the admin dashboard, I'm met with this error:

13:03:36] ERROR: QueryError: The following path cannot be queried: document.relationTo

How should I go about approaching these issues? Thank you

brave ploverBOT