Last post Aug 27, 2012 07:49 PM by mikemciver
Apr 27, 2010 05:48 PM|tpehrson|LINK
In a out of the box dynamic data site (linq to Sql) I've notice that when I navigate through list pages using foreign key hyperlinks to first the child table and then a grandchild table I am unable to back out using the back button to the original parent.
It seems that the parent page is gone from the cache. Has anybody come across this?
Apr 28, 2010 05:38 AM|sjnaughton|LINK
This is the correct behavoir, have a look at my sample here on adding ajax history to a DD site: AJAX History in a Dynamic Data Website
Aug 27, 2012 07:49 PM|mikemciver|LINK
Is this still the current/only solution? I was following the steps but got stumped on the mods to ~/DynamicData/Content/FilterUserControl.ascx.cs ... this ascx doesn't exist. Used the ASP.NET Dynamic Data Linq to SQL
Web Application project template.
Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.0.30319 SP1Rel
Edit: Actually I should explain the issue I have. Added class file with partial classes for tables to set DisplayName. DisplayNames render fine on default.aspx ... but when I use the back button, the real table names appear in the place of the DisplayName.
Using the home page link in Site.Master or the browser refresh, DisplayNames return. Also, created custom pages list.aspx, details.aspx for tables. Same issue exists for list.aspx. However, details.aspx always displays correctly even using the back button.
This dynamic data folder was added to an existing web application. I also use your DefaultAttributesTypeDescriptionProvider ... works great, Thank You. As a possible hint of the issue, I have a nav link in the top level Site.Master which displays based
on a sesssion var ... this link too has the same back button behavior problem, i.e. changes (disappears) but changes back (reappears) with the table DisplayNames on back button.
Edit II: Found most of the problem was the use of links without a file name, e.g. "~/somefolder" vice "~/somefolder/default.aspx". This appears to be a browser cache issue, i.e. cached pages with old(replaced long ago) graphics are showing up. Maybe this
post will help others sort out issues similar this thread's actual issue.