The default language in the forum is English (US).

I made some changes to registration rules text.

In my localhost, when I visit the registration rules page, I can see the new text.

When I point localhost to prod DB, and go to registration rules page, I can still see the new text.

The production is exact copy of localhost (since I used ftp to copy all folders).

Now, in production, when I goto registration rules page, I see the old (default) rules text.

I verified in admin settings and table registry that language is set to english.xml. It looks like production is using some other language file. This could be related to see weird characters in daily digest. I updated rules in china.xml file and uploaded it; but it still shows old text.

Any idea why this is happening?

Never mind. I was browsing through other forum topic and noticed squirrel mentioned that to see new logo, they had to restart the app.

Once I restarted the app, I saw the new text. :-d

I thought it would load automatically (like web.config). Thanks squirrel 👍

It's no problem! There are certain parts of YAF that are cached - one being 'what files are included' in page output - such as theme files and language files. Settings inside the app.config, mail.config, and db.config are also cached and do not trigger a restart. Only 'touching' the web.config, restarting the IIS application, or from within the YAF admin area, under Maintenance is a "Restart YAF" option. Additionally, under the Host Settings, clearing the cache can also reset many items without restarting the application (to the best of my knowledge).

Regarding language updates being 'live' - my theory in why the cache is not reset would be that it would allow many changes to a language file, then when all are complete, flush cache and check output - but would allow editing of many items without affecting output or triggering constant cache dumps (which can be resource heavy on a server) during editing --

I'm working hard on a FAQ section for YAF to be linked from the forums or place here for updatability and linked from other sites like YAF Wiki and GitHub...

---

I had actually (a) restarted IIS and (b) edited web.config files few days ago. This was for another bug (enabled blogspam and it was not letting admin post anything).

Both options above did not update the english.xml file. Only when the YAF app was manually restarted from admin settings, the new english.xml file was loaded.

That's interesting. touching web.config almost always is a failsafe for getting YAF or any ASP.NET / IIS application to restart. Now - it might require a 'change in filesize - such as inserting a blank carriage-return line' or something before IIS picks it up. But it was my understanding that IIS monitored web.config and anytime it was updated, it caused a reload.

ALTHOUGH - IIS can be configured to ignore and not restart a site if it's web.config changes - I just saw this in my 2008 configurations -- so there is a chance that web.config won't trigger a restart.

Additionally, Restarting YAF inside the app might cause it to flush it's caches and reload configs without actually 'restarting' the IIS application pool - -I haven't looked at the code.

In the future - give "Clear Caches" a shot in the Host settings -- see if that does it (be sure to hit a 'refresh' when you view a test page -- browser caching is hell.

---

I always thought restarting the IIS server would clear all memory and reload all files. I guess that is not true.

If you are creating a wiki, could you add this to the wiki (to manually click restart app of they upload any files from ftp).

I always thought restarting the IIS server would clear all memory and reload all files. I guess that is not true.

If you are creating a wiki, could you add this to the wiki (to manually click restart app of they upload any files from ftp).

I've also found that sometimes I have to force my browser to reload it's cached files from the themes - F5 on a page -- and it's reproduced immediate results without a cache clear in YAF or a restart. This applied to theme files though - not tested with other cache-able content...

---

Additionally, Restarting YAF inside the app might cause it to flush it's caches and reload configs without actually 'restarting' the IIS application pool - -I haven't looked at the code.

---