# Previous Custom Text keeps appearing when refreshing Customize Text page

**URL:** https://meta.discourse.org/t/previous-custom-text-keeps-appearing-when-refreshing-customize-text-page/180153
**Category:** Support
**Created:** [February 18, 2021, 7:52am UTC](https://meta.discourse.org/t/previous-custom-text-keeps-appearing-when-refreshing-customize-text-page/180153 "2021-02-18T07:52:13Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![frank.manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frank.manuel/32/203348_2.png) [@frank.manuel](https://meta.discourse.org/u/frank.manuel)
#### Post date: [February 18, 2021, 7:52am UTC](https://meta.discourse.org/t/previous-custom-text-keeps-appearing-when-refreshing-customize-text-page/180153/1 "2021-02-18T07:52:13Z")

</div>

So I manually updated category.replace\_paragraph in the database, in translation\_overrides table. This is part of some server sync thing I’ve made.

 ![Screen Shot 2021-02-18 at 3.24.19 PM](https://global.discourse-cdn.com/meta/original/3X/0/e/0e545f4290505e61f37d35d41756bcd0b90d7683.png)

And it reflects in the page correctly:

 ![Screen Shot 2021-02-18 at 3.23.57 PM](https://global.discourse-cdn.com/meta/original/3X/9/7/97e244933ff84f1df3e139040da97d0bfc1b1264.png)

Until I keep refreshing the page, for some reason, then it cycles back and forth between this correct value and an old value that I used as part of testing:

 ![Screen Shot 2021-02-18 at 3.24.29 PM](https://global.discourse-cdn.com/meta/original/3X/c/f/cf8c64ab77a9e12a5cb229c091866287c6222159.png)

But this WWW value is no longer in translation\_overrides. The only place left where I can find it is in user\_histories as one of the previous test values:

 ![Screen Shot 2021-02-18 at 3.30.32 PM](https://global.discourse-cdn.com/meta/original/3X/3/0/308e19a4ce44ce2a582d72457237a37a9b745fb0.png)

I thought it might have been an issue with WWW still being in memory or something, but even from a different browser (where WWW had never been loaded), the same behavior occurs.

Anyone have an idea why this happens? Is there another table that holds old values that I don’t know about?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 18, 2021, 7:55pm UTC](https://meta.discourse.org/t/previous-custom-text-keeps-appearing-when-refreshing-customize-text-page/180153/2 "2021-02-18T19:55:27Z")

</div>

How did you install Discourse? Unstable site settings is a sign of a broken install, based on what I’ve seen.

---

<div class="post-metadata">

### Author: ![frank.manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frank.manuel/32/203348_2.png) [@frank.manuel](https://meta.discourse.org/u/frank.manuel)
#### Post date: [February 18, 2021, 10:00pm UTC](https://meta.discourse.org/t/previous-custom-text-keeps-appearing-when-refreshing-customize-text-page/180153/3 "2021-02-18T22:00:25Z")

</div>

Standard Discourse-docker install, but I did mess with the settings, trying to migrate the settings from one server to another. Might have messed with some server-specific setting in `site_settings` that I shouldn’t have.

Should I take it that the settings saved by the `site_settings:export` rake task are all safe to copy from one server to another? Not likely to break anything? I’ll use it as a guide to whitelist the settings to migrate, if so.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 19, 2021, 5:34am UTC](https://meta.discourse.org/t/previous-custom-text-keeps-appearing-when-refreshing-customize-text-page/180153/4 "2021-02-19T05:34:49Z")

</div>

I’m not sure, I just wanted to mention it because site settings that don’t save, or come back different over time, tend to be associated with broken Discourse installs based on the last 7+ years I’ve been reading meta topics.