by Luc Saffre · in Developers · assigned to Luc Saffre

Kokkuvõte

Children

Kommentaarid

• 3 aastat, 1 kuu ago by Luc Saffre about #5119 (No LayoutElement for extra_data (<class 'django.db.models.fields.json.JSONField'>)) : Intuition-driven development: I removed the --merge in initdb since it caused problems in other places, and --out of a nightly inspiration-- have initdb loop over installed_plugins instead of sorted_plugins when calling on_initdb(). And voilà, the symptoms are gone! Without really understanding the ...
• 3 aastat, 1 kuu ago by Luc Saffre about #5119 (No LayoutElement for extra_data (<class 'django.db.models.fields.json.JSONField'>)) : Okay this is not yet done, I committed too quickly: the '--merge' fixes pm prep in cms1, but it causes "sqlite3.OperationalError: no such table: contacts_companytype" in doctest specs/migrate.rst...
• 3 aastat, 1 kuu ago by Luc Saffre about #5119 (No LayoutElement for extra_data (<class 'django.db.models.fields.json.JSONField'>)) : The initdb command now calls makemigrations with '--merge' , which fixes the "multiple leaf nodes" issue.
• 3 aastat, 1 kuu ago by Luc Saffre about #5119 (No LayoutElement for extra_data (<class 'django.db.models.fields.json.JSONField'>)) : Oops, no, I have another error after upgrading these packages: "go cms1; pm prep" says "CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0014_alter_association_id_alter_code_id_alter_nonce_id_and_more, 0015_rename_extra_data_new_usersocialauth_extra_data in...
• 3 aastat, 1 kuu ago by Luc Saffre about #5119 (No LayoutElement for extra_data (<class 'django.db.models.fields.json.JSONField'>)) : I can reproduce this issue on my machine after upgrading the python packages required by google plugin.
• 3 aastat, 1 kuu ago by Luc Saffre about #5119 (No LayoutElement for extra_data (<class 'django.db.models.fields.json.JSONField'>)) : Created new Ticket #5119 (No LayoutElement for extra_data ()).