QRZ
You are discovering that developing code in this server and browser environment can be tricky, often several different languages in use, and in environments that keep you at arm’s length.
What I do is output a running narrative of how the code is executing, where it has got to, and what values it has calculated. Because of the segfault, you will be examining where you got to before the fault, and commenting out crucial calls. This will identify just which call and what arguments are causing the segfault. I wish there was an easier way.
I have checked, your code has no syntax errors.
http://www.piliapp.com/php-syntax-check/
I notice that many of your id fields and names have a leading digit (“2”), is this good practice ?
Hi,
I guess that’s the problem. It never actually gets to the next page. I enter my data, and then press save, it waits for a few seconds, then comes up with this program has stopped working message for apache. My only thoughts are the sanitization functions I defined are doing it, unless it’s something in wordpress itself.
I’ll definitely see what I can figure out with your suggestions though.
As for 2mb with 2 in front, I’m not sure if it’s good practice or not, I just did it because that’s the beginning of our website.
Thanks,
-Michael.
You are crashing in one of:
* WordPress functions
* PHP functions
* underlying mySQL functions
I don’t see many other options.
So progressively comment out various categories of function call. Take out more and more until it no longer crashes, then re-enable functions until it starts crashing again. You will end up with a minimal functional program which does not crash, one in which un-commenting any function causes it to crash again.
Then the question can be re focused onto why.
Hi,
Thanks for your advice. I will go ahead and start doing this.
-Michael.
