Troubleshooting notes

This page collects messages and anomalies that occur again and again and explains the cause of each. The entries are named after the message that the buyer or you get to see. If the problem persists or is not listed here, WEBSALE support can help.

“Document expired” after clicking Back

The buyer searches for something, opens a product from the result list, and then clicks the browser’s Back button. Instead of the result list, “Document expired” appears.

The cause

The result list is the result of a submitted form. Browsers do not simply display such a page again when going back, because they would have to resend the submitted data to do so. For a search term, that would be harmless; for a sign-in form or an order, it would not. That is why the browser prefers to ask or refuses to display the page. So this is not an error of the shop but a protective measure of the browser. The buyer can get to the list via the “Try again” button in the message.

What helps

Change the FORM-Search and FORM-QuickSearch forms to method="get". The search term is then in the address, there is nothing to resend, and the message no longer appears.

<form action="~FORM-Search~" method="get">

Change only the search forms. With method="get", the data is in the address, and its length is limited. That is enough for a search term, but not for address data, comments, and inquiries. Forms with file upload must use method="post" anyway.The opposite applies to the forms of the filter and sort functions, see the next section. Check which form you are dealing with before you change anything.

If you have built your own Back button into the shop that triggers the browser’s back step, the same message appears. A button that links to a known address instead of the browser history does not have this problem. Reference: FORM-Search · FORM-QuickSearch

“Not Found” when filtering and sorting

If this error occurs after basic link optimization has been switched on, check the form of the filter and sort functions. It must contain method="post".

<form action="~FORM-Search~" method="post">

Here, exactly the opposite of the previous section applies. The two cases concern different forms:

Form	Method
Search field, `FORM-Search` and `FORM-QuickSearch`	`get`
Filter and sorting with basic link optimization switched on	`post`

If you want to keep the sorting and also have shareable addresses, there is no way around post when basic link optimization is switched on.

Guide: SEO URLs and link optimization

“Your selected product could not be added to the basket”

The complete message reads: “Your selected product could not be added to the basket. Please enter the desired quantity or make a selection.” It appears even though the buyer has selected the variant and quantity.

The cause

The quantity input field is assigned a sequential parameter via PR-Quantity_Input. This allows several products in a list to be ordered with one click. If a product list is placed before the PR-Data area on the product detail view, this list increments the parameter. The actual product then no longer gets the number expected for a single product, and the assignment fails. This arrangement leads to the error:

{CAT-AdvData($C-Links,9)}
   {@PR-Data}
      <!-- Produktliste -->
   {/@PR-Data}
{/CAT-AdvData($C-Links,9)}

{PR-Data}
   ~PR-Name~
   <input type="text" name="~PR-Quantity_Input~" value="~PR-Quantity~">
{/PR-Data}

What helps

The actual product belongs before every product list:

{PR-Data}
   ~PR-Name~
   <input type="text" name="~PR-Quantity_Input~" value="~PR-Quantity~">
{/PR-Data}

{CAT-AdvData($C-Links,9)}
   {@PR-Data}
      <!-- Produktliste -->
   {/@PR-Data}
{/CAT-AdvData($C-Links,9)}

For set and grouping products, the list is inside the PR-Data area:

{PR-Data}
   ~PR-Name~

   {CAT-AdvData($SetProducts,999)}
      {@PR-Data}
         <!-- Produktdaten der Setbestandteile -->
      {/@PR-Data}
   {/CAT-AdvData($SetProducts,999)}
{/PR-Data}

The sequential parameter cannot be reset. The order in the template is therefore the only lever. Reference: CAT-AdvData() · PR-Data · PR-Quantity_Input

“Loading mixed active content was blocked”

The browser reports that it has blocked a component embedded via http:// in a page delivered via https://. Such components could be read or modified in transit, which is why the browser does not load them. Search the source code of the page for http:// and change the affected embeds to https://. This applies equally to scripts, stylesheets, images, and dynamically loaded content. If the message occurs in connection with the FACT-Finder suggest layer, first check whether this function is activated for your shop. Guide: Integration of the FACT-Finder search function

“Bitte vermeiden Sie Doppelklicks. Please avoid double clicks!”

On the order overview page ws_place_order.htm, WEBSALE V8s automatically generates a script that intercepts a double click on the order button. This message is part of it. This is not an error but a safeguard. Without it, a double click would submit the order twice. The behavior cannot be switched off. Therefore, design the order button so that it reacts visibly after the first click, for example with a loading indicator. Then the double click does not happen in the first place.

Econda Cross Sell is sometimes not displayed

The cause lies in the order. It is recommended to include the script below the display area within body. If the script is in the head, widget.render() is called before the display area exists. In that case, it helps to delay the call until the document has loaded completely. Guide: Integration of econda Cross Sell

WEBSALE V8s

Basics