premiso

It all depends on the OS type Sure home basic os goes for $100, but honestly who uses that? For the Pro content it gets up to around $200. http://go.microsoft.com/fwlink/?LinkId=167235 That is just for the upgrade from Vista to Windows 7 Pro The non upgrade is $300 and the Ultimate is a bit more expensive. (sorry if the link above violates ToS...)

Ok, take a step back and breathe. The reason I said 6 hours is because I basically mimiced the cookie your current script was setting. So doing this test everything is setup like the cookies are being set in your script. Going ahead 6 hours, which is the time you stated that you are logged out of your site automatically, will test if the issue is in your script, on your server or on your computer. Basically we are just trying to narrow down what the culprit maybe. Does that make sense? So adding 6 hours to your computer's time the cookie should still be valid, cause it is well under the 60 days like the cookie is set for. If it does get deleted then we can rule out your script and chances are it is something in your computer or on the server that is causing the issues. This is the act of testing and debugging.

Yea, when I refer to "box" it generally means your computer. A lot of IT people call them boxes because...well most of them are as a big as a box and store a ton of junk inside (at least that is how I define the term).

time()+60*60*24*60 That sets the timeout to be 60 days from now. So techincally you should not have to "re-login" within 60 days. It could be something with your code, hard to tell without seeing it... Something to the effect of a script that goes and wipes out the session after a certain time etc. Could also be in your configuration files for session timeout, after x amount of time the session will expire. A quick test you can do to see if it is the script or server is create a simple script <?php if (!isset($_COOKIE['mycookietest'])) { setcookie("mycookietest", "test", time()+60*60*24*60, "/"); }else { echo "mycookietest has been set to: " . $_COOKIE['mycookietest']; } ?> Run that then adjust your time on your box to be 6 hours and then refresh the page, see if the cookie is still active (no clue if this will work but sounds like a reasonable test). If it does stay the chances are it is your script that is tossing the cookie somewhere... (given that it is a valid test, I cannot see why it would not be).

Does it do it on other browsers/computers? It could just be a setting on your computer wiping the cookie data...

lol, I am going to have to save that image and show it to the wife, maybe she will be up for the new style?

I think you need an imagecreate function to create the initial image resource before continuing...I am no expert at GD, just gathered that from the manual.

What is the error you are getting? Providing that will help us out a bit

Do you have a database or how do you plan on storing the data? It is entirely possible, you just have to have a way to save the data so you can retrieve it when the members profile is pulled up.

Not sure if it will work, but worth a shot: $doc = new DOMDocument(); $doc->formatOutput = true; $l1 = $doc->createElement( "main" ); $doc->appendChild( $l1 ); $l2 = $doc->createElement( "configuration" ); $doc->appendChild( $l2 ); $l2->appendChild($doc->createTextNode("\nvariable1 = \"2\"\n" )); $l2->appendChild($doc->createTextNode("\nvariable2 = \"9\"\n" )); $l1->appendChild( $l2 ); $doc->saveXML(); $doc->save("write.xml") ; \n only is interepted inside of double quotes, single quotes takes it literally, give that a shot.

Sorry, that is a bad example. To "encrypt" which you really are going to hash it, you use md5 with a unique salt. The gist of it: You take the password in at registration, you md5 it with a unique salt, basically just a random string unique to your script so it makes the hash a bit more secure. You have to re-use this salt on authentication. For authentication, you take in the username and password on the checking page, you hash the password up with md5 and the salt, then you check it against the database. If they both check out you set a session variable saying the user is authenticated and away they go. Hopefully that gives you enough information to get started on it and post here with some code when you get stuck. And on a side note, I do not know why a lot of tutorials leave out hashing the password....that is just stupid. Maybe I will make a tutorial for it

I recall that there is a way, but if you are doing password strength you want to let the user know what is missing, so why not just seperate them out into their own if statements, that way you know what is missing and can inform the user of it so they can properly fix it... I have some code, but it is on a different PC at home, when I get home, if I remember, I will post my code for a password strength checker (it was made for AJAX).

http://www.phpeasystep.com/phptu/6.html Plenty of tutorials online to get you started. Googled "php login tutorial" to find the above tutorial, many others out there as well.

Well look up the function in the manual and do some debugging to figure out why the delimiter is empty. stristr

Well welcome back Wasn't here before you left, but yea! Good to have you back

You do not have that commented out. Make it like this: //that contains the file attachment. Here's the code: And hopefully that fixes your syntax error.

Why do you need to memorize phone numbers? That is what address books are for and contact lists in your cell phone I have not memorized a phone number for a long time...if my cell phone were to crash heaven forbid! (That is why you sync it to your computer as well). As for passwords, I try not to memorize anyone's password but my own and some basic default ones.

I have this on my site, it is inside of <body> and </body> <script type="text/javascript"> var workIsDone = false; window.onbeforeunload = confirmBrowseAway; function confirmBrowseAway() { if (!workIsDone) { return "CAREFUL! Discard this entry?\n" + "This blog entry will not be saved."; } } function save() { workIsDone = true; } function disableForm(theform) { if (document.all || document.getElementById) { for (i = 0; i < theform.length; i++) { var tempobj = theform.elements[i]; if (tempobj.type.toLowerCase() == "submit" || tempobj.type.toLowerCase() == "reset") tempobj.disabled = true; } return true; } } </script> Then on the html form I incorperate the save() function so if they user wanted to save it it saves and then the workisdone is set to true and it allows you to save and move on. <form name="form" method="POST" onSubmit="save(); return disableForm(this);" action="your action here"> The disable form helps prevent multiple sibmits etc, and can be omitted.

That is not a question...if you want someone to code this for you, post in the Freelance section. If not post your attempts at coding it to be helped along the way.

I think Semi hit the nail on the head. For computer users who do not know any better, a Mac is great as they do "Just Work". However, for users who like to customize and have full control, Unix all the way, and for the ones who want something that is more robust and provides us with interesting work arounds, Windows is there I would switch to a Mac, but I freaking hate having a single mouse click and I hate the trendy ness of it. I mean come on $2,500 for a computer I can get for $800 with Windows or $500 with Linux....seriously. Just buy a Windows PC and put the Mac OS X on it and be happy For testing, however, I can totally see owning a mac as hardware can have issues on programs.

I would stick with the open source database. It will be more reliable and updated continually. The other links you either had to pay for or are not reliable at all.

I think it was a prototype made in C++ actually...which is how that function got left in there. It was suppose to be removed once they went into production, but did not.

Well, that object is somewhat tempermental. I mean it did come with the function denySexPriveleges(int Length); as part of it's class functions =\

I tell you, it is not the sleep() function that needs debugged. It is the changePoopyDiaper() function that needs fixed =\ Seriously!

Wow lol....that is too funny. I guess I need to refresh myself on the stickies too :X