Page 3 of 3 First 123
  • Jump to page:
    #31
  1. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Jan 2017
    Posts
    830
    Rep Power
    0
    Originally Posted by gw1500se
    I'm sure someone on the Hire a Programmer forum can.
    You mean someone like you ?
    You mean: I am sure I can for $$.

    Not gonna work buddy.
  2. #32
  3. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Jan 2017
    Posts
    830
    Rep Power
    0
    Originally Posted by SimonJM
    As I have said, I don't do php, and have no way of running any php code. I did wonder about using $title as both a string variable and an array but as you have used this code (or something very similar to it) I 'overlooked' it; and don't even know if that IS the issue you get, ad you didn't bother saying what error you get!
    You are also going to get the same 'undefined index' error with 'description' if the tag does not contain a description element. Can you (should you?) preload the target array with dummy (blank/null) values for any element that you need to be there?
    I did add '@' like you suggested on my version:
    @$description=$tags['description'];

    On post above you saw the original version from the tutorial
  4. #33
  5. Banned (not really)
    Devshed Supreme Being (6500+ posts)

    Join Date
    Dec 1999
    Location
    Caro, Michigan
    Posts
    14,944
    Rep Power
    4554
    Didn't we tell you elsewhere to stop using @?? You are the last person that should be suppressing errors.
    -- Cigars, whiskey and wild, wild women. --
  6. #34
  7. Contributing User
    Devshed Frequenter (2500 - 2999 posts)

    Join Date
    Mar 2006
    Posts
    2,673
    Rep Power
    1841
    Originally Posted by UniqueIdeaMan
    I did add '@' like you suggested on my version:
    @$description=$tags['description'];

    On post above you saw the original version from the tutorial
    I think you'll find that me quoting a web page that explains what the @ symbol does is NOT me suggesting you use it. If that's the way you read manual pages, if and when you do, all I can say is I am not surprised!
    The moon on the one hand, the dawn on the other:
    The moon is my sister, the dawn is my brother.
    The moon on my left and the dawn on my right.
    My brother, good morning: my sister, good night.
    -- Hilaire Belloc
  8. #35
  9. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Jan 2017
    Posts
    830
    Rep Power
    0
    Originally Posted by SimonJM
    I think you'll find that me quoting a web page that explains what the @ symbol does is NOT me suggesting you use it. If that's the way you read manual pages, if and when you do, all I can say is I am not surprised!
    I took your suggestion as an advice to me.
    Ok, since you agreeing with Sepo then best listen to the fella! He talks from 'expo' (experience). Just invented a short word. Wow!
  10. #36
  11. Contributing User
    Devshed Frequenter (2500 - 2999 posts)

    Join Date
    Mar 2006
    Posts
    2,673
    Rep Power
    1841
    Originally Posted by UniqueIdeaMan
    I took your suggestion as an advice to me.
    Ok, since you agreeing with Sepo then best listen to the fella! He talks from 'expo' (experience). Just invented a short word. Wow!
    Language may be a barrier, but it's still not a suggestion! What IS a suggestion, however, is to, never mask or hide errors. Whilst developing by all means have the full message code and text sent to screen, but for a production system you should log them and show the user a 'friendly' message such as "We had an error entering your information. Sorry about this, we have logged it and it will be looked at. Please try later." instead of showing,say,. the raw SQL, etc.
    The moon on the one hand, the dawn on the other:
    The moon is my sister, the dawn is my brother.
    The moon on my left and the dawn on my right.
    My brother, good morning: my sister, good night.
    -- Hilaire Belloc
  12. #37
  13. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Jan 2017
    Posts
    830
    Rep Power
    0
    Originally Posted by SimonJM
    Language may be a barrier, but it's still not a suggestion! What IS a suggestion, however, is to, never mask or hide errors. Whilst developing by all means have the full message code and text sent to screen, but for a production system you should log them and show the user a 'friendly' message such as "We had an error entering your information. Sorry about this, we have logged it and it will be looked at. Please try later." instead of showing,say,. the raw SQL, etc.
    I know what you mean. On on of my old files I got a line like this which i grabbed from the web:
    PHP Code:
    if (!$mysqli
        {
            
    //Error Message to show user in technical/development mode to see errors.
            
    die("Database Error : " mysqli_error($mysqli));
        
            
    //Error Message to show User in Layman's mode to see errors.
            
    die("Database error.");
            exit();
        } 
  14. #38
  15. No Profile Picture
    Contributing User
    Devshed Specialist (4000 - 4499 posts)

    Join Date
    Jul 2003
    Posts
    4,451
    Rep Power
    652
    As usual, you just grabbed and did not read what die does. If you had you would recognize how dumb that code is. Another lesson on why you don't copy and paste code from the internet without taking the time to understand it.
    There are 10 kinds of people in the world. Those that understand binary and those that don't.
Page 3 of 3 First 123
  • Jump to page:

IMN logo majestic logo threadwatch logo seochat tools logo