(adsbygoogle = window.adsbygoogle || []).push({}); Please delete this thread.

I’m going to assume my help isn’t wanted. Take what I have said and learn from your mistakes. You will become a much better developer.

I just took a look at this and you have a pretty big bug on redirects:

    

	    if($_SESSION['rank'] == 0)

	    {

		    header("Location: pages/banned.php");

	    }

You can ignore HTTP 302 redirects with some browser extensions. Having that code will indeed set the header, but the script will continue to execute regardless of what happens. If you installed one of these extensions, you could access any page where this is being done on, regardless of permissions.

Simply die() or exit() the script after the header function call to fix this, like so:

    

	    if($_SESSION['rank'] == 0)

	    {

		    header("Location: pages/banned.php");

                    die();

	    }

That's just one of the bugs

this source did take about 4 or 5 hours to go threw and fix all the bugs and security issues but its saved me about half the time i would have used coding it all from scratch

I'll be extremely surprised if you've fixed all the bugs in this. There are lots.



That's not an issue connecting, that's an issue performing an UPDATE or INSERT by looks of it - again, just another bug.

well if your going by your standards prob not but as far as all the important ones like the security bug in the js that lets you make ur own key just by knowing the url and stuff along those lines

How about the one where you can reset the main admin password by entering just a single character?

I stand by what I said earlier in this thread, using this script in any form (and even by attempting to patch certain bugs) you are leaving a huge exploit vector for attackers to manipulate. It is unsafe to use in any form and I highly recommend removing it in order to protect yourself and your users.

this was while back when source was released i have changed i think about 90% of it by now.

but i agree it is alot of shit to fix and change to use this source i would recommend against it also

The original developer has barely pushed an update since releasing this pile of shite, so if you're using an extremely old version, not only was it outdated code, but also likely more vulnerable.

I just find it hard to believe you can say you've changed 90% of the code, yet you say it's "still saved you a lot of time" - I could write something that does exactly what this does in a day, and it would be a thousand times better than this.