pgcd on Nostr: I'm looking at migrating a #Django 1.9 installation to a 5.1 (ideally, TBC) and ...
I'm looking at migrating a #Django 1.9 installation to a 5.1 (ideally, TBC) and everything's going swimmingly (for a given value of) except Django CMS which is giving me a rather unexpected error:
'CMSConfig' object has no attribute 'cms_extension'
In other words, it expects the CMS AppConfig instance to possess an attribute that is never explicitly set anywhere.
Sooner or later I'll figure it out but if somebody knows what's going on (eg. sm1 from Divio) that'd be *AWESOME*.
(please boost!)
Published at
2025-01-27 14:25:45 UTCEvent JSON
{
"id": "34b13dac81fe3f6d957c8e27ca0ff99a516f9b9565288fb55f06c2a124fbc762",
"pubkey": "701304e8500bf9c941021b768d1ed3649941fdfac4760132cfeaa6344348f912",
"created_at": 1737987945,
"kind": 1,
"tags": [
[
"t",
"django"
],
[
"proxy",
"https://mastodon.online/users/pgcd/statuses/113900777971226701",
"activitypub"
]
],
"content": "I'm looking at migrating a #Django 1.9 installation to a 5.1 (ideally, TBC) and everything's going swimmingly (for a given value of) except Django CMS which is giving me a rather unexpected error:\n 'CMSConfig' object has no attribute 'cms_extension'\nIn other words, it expects the CMS AppConfig instance to possess an attribute that is never explicitly set anywhere.\n\nSooner or later I'll figure it out but if somebody knows what's going on (eg. sm1 from Divio) that'd be *AWESOME*.\n\n(please boost!)",
"sig": "a92a14f5bc0a3e43868eeb0b454a1da89c5f580ac8f9c35b3a97dae3e365174d8b2294c047a247a78fc9180a6751b8706b00d2364715f157b9fee0978bd1a285"
}