Last post Sep 13, 2005 10:33 PM by edison135
Sep 12, 2005 04:35 AM|edison135|LINK
Sep 12, 2005 04:20 PM|jfetters|LINK
Which portal kit are you using (C#/VB & SDK or non-SDK)?
Sep 13, 2005 05:57 AM|edison135|LINK
Sep 13, 2005 12:54 PM|kthorne|LINK
Sep 13, 2005 01:13 PM|jfetters|LINK
Sep 13, 2005 02:19 PM|kthorne|LINK
I don't think this is a language issue, though I'm using the c# kit too. Like I said, I'm seeing the cache act normal on my local IIS but on a remote host the cache dosen't presist more than a fraction of a second. I'm guessing there is an issue outside
of the language
For what it's worth, I found this info:
These values remain in the web server cache until one of the following events occurs:
When I find a resolution I'll post it here; but I'm out of time for now. Good luck.
Sep 13, 2005 06:02 PM|kthorne|LINK
tabRow.TabOrder = tabOrder;
This updates that row's tab order column with it's new position but this apparently is not always updated in the cache's version of the dataset. To correct this add the follwing line after the above line:
HttpContext.Current.Cache["SiteSettings"] = siteSettings;
This updates the cache's dataset with the new position as well so that the following call to SaveSiteSettings() will see this change.
Seems to have worked for me. Good luck and I welcome any explaniation as to why this isn't needed in some environments while it seems to be needed in others.
Sep 13, 2005 10:33 PM|edison135|LINK