Jump to content

Jessica

Staff Alumni
  • Posts

    8,968
  • Joined

  • Last visited

  • Days Won

    41

Everything posted by Jessica

  1. You need to check if the $_POST variables are set before trying to access them.
  2. Sometimes yes, sometimes no. If it's one or two lines, I'd probably put it in the body. That's what I mean by depending on the script. Would a broswer that old be able to run jQuery?
  3. It's also best practice to put all JavaScript in your <head> and not at the bottom of the page. I think it depends on what the script is. Should you create a separate JS file for something that will be used one time? I have read the best way is to put them at the bottom of the page, and when you're doing jQuery, a lot of what you do is just functionality for one page and should go at the bottom of that page.
  4. Reminded me of this: http://comedians.jokes.com/anjelah-johnson/videos/stand-up--anjelah-johnson---you-got-to-yahoo/
  5. That is serialized data. Use unserialize on it.
  6. He never said anything about a database, and you've refused to try the suggestions made to you.
  7. echo your $query before running it and see if it looks the way you expect. Try running it in a tool like phpmyadmin and see if it works. What does your data look like
  8. $result will still be a valid resource if the query returns 0 rows. I thought it was, but I had a brain fart. Ty.
  9. Show the code that processes $_GET['name'] - just the relevant code
  10. $i is not defined before your if. turn on error reporting to E_ALL And that is a great example of if/else that should be written as a switch.
  11. Try putting all of the text into a string, then you can write the string to the file and output it, rather than using ob_get_contents(); I don't know if ob_get_contents will work for html that is not echo'd by PHP? Maybe not? Also $Name is the only one you've defined. If error reporting is indeed on, you'll get many notices about your script.
  12. For pete's sake if you want help at least show us you care enough about what you're doing to sit down and write a proper sentence explaining what is wrong and what you want, and demonstrate that you've tried the suggestions already. Spelling matters.
  13. 1. Don't surpress errors (@) 2. Is error reporting turned on and set to E_ALL
  14. You need to check if $result is not false before attempting to use it. $result being false means your query failed or returned no rows.
  15. Wow, you realize he was agreeing with you about the OP's site, right?
  16. Wait, I think you have this backwards. The purpose of modrewrite it to accept a URL like http://www.mydomain.com/profiles/tutors/1255/Kasun+Perera and translate it to http://localhost/tutor_institute/profiles/tutors/index.php?tutorCode=1255&tutorName=Jhon Amarathunga&city=Perth So that index.php gets run. It does not change the URL in your existing link attributes.
  17. Okay that's not tabs then that's just AJAX. Did you put that javascript code at the bottom of the page? And it needs to be wrapped in $(document).ready(function(){ //your code here }); I would install firebug and test it out in Firefox, and look for errors there. If you add alert('test'); before the load call, does it alert you?
  18. This is a prime example why there's enough work out there for the rest of us. And why after a while, you refuse to work on existing code. If a small business comes to me and says they need me to fix something on their site, 9/10 out of ten it's not worth taking the job.
  19. <?php if(){ }else if(){ }else if(){ }else{ } ?> Also, see switch
  20. Even when you do a plain <style> section rather than a separate file, doesn't it have to go within the HTML, not before your opening html tag?
  21. For future reference, that means In My Opinion. (IMHO = same with HONEST).
  22. You're suppressing errors with the @ symbol. Remove that, and ensure error reporting is on and set to E_ALL.
×
×
  • 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.