floridaflatlander

and ... did you figure it out ?

Okay, "just for me" would have to be something like this ???? while($result = mysql_fetch_array( $data ) or die("Error: ".mysql_error($data)))

Can you comment out the if ($anymatches.... and see if "or die("Error: ".mysqli_error($dbc)); gives you any clues" ?

Should it be $anymatches=mysql_num_rows($results); ?

They are old school for general lay out of web pages. But we're talking about forms for a forum right?

I use tables but someone on here was using list and it looked good, maybe those with experience can chime in. It's been several months since I've seen the style but I think the basic setup was something like this <ul> <li style="wide"></li> <li style="content"></li> <li style="content"></li> <li style="content"></li> <li style="content"></li> </ul> Using display block, floats and widths(I think)

Are you talking about this $urltext = Product_Name_'with_single_quotes'_"_B ?

Are you pulling this info from a db http://www.phpfreaks.com/forums/index.php?topic=330776.msg1556643#msg1556643

It wont over write it unless you use UPDATE .... WHERE id=id or something like that If you use insert it will add to the records not over write

You may want to explain that to your potential customers in your about us section. They may be spending or getting ready to spend $50-500k with you. But with that said, you site looks very good to me.

The others do too I believe, I know bing does. How long have those pages been up, google is the quickist I think. When I did a lot of 301 redirects google had changed to the new pages way faster than the other search engines

You can use a SELECT query or mysqli_insert_id() after your mysqli_query if you need it right after an INSERT I use: $last_id = mysqli_insert_id($dbc); // Get the items ID

Okay, someone who I think is a good guy and gets gets a copy through me or a third party of my table, then gets my hashed passwords. Therefore salt them.

if your database security is so poor that you end up revealing your user's plaintext passwords I hoped they're hashed. True, but they first must get it

Different things do different things strip_tags() removes things like <a>, </a>, <javascript> etc anything within tags <> htmlentities() changes things into their html entity like & changes into & int() makes sure everthing is a number mysqli_real_escape_string() is the cats meow and turns every thing into a string

LOL they're already there, AKA inside.

So salt helps protect against a list of hashed values from a (or my) users table? And if thats true that means the bad guy must first get this list of hashed values in the users table?

Step 1. Jo bob signs in using his name (Jo bob) and password. Step 2. Select query1 finds the name Jo bob in the user table and retrieves the salt Step 3. Select query2 uses name = Jo bob and adds salt & password to get $stored_password = sha1($salt.$password) to sees if user exist. Maybe I don't know what brutt force is but like I said if they know a name, in theory they can just keep trying passwords until one worked. Having salt wouldn't matter.

I'm still trying to figure out why I should use salt. If the bad guy knows a name and tries something like brute force shoving passwords into the log-in form until one worked how would salt help stop that? If a bad guy, God forbid, gets hold of the user names and passwords like they did phpbb(?) forums several years ago how would salt stop that? I know I may be beating this issue to death but if I have salt in the users table assigned to a user and his password now equals $stored_password = sha1($salt.$password) does this really doesn't matter? Because if the bad guy knows the user name and uses brute force or has a list of passwords from the users table that he has gotten some way. All he has to do is type in the user name and password and salt will be added automatically.

Java script or after the select a second page with the second page dependant on the option selected. Use sessions to keep track of the user between pages.

Or could you use <meta HTTP-EQUIV="REFRESH" content="0; url=http://www.website.com"> 0 = seconds

? ... I hope that was a joke.

I don't know if you'll be penalized or not, I think the penalty comes from duplicate information on the same site. People publish and republish news all the time on different web sites. How does Google know or not know if they are related? You can also put a no-follow on your new site to prevent confusion, when the time comes use a 301 redirect and remove the no follow. Make the file paths a logical path that will help you easily implement your 301's. It will take 2-4 weeks for almost all the search engines to drop your old website name and start listing the new one. I have had one photograph that was at nine weeks before it was redirected(on bing). Until then, search engines will list old URLs and when someone clicks them they will be automatically redirected to the new site.

Sorry, I just got up, I didn't read your last sentence

Are you doing this for security reasons? Could you as an example have a page called member.php and use sessions and add as needed if ($_SESSION['mem_id']) {SELECT display info}