I figured it out. In case anyone sees this, and wants a fun story about me being dumb: I had an older version of my site that did not have the new setting running on a different domain (for QA), but forgot I'd left it hooked up to the production database. Unbeknownst to me Mezzanine will delete any settings in the database that are not registered. So probably some web spider was hitting the other domain and caused this.
On Thursday, 8 November 2018 11:09:55 UTC-5, Chris Hawes wrote: > > > I added a setting in defaults.py in on of my apps: > > > from mezzanine.conf import register_setting > > register_setting( > name='MY_SETTING', > label='My setting', > description='Some stuff.', > editable=True, > default='' > ) > > I set it to a value in the admin, but a few hours later, I noticed that it > was blank. I set it again, and a few hours later I came back, and it was > blank again. Repeat ad nauseum. > > When I look in the database, I see what is happening: the row in > conf_setting for this setting is simply disappearing. It's getting dropped > somewhere. I set it again, and then it disappears again a few hours later. > I've looked through the code in mezzanine.conf.__init__.py and cannot see > any reason why this row would get dropped. I have other editable settings > in my project that do not exhibit this problem. > > I am perplexed. Has anyone seen anything like this before? Any ideas what > to look at? > > I'm using: > > - Django 1.11.16 > - Mezzanine 4.3.1 > - PostgreSQL 9.6 > > Thanks for any help, > Chris > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
