[MM3-users] Re: [migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite

On 10/20/23 14:04, Wikinaut wrote:

I also solved this issue. How?

By adding columns to two tables in the database mailman3web:

alter table hyperkitty_mailinglist add column archive_rendering_mode varchar(255) default null; alter table socialaccount_socialapp add column provider_id varchar(200) NOT NULL; alter table socialaccount_socialapp add column settings longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL CHECK (json_valid(settings));

The proper fix is just to run mailman-web migrate. See https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mig...

You should also run that and mailman-web collectstatic mailman-web compress and mailman-web compilemessages any time you do any kind of update. See https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-f... et. seq.

Running mailman-web migrate at this point may fail because of the changes you made manually.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan