Jump to content

benanamen

Members
  • Content Count

    2,018
  • Joined

  • Last visited

  • Days Won

    38

benanamen last won the day on December 15 2020

benanamen had the most liked content!

Community Reputation

130 Excellent

1 Follower

About benanamen

  • Rank
    Master Coder

Contact Methods

  • Website URL
    http://galaxyinternet.us/
  • Yahoo
    phpfreaks@galaxyinternet.us

Profile Information

  • Gender
    Not Telling
  • Interests
    Email me at phpfreaks@galaxyinternet.us

Recent Profile Visitors

6,831 profile views
  1. Where does $url magically come from?
  2. You need to use Prepared Statements and your problem will be solved. NEVER EVER put variables in your query and NEVER EVER trust user supplied data. But as to why the problem, there are no quotes in your $_POST values. You have $_POST[article_id] instead of $_POST['article_id']
  3. Yes, stop using shared hosting and get a VPS.
  4. As far as file names, what DOES make a difference is underscore and dash to separate words. As simple search proves this out. On google search fast_cars and see returned result count, then try fast-cars. I get 13,000,000 results and 1,600,000,000 respectively Bottom line, use dashes as the separator.
  5. Take a look at my clean-pdo code repo. https://github.com/benanamen/clean-pdo
  6. Your code is vulnerable to an SQL Injection Attack. You need to use Prepared Statements. NEVER EVER PUT VARIABLES IN YOUR QUERY
  7. The form data is in the POST array which you do nothing with. Besides that, this code will be vulnerable to an Email Header Injection Attack if it were to work.
  8. Oh, so your a Domain Squatter. 🚩🚩
  9. The break tag (br) by no means goes anywhere within a Select element. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/select
  10. How about giving us a high level overview of what you have going on and the real problem you are trying to solve by doing this.
  11. You might want to tell us exactly what that error is. We cant see your screen and you posted incomplete code. What you did post is wide open to an SQL Injection Attack. You need to use Prepared Statements.
  12. When you are done, post a sql dump of your db tables and we will review it for you.
  13. Here's what I would suggest.. Back up your DB and Code-base Clean up your orphans Add the Foreign Keys Learn and implement cascading update/delete Clean up the unnecessary code You have been doing it "your way" long enough that the difference and time/effort savings will be very apparent. In a nutshell, but some fresh eyes on it and just try it. There really isn't much more to say about it. * I am assuming your DB is already normalized. If not, now is the time to fix it.
  14. Sounds like someone hasn't set unique indexes on the relevant DB columns.
  15. Sure, if you can tell me why the obsession with resetting the auto-increment. I will go first to save a post.... #1 reason to use Foreign Keys is to enforce Data Integrity. You can try and manage it yourself but if you get it wrong you will end up with orphan records (Bad Data). Wouldn't surprise me at all if you already have orphans. As soon as you try to set the FK's you will know right away if you do. It also clearly defines the links between tables (That would be the R in RDMS, Relational, AKA Relationships) Then you didn't learn how to do it. It is not complicated and is
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.