ginerjm

Why not just use a pdf printer driver in your browser? Or better yet - design a better output more suited to a print-job rather than a web page and use a pdf extension such as FPDF in your php script to output it.

If you are storing a timestamp in the "kick" field, it must be hard to store a text value in there. I'm guessing that you don't have that field defined as a time-related field which makes it hard to use that comparison you have in your where clause. Try defining your kick field as a timestamp and then add another field as a flag to be set when you want "permanent" status set on this record.

I really think that if you did RTFM you would have a better mental outlook on how a query works and how various functions enable you to get what you want out of it. If you think that you can actually become a 'good' programmer without ever availing yourself of the specific knowledge available in the documentation for the tools that you may use in that learning process, you are sorely disillusioned.

You might get a quicker solution if you posted the latest change to your code showing how you used var_dump.

Since nobody else has responded to your vague question, I'll ask. What do you mean by "shares"?

As previously mentioned - you should really send an email asking the user if he wants to reset his password to avoid someone hacking and causing you to make a change that the user didn't request. Add a hidden field to the reset form that you provide the user if he responds 'Yes' to be able to detect a valid reset request from the user as opposed to the perhaps invalid request from a hacker.

It doesn't make sense that you can't break out your thoughts into distinctive sentences when you write non-code.... Come on - you guys invented English!

And where oh where did your previous writing style go to already?? So messy..... tsk tsk tsk

So where is your query defined? $sql? You could also read up on html tags that are deprecated. Such as <font>. And how to use css to make styling your html much simpler. A major improvement in script development would be to learn how to keep you html block of code completely separate from the php block of code. You begin your script with the start of an html doc. What's the rush? You should begin with the php code and the logic to determine what exactly you are supposed to do at this instant. Then do it. If it involves building some formatted (ie, html) output, then do that as part of your query results loop and store it in a php var that you then embed in your html block where it needs to go. Splitting things up like that makes it Sooooo much easier to follow - for you and for us - and easier to debug later on and easier to enhance and add features such as more html or more php logic.

As resident nitpicker here, you could also learn to write your sentences with caps and periods so all your thoughts don't just flow at us without making sense.

IMHO - When a user enters incorrect credentials you should simply put back the login screen with/without the incorrect userid and NO password and a message saying that the entries were invalid. This way they get to try again without having to click on boxes. Don't send back the password, just the userid entry to avoid multiple transmissions of a possibly valid pswd.

YOU built this script? It is so outdated I find that hard to believe.

A good model for script design is to set your php code all up front and your html all at the end. They don't need to mix unless you are using php vars to convey html with dynamic embedded data into the final webpage output. Keeps the logic and heavy work away from the presentation and display work. No need to output intermittent dribs and drabs of html while you are trying to write the "serious" code.

You should add error checking to this script and you should make a decision on whether to use the mysqli functions or the MySQL functions. YOu can't mix them together. Plus - if you took a look at the manual you would see the big highlighted statements telling you NOT to use MySQL stuff. Despite all this, you also use a query statement as an argument to your select db call. That's not going to work. Personally I prefer PDO

To quote your initial post: That statement simply says "I'm hosting an application that people can use to send faked emails out on." Is that what you want to do? I doubt that your hosting company would allow you to continue doing this if you become a pariah among mailservers (which means they do if you are on a shared host.). I cannot fathom an application that I have ever used for the express purpose of sending someone an email. Sure - sometimes an appl asks if I want to send a link or something similar to another person and those emails do go out with that apps/servers credentials on them, usually with some reference to my id in the message saying who it was sent on behalf of. What you continue to march on to is in my opinion poor internet behavior. Everything that Gizmola told you in her succinct and spot-on post should be listened to and used to guide you to make a change in your plan. Emails should always indicate where they came from - NOT some false address that may or may not be real. You say that the supposed client will be placing their own address in the From field, but how do you know this to be true? Your host probably would frown on an appl design that plans on mis-using their mail services in this way and could very well terminate your account. Please find another way to inform your recipients from whom these emails have been sent. (I already suggested using the Subject line.) Spam is not the way to go and one less spammer in the world is a good thing.

No - I meant if you want to send an email that is truly from you, don't use a web app to do it - use your own email client. Spoofing a part of an email to mis-represent it is one of the biggest problems on the net in this day. That and viruses. And hacking of websites to make them do something not intended by the designer. All of these are fraudulent activities and for you to even consider doing what you propose makes you (sorry) guilty of the same behavior. If you need to make an email stand out and show who it's from when generating it from your appl., then put that into the Subject.

Then send the email from YOUR account where the From address will be properly set to your address. Don't send it from the application which is already designed for a different purpose. Frankly - apps that allow such behavior are quite possibly the source of many spam messages today.

Using someone else's email address as the From address for your email IS a definite red flag to email servers as it should be. Just because you think it is ok to forge a from address to send one simple email doesn't mean that a mail server will think like that. The job of a mail server (IMHO) is to prevent such abuses!!! People do this ALL THE TIME and that is why all of us legitimate email users have to deal with emails coming back from people that we didn't email to or why our IP addresses get blocked because of spam problems. There is absolutely no good reason to use someone else's email address as the from address that is FROM YOU

If you post some of your code here you might get more interest. Some of us refuse to click on links to see code posted elsewhere.

You do realize that the value is expressed in seconds? 7200 = 2 hours. If you insist that you Really need to extend a session for that long, bump up that 7200. Is this some kind of secured or sensitive application? Do you really want a session on an unattended pc to just sit there for someone else to walk up and access?

I have to wonder if foreach ($res as $res) will work. You are supplanting the $res variable with a new value so you lose the rest of the array! Try foreach ($res as $item) instead and then manipulate $item

Gee - all this time I have thought very highly of Jacques' informative posts, even at the cost of sometimes being the target of his rants. His English is quite succinct. When it comes to whose native language is English, I often wonder about Mac_gyver's use of it since he doesn't seem to have ever learned about proper structure of a paragraph which recommends sentences that begin with an uppercase letter to help make the reading easier. So much of his posts seems to be run-on text because of the fact that my older eyes don't see the little tiny periods that my font (or this site) uses. Caps would make it much easier to read, as I said, and would represent proper composition of an English/American post. As for the post in question - I think Jacques interpreted post #6 exactly as it was written and I agree whole-heartedly with what he was saying.

Where are you setting the email for html content??? You are sending a header to the client, but that's not going to affect the email is it? You're not sending the email to the client - you are sending it to an email address. Google something like "send html mail" for examples.

You have formatted the email properly as an html one, correct? Have you altered your to address to send the email to yourself to see what you actually get?

Assuming that you posted your intput followed by the code followed by some output you generated - this doesn't make sense at all. The output is not in the same order as the input. The output is different than the input. You are not showing us something. How about doing it again and breaking it up so it makes sense to us ordinary people? And show all the code involved!