Skip to main content

Timeline for PHP gaming community website

Current License: CC BY-SA 3.0

7 events
when toggle format what by license comment
Apr 18, 2016 at 9:05 comment added Pimgd I'd agree with this approach as well - I don't know where the OP is in his life, but personally I have a job and I don't have the time to undertake such a big project ... for less than 300 users? I'd fix the security holes, maybe check in with the top parts of the community to see if there's any easy features (on the scale of 15 minutes to 1 hour) to stick in. But that's that... There's just no time to spend weekend after weekend on something like this.
Apr 18, 2016 at 0:43 comment added Criticizing Israel not allowed If you want to rewrite it and stay with PHP, then you can try to rewrite one page/module/function at a time.
Apr 17, 2016 at 13:27 comment added RedDragonWebDesign I edited my post to include my site's security features.
Apr 17, 2016 at 11:31 comment added tim If the OP doesn't want to take the website offline, patching it up in a day may be a temporary solution, but I wouldn't feel good hosting anything like that on my server. Security really isn't something that you can just add on as an afterthought, you need proper mechanisms in place. I do understand that "just rewrite it" is suggested too often, but with such an old and broken website, it really seems like the best approach.
Apr 17, 2016 at 11:31 comment added tim My problem with this approach would be that 1) these are unlikely to be the only security issues. The code was written 13 years ago, with no concern for security. There are likely to be insecure includes and file uploads, and insecure use of potentially dangerous functions such as extract, eval, etc all over the place 2) patching it up will catch many of the insecure queries and prints, but it is extremely likely that some will be missed. 3) If you think that the website is so complex that a rewrite will take a year, I doubt it can be made even somewhat secure in a day.
Apr 17, 2016 at 10:34 review First posts
Apr 17, 2016 at 15:31
Apr 17, 2016 at 10:31 history answered James CC BY-SA 3.0