Jump to content

requinix

Administrators
 View Profile  See their activity

  • Posts

    15,264

  • Joined

  • Last visited

  • Days Won

    431

 Content Type 

Everything posted by requinix

  1. requinix
    1. In order for Javascript to find the #input-id element, it needs to exist in the browser's DOM - that's the internal model that the browser uses to manage the page. 2. When you put things into the <head>, they happen immediately as the browser is loading the HTML markup it's receiving from the server. 3. Your datepicker input is somewhere down on the page. Putting those together means that DOM stuff in the <head>, such as using getElementById, is not going to work in 99% of cases. You're simply trying to do things too early and they're not available yet. The right way of doing this is to wait until the DOM is ready. Exactly how depends on what/whether you're using Javascript libraries, as most tend to give you an easy way to hook into that without worrying about the details; the classic example is jQuery's $(function) syntax. But for a simple, non-library method, it's generally sufficient to put your DOM <script> stuff at the bottom of the page. Browsers build up the DOM as they go, so putting your scripting at the bottom of the page generally means that the rest of it is ready to use. <html> <head> <!-- these resources will be loaded immediately when the browser reads the page --> <link href="css/hotel-datepicker.css" rel="stylesheet"> <script src="js/fecha.js"></script> <script src="js/hotel-datepicker.min.js"></script> </head> <body> <script> // #input-id does not exist yet... </script> ... <input type="text" id="input-id" name="datepicker"> ... <script> // now it does var hdpkr = new HotelDatepicker(document.getElementById("input-id"), options); </script> </body> </html>
  2. requinix
    This page lists their supported platforms. It doesn't go back far enough to list MySQL versions that existed around the time of Windows XP. Unsurprisingly. If you look at the Important Platform Support Updates, you'll see they killed XP support around 2014. Pull up the platforms page on archive.org around that timeframe, or a little later, and I bet you'll have an answer.
  3. requinix
    If the scanner cannot be told to ignore this warning, there is a minor modification you can make to the code that I suspect will "resolve" it...
  4. requinix
    There's no way we can tell you whether this file meets "legal regulations" and, since we don't know anything about you, all we can do to judge whether the file is safe is to venture guesses. It appears to be a valid file, even if it does some risky things - the scanner may have noticed the "eval" at the bottom, which allows executing arbitrary code - and follows some outdated and discouraged practices, and it does not appear to be malicious. You should confirm that the file hasn't been modified recently: something like this should not have received any recent modifications, and likely would be dated to the same time frame as many other files on the site.
  5. requinix
    String needs to be in quotes. You've got one set on the outside for PHP, another set on the inside for the HTML attribute, and now you need a third set for the Javascript string. You have three options: // raw double quotes, but escaped because of the PHP quotes $out .="<tr class='align-middle custom-lc' onclick='triggerClientContextMenu($cId, \"$coName\")'>" // double quotes as HTML entities, which won't conflict with PHP's quotes $out .="<tr class='align-middle custom-lc' onclick='triggerClientContextMenu($cId, &quot;$coName&quot;)'>" // single quotes as HTML entities, which won't conflict with the HTML's quotes $out .="<tr class='align-middle custom-lc' onclick='triggerClientContextMenu($cId, &apos;$coName&apos;)'>" These three options may leave you open to problems if $coName contains apostrophes and you haven't protected yourself against that. A fourth option is to run $coName through json_encode and then htmlspecialchars with the ENT_QUOTES flag (and them in that order), after which you can put it directly into the "code" without manually adding quotes. But the fifth option is better: take a whole different approach to this by not using 1990s' web techniques like inline Javascript handlers...
  6. requinix
    Does this triggerClientContextMenu(1, Company Name) look like valid Javascript code?
  7. requinix
    If you need a count then array_unique won't help you. There is one that can help, though, in this list. To output something before each "word", what have you tried so far?
  8. requinix
    I've heard opinions that if a piece of data (read: column) will often be null then it should be moved into its own table. I don't agree. Ah, then that means a one-to-many relationship and you're forced into creating that third table.
  9. requinix
    Generally, the first step for something like this is to figure out what sorts of "entities" you have. Don't think about it in terms of database tables: you're modelling the real world right now, not what you put into the software. These things tend to stand out on their own, like you could look up the data for each one individually. "A question" and "an answer" are the two most obvious things; you could think of "an image used in a question" as one as well, but I don't. Then you figure out relationships between your various entities and the pieces of data - "has one of", "has many of", that stuff. If you could have more than one of a thing then it almost always needs to be a separate entity (if it wasn't already). So here, I think Questions ID Type Text Image path Whether the image is inline or opens separately Answers ID Question FK Text Maybe a priority/sort order for arranging the answers Whether it's the/a correct answer The questions and the answers are obviously their own logical entities. I don't think the images are, like I said, unless you wanted to reuse images for multiple questions. You could still do it if you really wanted to, of course. The relationships are "each question has one-or-more answers" and "each answer belongs to one question" (I assume). That means answers must be their own entities, but that was already established. The fact that it's one-to-many means you don't need an association table and can just use regular FKs; if you were to decide that "each answer could belong to multiple questions" then you have a many-to-many and be forced into creating that third table. Likewise, I wouldn't say you need a separate table to associate a question's correct answers: the relationships there are "each question has one-or-more correct answers" and "each correct answer belongs to one question" (unless not, but this one's even less likely), which is identical to their general relationship and so fits into that system naturally without needing anything more than an "is a correct answer" flag.
  10. requinix
    Seems to be working correctly. You do realize that you have nothing in that header except for a tiny image applied as the background, right?
  11. requinix
    There isn't an error because you didn't write any code to do that. If you want to show an error (and also redisplay the form) then give PHP appropriate code for it. It'll be a little awkward, though, considering your form is shown before you try to process it. Any errors you try to show will display below the form, which isn't where people would normally expect to see them. It's actually quite backwards from how things are normally done. You should rearrange your code a little so that (1) if the form was submitted you process it, and then (2) you can show the form (if you want) with appropriate error messages (if you want).
  12. requinix
    Presumably both of them do so to match the original mysql, whose fetch_array returned the combined form. And I'm going to guess it did out of some sense of "maximum usefulness, minimum effort": call the thing that returns an array and you can use it however you want. $_REQUEST will have come out of that same sort of mentality too, back when PHP was treated more like a templating system than a programming language.
  13. requinix
    You don't have to if you don't want to, but it is the package management tool for PHP. And it's not like you have to install any actual software - Composer is, itself, also PHP code that you can simply run.
  14. requinix
    Those are just PHP libraries. PHP code. They'll work just as well as your own code does.
  15. requinix
    1. CAPTCHA 2. CAPTCHA 3. Use a mailing library like PhpMailer or SwiftMailer instead of doing it yourself with mail() - not least because they will construct proper emails that are less likely to hit your spam filters 4. CAPTCHA
  16. requinix
    Parentheses are for grouping. You use them when you want to deal with things as a group instead of each one individually. "Alice is driving to work, and Bob is driving to work, and Cindy is driving to work": the three of them are each taking their own cars to work and contributing to local traffic problems. "(Alice and Bob and Cindy) are driving to work": the three of them are carpooling like responsible human beings. Having parentheses for the sake of having parentheses is wasteful but not inherently wrong. But when you throw other things into a regex, like + or *, and to apply them to the parenthesized group, then you change what the regex does. "(Alice and Bob and Cindy)+ are driving to work": there are some number of people, every one of them named Alice or Bob or Cindy, and they are all driving to work together in one comically-oversized minivan. "(Alice and Bob and Cindy)* are driving to work": maybe there are three people driving to work, or maybe there are more than three people, or maybe there aren't any people at all because it's the weekend and they don't work on the weekend. Try this.
  17. requinix
    No. When testing software, your goal should be to break it. To make it do something you don't want, or to not do something you do want. Simply testing some examples of what you want and what you don't isn't enough. Since I have other things to do today, $pattern = "/^[A-Z][a-zA-Z '&-]{1,48}[A-Za-z]$/"; Try both your solution and my solution against the string AbcdefghijklmnopqrstuvwxyzAbcdefghijklmnopqrstuvwxyzAbcdefghijklmnopqrstuvwxyz
  18. requinix
    Then you didn't test it very well. Nevermind your current problem. Go back to what you had before and make one simple change to it. That's the puzzle for you to solve: there is a single change - replacing one thing with another - that will make your original regex do what you need to do.
  19. requinix
    You've tested that with things you want to allow, I assume. Did you test it with things that you didn't want to allow?
  20. requinix
    Think about it a little more: 1. The name must start with an uppercase letter. You already have that. It will account for 1 character. 2. The name must end with a letter. You already have that. It will account for 1 character. 3. If you require 3-50 characters total then that means the part in the middle must be between ___ and ___ characters long.
  21. requinix
    Stop using IDs.
  22. requinix
    MDN, mostly. MSDN has some stuff too.
  23. requinix
    I'm suspicious of your action.js. Please post the exact contents of that file. And you're sure there are no errors in your browser's console at all? So you load the page, open the console, and it says nothing?
  24. requinix
    "Uncaught TypeError"? What is the uncaught TypeError it speaks of? There should be more to the message than just that...
  25. requinix
    1. IDs are unique. You cannot have more than one #from or #to on your page. Find some other means of identifying which inputs you want datepickers on. 2a. If you create a bunch of elements and some of them need to be hooked up with some Javascript stuff, (and you can't apply the Javascript stuff globally,) then hook up those new elements with the Javascript. 2b. When applying the datepicker, all you need is some jQuery collection - you can do whatever it takes to get a collection of the elements you want. 2c. There are multiple easy ways to have jQuery return you a set of elements somewhere specific and not across the entire document.
×
×
  • 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.