Jump to content
Larry Ullman's Book Forums

Larry

Administrators
  • Posts

    5394
  • Joined

  • Last visited

  • Days Won

    154

Everything posted by Larry

  1. Hey! Good questions here! For question 1, there are two facets. First, the database needs to store the product+size+price combination, which is already supported. (I forget if the admin interface allows you to set different prices for different sizes or not.) Second, on the client-side (in the browser), you'll need to use JavaScript to make the magic happen. You'd use an event handler to watch for size changes and then update the price HTML accordingly. I think I'd be inclined to have the PHP script pull all the sizes and prices first, and store these in a JavaScript object. Then, when the size changes, the JavaScript uses that object to update the HTML. For question 2, with the current database structure you'd add a colors table and then a color column to the database, so you create a new SKU for each color. Hope that helps but let me know if you have additional questions.
  2. (Resolved over email...) The publisher has PPT slides available; there aren't sample tests or homework assignments.
  3. You've already done all the hard work. Kudos! You have the values you need, as an associative array. All you need to do now is pop those values into an INSERT query, something like $arr = json_decode($json, true); if (!empty($arr['isbn'])) { // Basic validation that data was returned... INSERT INTO books (ISBN, title) VALUES ('{$arr['isbn']}', '{$arr['title']}'); Although it'd be best if you use prepared statements or somehow sanitized the values before using them in the query.
  4. If you're concerned about a fake ID scenario AND such a query not affecting any rows is cause to stop execution of the code, you could run a SELECT query using the ID first to validate that it's real before running the UPDATE. That being said, doing all that seems to me like adding extra overhead to "solve" a problem that's not really a problem. The UPDATE query, like on a password change, should use the primary key, which is immutable, and therefore not user-provided. It's unclear how a fake ID would get into the mix.
  5. Thanks so much for the nice words! I really appreciate it. This is an excellent question! What you can do is just use mysqli_query() as the conditional. The function returns a false value if it didn't run (i.e., there's an error), which is a different thing than the query running but not affecting a change. https://www.php.net/manual/en/mysqli.query.php
  6. Thanks for your interest and sorry for the delayed reply. Right now there's no plan to update the PHP Advanced book. I've not even spoken with the publisher about it. Thanks again, though, for asking!
  7. If you just google "xampp mail server windows" you'll find plenty of tutorials on the subject. (I don't have XAMPP on Windows, so I don't know off the top of my head.)
  8. From there error messages, you have two issues to resolve. The first is you haven't configured a local mail server. The second is your error handling script still references the $e_vars variable, which it no longer has defined as an argument.
  9. There are two issues here. One is that there's an error going on in the script. The second is the error handling isn't working properly. For the latter, you don't mention what version of PHP you're using, but I expect the warning in the box applies: https://www.php.net/manual/en/function.set-error-handler.php Remove the last parameter from the my_error_handler() definition, as well as the use of that $e_vars variable within it. Once you fix that, you should properly see the actual error that's happening on the page.
  10. Glad that's working for you and thanks for letting me know about the emails. I'll look into it. Cheers!
  11. My inclination is it's either not being stored or retrieved in a format that PHP can use. I'd check/confirm your column type. Also, it's best not to use "Date" as a column name since it's also a keyword in MySQL. That being said, I'd have MySQL return the data in the format you want, rather than ask PHP to convert it.
  12. Hey Max. Kudos for figuring it out and thanks for sharing the solution. The first thought that came to my mind would be to store the coordinates in separate columns. In other words, split the coordinates upon receipt and then store them in two columns. That'll make future work easier to do.
  13. Hey Nick, are you setting a "from" address when you send the email? Also, it may help if you use placeholder values when describing the problem here. I'm not 100% sure I understand the distinctions you're trying to make (e.g., sending the email to me vs receiving an email or all the uses of "me").
  14. So you have the script D:\xampp\htdocs\phpmysql4_scripts\ch09\view_users.php which is including ../mysqli_connect.php. The ../ bit means "go up one directory from the current directory". Up one directory from D:\xampp\htdocs\phpmysql4_scripts\ch09 is D:\xampp\htdocs\phpmysql4_scripts, so the code is looking to include D:\xampp\htdocs\phpmysql4_scripts\mysqli_connect.php.
  15. Hey Marie. From what you describe, if the problem isn't with the database then it's with your code. In other words, it could be giving you that error message for the wrong reason. Looking through the downloaded code, I don't think this book uses a "form functions" file but it does use a login functions file.
  16. Thanks so much for the kind words and for the interest in a Python book. I truly appreciate it. Unfortunately I'm not well versed in Python, so that's not in the cards. Thanks again, though!
  17. Yes, that would be my assumption: that it's doing a conversion. If it wasn't, then the SHA2() function would return an error for an improper argument.
  18. Thanks for your questions and for the nice words. For the first question, when executing queries like this, there really is no "automatic". In a real application these queries would be executed by code that verifies the results as part of the process. For example, using PHP you could start a transaction, fetch the balances, adjust the balances, fetch the new balances, verify, and then commit. For the second question, what you describe is called a "race condition" and can be prevented by implementing locks. So you'd lock the row, run one update, and then unlock the row. A subsequent query that would theoretically make a quantity negative (assuming that wasn't allowed) would then fail.
  19. Thanks for your question, and for your patience! Mostly it's just hard--nearly impossible--to have a full-time job and a family and a house, etc. and work on the book. This is part of the reason why I don't spend any time on social media, too. However, finishing the Yii book is always on my mind. In fact, I took two weeks of vacation last month and spent that on the Yii book. I got a rough draft of half of what was remaining done. I still have the last five chapters to rough out, and then polish these last eight. So the short answer is: yes, it's still being worked on and I just made some decent progress by using my vacation time, but it may still be a while before I complete it.
  20. Yeah, that'll do it. Kudos for figuring it out and thanks so much for sharing the solution!
  21. It might be best if you start coding by documenting what you want to do and then convert those comments into code. For example: Add a record to the products table. Get the product ID for the record just added. If there are sizes, add one record to product2size for each size. This uses the product ID already fetched and the size ID, which comes from the HTML. If there are product categories, add one record to product2pcat for each category. This uses the product ID already fetched and the category ID, which comes from the HTML. So with that written out like so you can see for starters that you don't need to fetch the product ID multiple times, just once will do. You'll also see that steps 3 & 4 are parallel, not dependent upon each other (from what I can tell). But your code for step 4 includes "isset($sizeError)". I don't see why that's there. That may be why the third query isn't running? From the code and your comments it looks like the second and third queries could be executed in either order as neither depends upon the other. There's nothing particularly special about running these three queries. I think you have some logic issues. As I recommended before, if you use a slew of print statements you could see what is or is not true or happening. It's a blunt debugging tool, but it works. Another likely cause of confusion is you're using both prepared statements and non-prepared statements. That's not really a good idea, from the point of comprehension. Moreover, you're not using prepared statements for the two queries that would benefit the most from the prepared statements. By using prepared statements the second and third queries can be executed within the foreach loops, nicely.
  22. One issue I can see is that you call `$product_id = $stmt->insert_id;` a second time, but you already have the $product_id value, so that shouldn't be necessary. And there's a good chance `$stmt->insert_id` won't return anything a second time it's called, but I could be wrong about htat.
  23. Could you be more specific than "the query did not run"? Did PHP attempt to execute the query but it didn't succeed? And, if so, what was the MySQL error? Or is it not getting to that point in your code where PHP is even trying to execute the query? You may want to litter your code with print statements to see what is or isn't happening, and what values exist where.
×
×
  • Create New...