I was certain I was editing the correct file.
Now that you hinted at it and I verified.
I’m certain I’m editing right files. Moving any part of dependancies or the script itself change the outcome (missing (removed) functions “fatal error missing functions”, die() (in middle of executions) etc.) react way that they should. But this error is still there. I am changing the correct files.
Your solution has brought to me to think about something.
Which I used to solve a problem. Which made 3 new problems,
that I also solved, now there’s a new problem, which doesn’t make
sense, I know why, but I don’t know how.
As of prepared statements. My stupid host doesn’t support prepared statements, and finding good free hosting is pretty tough (for presentation). Don’t suggest anything, and don’t ask why they don’t support prepared statements. I don’t know. I don’t care, I just want to be done with this stupid job.
As for PDO. This has been suggested a lot. And I wanted to start “learning” it and apply to my future projects, but for this one I have to stick with old trashes. Using PDO would take longer time than struggle with whatever I’m doing.
Essentially you fixed the problem, so thank you, I’ll have to make new thread for new problem.
they dictate what databases you can access but PHP dictates how you can access them and both of the access methods that PHP support allow for prepare statements to be used.
The host cannot dictate what parts of PHP they do and don’t support - just which versions of PHP they support. Only PHP 4 (now over 10 years dead) did not support prepare statements and those working on PHP itself only support PHP 5.6 and PHP 7 so if your host isn’t providing one or both of those then they are not providing a current version of PHP and you need to find a new host if you want to use PHP. If your host only provides PHP 5.5 or earlier then don’t use their hosting for PHP as those versions of PHP can contain security holes and other bugs that will never be fixed.
YOU HAVE THE PREPARED STATEMENTS ON YOUR HOST. Period.
I dunno what are your reasons to deny the fact. May be you don’t like the prepared statements yourself or your host is lying to you, but from your question it is obviously evident that you have full support for the prepared statements. Your question title says that your code is using mysqli. And mysqli has full support for the prepared statements.
I DON’T HAVE PREPARED STATEMENTS ON MY HOST. Period.
My reason to deny that “fact”. Is when I crafted prepared statement script on my computer, it worked, then I uploaded and errors started popping out. They looked extremely cryptic and no, those weren’t faulty SQL queries or misconnections.
Anyways, I’m not here to argue. I’m done. You can keep telling me to turn on the lightbulb, and I can keep telling you we’re in Middle Ages. You’re not here to witness.
Ok, it’s clear now. Your reasons are the error messages that were “too cryptic” for you. So you can keep thinking your technology is the middle ages. Just don’t forget to tell that the customer you are trying to sell the code to.
Who is your hosting provider may I ask? I would like to research and see if they do support prepared statements or not. It’s quite odd that hosts like yours don’t support prepared statements. Makes it worse since 000webhost is free and supports prepared statements and they’re running on 5.2 as well. If you are using a free hosting provider, I suggest using something other than that current one you have.