Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We use iframes, POST and php all the time at our company. I'm not aware of a particular problem for this setup. I suggest you look elsewhere for problems because iframes and post are pretty basic, standard stuff.</p> <p>Also, php doesn't loose POST data and still continue to process the request. I'm guessing that what really happening is the request can't really reach the server (network connection problems) or server couldn't process the request (server configuation problems), answer doesn't get stored in the database, the visitor gets bored and retries thus making a new request (without the answer), visitor is greeted with first question again.</p> <p>So, where to start? Here is a couple of pointers i can think of:</p> <ol> <li>Ask your customer how often does this happen, does it happen at certain times (for example peak times like morning) or with certain people or with certain browsers or ... you get the idea.</li> <li>Look at apache's access_log and error_log for HTTP status codes other than 200, php warnings or errors.</li> <li>Look at mysql's error_log, slow_query_log for errors or warnings.</li> <li>While you are at it, look at /var/log/messages</li> <li>Add debugging code to your site for example when the site catches that visitor did not answered first question and redirect him/her to first question, log some data about it to some txt file on disk or to some table in database.</li> </ol> <p>These should shed some light on the nature of the problem you are facing with.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload