IMPORTANT NOTE: If you recently started experiencing this error, and it consistency occurs while editing an Order, Uploading an Image, or when using the shop's Contact Us page, than please download & install the latest revision of your edition of PDshop. Earlier revisions of some of PDshop's .aspx scripts may not work with newer versions of Microsoft's ASP.NET Framework.
While we recommend downloading the latest revision, which usually does resolve the above issue, you can try a different approach (although it's not recommended unless the above solution does not work). An alternate solution would be to add the EnableViewStateMac="false" code to the "pages" settings of the system.web section of your web.config file.
For example, in your web.config change:
<pages buffer="true" enableViewState="true" enableSessionState="false"
autoEventWireup="true" validateRequest="false" />
To this:
<pages buffer="true" EnableViewStateMac="false" enableViewState="true"
enableSessionState="false" autoEventWireup="true" validateRequest="false" />
MORE INFO & ADDITIONAL TROUBLESHOOTING:
Like most asp.net applications, PDshop relies on certain features built into Microsoft’s .Net Framework (built into your web server). In order to facilitate fast loading of pages and what’s known as “postback” features, PDshop utilizes Microsoft’s Viewstate functionality.
If you receive an asp.net “Viewstate” error after clicking “Save” or “Continue” in PDshop or PDAdmin, this can indicate a web server problem. However, if you have left your web browser open for a long period of time, or configuration on the web server was changed while you were on a PDshop page, you may need to close your web browser, and then restart it (or, clearing your web browser's cache and temporary internet files may resolve this).
If the problem persists, than it’s likely your web server is out of resources (such as memory) and may be prematurely discarding asp.net viewstate data from its memory, the server is rebooting/recycling abnormally, or there is a configuration problem with the web server itself. For these issues you would need to contact your web hosting service (or the server’s administrator).
NOTE: if you are using a “shared” web server, this problem can be an indication of an overloaded server; in other words your host may have more clients/websites setup on your server, than the server can physically support. Or, you may have reached the limitations of shared hosting (in which case a better plan or dedicated server is recommended).
