by andperry » Wed Oct 20, 2010 1:43 am
Hi Steve,
Thanks for the reply. I've done a bit more investigation and still seem to be none the wiser. Here are some observations:-
1) I'm not so sure now that it relates to specific databases or even to later versions of Xataface as originally suggested. The problem seems to be more "across the board" than I had previously realised. The main reason why some tables don't give the problem is simply because in these cases the 'afterSave' function loads a new page by calling the PHP 'header' function followed by an 'exit' statement (e.g. to return to the table listing instead of staying in the saved record screen). The record is updated OK and everything looks OK to the user, but actually if you click the browser 'back' button you can still see the page with the error message.
2) With reference to the previous paragraph, I'm quite sure that I would be able to code appropriate workarounds for all databases/tables, and this might have to be the course of action in the short term. It still however doesn't change the fact that there is an underlying problem, which obviously makes such a solution less than ideal.
3) I've tried one of my databases with a Xataface application stripped down to the bare minimum of a 4-line index.php plus a very basic conf.ini and the problem still occurs.
4) The PHP/MySQL versions in use are as follows:-
Local Host (Windows) - PHP 5.2.11, MySQL 5.1.44
Online (Unix) - PHP 5.2.14, MySQL 5.1.48
Any further ideas/suggestions would be appreciated.
Regards,
Andrew.