I just installed the 6.9.4 update and am having problems navigating to the correct product from both the products.asp and categories pages. When I go to the details page from https://www.theposhpeddler.com/products.asp?cat=2, for example, and click the links, the first three bring up the correct product. After that, while the correct product is listed in the address bar, it continues to display the product from an earlier link. This happens even when I click the Previous l Next button at the bottom of the page and when I attempt to navigate from and category in which I have products listed. The same issue happens whether I use ie, chrome or Firefox.

Hi luc627
Also, the pages seem to be throwing a 404 Not Found error when they do seem to be being found. Have you tried looking to see if you have any strange entries in the .htaccess file? Also, have you tried asking your host to see if they have any idea?

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Thanks Vince. I will check.

Ooops, I mixed up the forums and there is unlikely to be an .htaccess file on a windows server, but do ask the host as those 404's are pretty strange.

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Problem solved. The Customer Service at servelink.com is amazing. My web.config file had to be changed:

"You had this block of code in your web.config file:

<caching>
<profiles>
<clear />
<add extension=".ico" policy="CacheUntilChange" />
<add extension=".js" policy="CacheUntilChange" />
<add extension=".css" policy="CacheUntilChange" />
<add extension=".jpg" policy="CacheUntilChange" />
<add extension=".png" policy="CacheUntilChange" />
<add extension=".asp" policy="CacheUntilChange" />
<add extension=".aspx" policy="CacheUntilChange" />
<add extension=".php" policy="CacheUntilChange" />
</profiles>
</caching>
per Microsoft, server side output caching is unnecessary for static resources and as you have seen causes undesirable behavior with dynamic pages. I replaced with this instead:

<staticContent>
<clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="30.00:00:00" />
</staticContent>
which will promote client side caching of static resources only.