I have that obe website in one language only: in Khmer, so I have Km-KH enabled and en-US disabled. I had that website prepared for a long time as a subdomain of my university domain, but I then discarded it because it was developed on another system under Joomla.

As expected, the designer quit and I was asked to take over. The problem was that he was requested for features that were not standard present in Joomla.

Moving the data to DNN and create modules in DNN seems like a faster option than learning PHP and then develop the website further under Joomla.

So, I started creating a skin for the new site and the first object to go in is the logo.

First finding: Saving my logo in portal settings: the settings do not persist.

Second finding: My portal localization settings are in disarray. So I manually clean up this table.

Third finding: Saving my portal settings still disregards the logo source. Actually, checking the portal localization table, I find that DNN has modified the settings for en-US (disabled in this portal), rather than km-KH.

After copying that file number to the settings for km-KH, my logo still does not show up.

As I said, I have opther priorities. So I put the logo directly in the skin with an img tag, instead of a logo object and only I know that I cheated.

Conclusion: 5.6.2 is still too buggy. Whether I want it or not, I will be forced to move my production sites into DNN 6 to get rid of these issues. I had been hoping so much DNN 5 would end with a stable version like DNN 4 but that seems to have been idle hope.

---

____________________________________
The one-eyed in the land of the blind.

PS: saving portal settings no longer produces garbled entries for the culture code column in dbo.PortalLocalization.Leftover from past issues?

---

____________________________________
The one-eyed in the land of the blind.