Jump to content

requinix

Administrators
  • Posts

    15,045
  • Joined

  • Last visited

  • Days Won

    413

Everything posted by requinix

  1. Given that the CSS you wrote is invalid and what you're trying to do isn't supported, Either restructure your HTML so that the input and your <p> are sibling elements, thus allowing you to use ~ or +, or use Javascript to apply a CSS class somewhere useful or to show/hide the paragraph element itself.
  2. Let me put it this way: you can't use Javascript to show or hide something without also using CSS.
  3. That describes the "ListDevicesDB" API you can call. 1. It uses the GET method. 2. You need to include a "token" header that includes some value. If the value is what you included in your post then that needs to change because this was (probably) supposed to be a secret value and you've now shared it with the whole internet. 3. The URL is as given there. It optionally supports a "deviceSerial" query string parameter, as the description indicates. 4. It doesn't describe what the return value is. So you need to get a basic API calling thing in place. You can use libraries for it, or you can write the API calls yourself using cURL. Your first step should be to understand more about making API calls through PHP. It's all the same everywhere - only differences being exactly what the API wants, and that's the information they gave you. Once you understand a little more about API calls, then you can deal with the PHP code to try to make them. It's pretty simple but you do need to know more about what this is all about to be effective at it.
  4. Are you sure you edited the right file? Did you restart Apache to pick up the changes?
  5. Use XSRF tokens to prevent people from submitting forms unless they are the user themselves, and use a reputable CAPTCHA service to (try to) prevent bots from using your form.
  6. Print out the value of the DOCUMENT_ROOT and see what happens when you try to add "../includes/db.php" to it.
  7. RDP servers are notoriously risk-prone. It's almost always a bad idea to have them open to the internet for anyone to connect to. By "tunneling" through the VPN, the RDP server remains disconnected from the internet, but you can still access it by connecting to the VPN (which is going to be much more secure). Ditto for the remote server. In your case apparently you need two hops, presumably because it's not accessible over the VPN directly, but the point is the same. It's very common to have a database server not connected to the internet, to minimize risk, so to allow access you can VPN or SSH into the network and then tunnel to get a direct database connection.
  8. If we're still talking about the original issue, my reply was trying to point out that you were rewriting everything when you should be rewriting only the things that don't exist. Also, followed by is funny.
  9. Preview? They might not have a name per se...
  10. It's rather unlikely that GoDaddy is running a PHP that isn't using mysqlnd. And I'm not sure that existed in the time of PHP 5.2. So this situation you're describing seems backwards. First things first, though: PHP 5.2 is extremely out of date. You need an version of XAMPP that has PHP 7.4 - to match what your real website is running. Frankly, I'm amazed XAMPP even provides PHP 5.2...
  11. If you're looking to hire somebody, try the Job Offerings forum. If you need some help doing the work yourself, we have a few forums according to the topic, such as PHP Coding Help and MySQL Help.
  12. Basically no. The query optimizer will rearrange the query as it sees fit according to heuristics that are probably better informed than you are. Generally, you want to write the query in the most logical way and let MySQL execute it however it wants. Post your query and an EXPLAIN for it.
  13. get_result is only available if you're using mysqlnd, the exact details of that being mostly irrelevant as virtually everyone should be using it by now. What version of PHP are you using locally, and what version is on your server?
  14. I don't see anything in our regular logs... Are you sure the message didn't get dumped into a spam folder? Ever had problems with signups (or just emails in general) from other sites? And a fun fact: the last person to sign up with an sbcglobal.net email was back in 2015...
  15. Once again: the "latest version" of Webalizer, this 2.23-08 that you found, is ten years old. https://webalizer.net/news.html Webalizer is dead, and the longer you insist on using it the worse things will be for you. No updates. No features. You're going to fall further and further behind on the sorts of things everybody else is using because they're using modern tools. Changing software sucks, I know, but it's very much worth the temporary discomfort.
  16. I can't think of a reason this code should be in place: it modifies where PHP stores session files, which PHP is quite capable of handling by itself. Why do you think you need this code?
  17. Has it always been slow/occasionally not returning, or did that change recently?
  18. Webalizer? You mean this one? Whose homepage dates to 2014, and tells you to download it over FTP?
  19. I don't see anything in this code that has to do with your PHPSESSID.
  20. Sure it does. I can't tell why you attached a sig.txt file to your post though.
  21. I don't know what you're asking or how to answer it either, but I can definitely confirm that the code you posted doesn't make any sense whatsoever and there is no reason it needs to exist.
  22. Basically anything that has "await" and/or "async" keywords works the same way.
  23. 800 isn't enough to run into the one or two PHP bugs I know of (which also have their own specific circumstances) but you should avoid putting everything into one directory on principle. Typically one partitions into ~a hundred or so per directory "tier". Though really, you shouldn't be storing stuff in files like this to begin with.
×
×
  • 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.