Search results

We're at 2-2 for Hockey Olympic Gold. How does X10 line up in supporting U.S.A. vs Canada? And there we have it. Canada for gold.

It means your script isn't handling errors. You've got a line like $db->setQuery(...), but $db isn't an object because the line that was supposed to create an object failed. Always handle errors, whether it means catching exceptions or checking return values.

You mean you can't get your cron jobs to work, which is different from cron not working. "&" is a special character in shells. Try enclosing the URLs in single quotes.

What you want for an image picker view isn't entirely clear, but here's some stuff to get you started: There are plenty of color picker widgets for web pages Simply store the hex value in the table for the user's pet's stats To color the pet, you can use the GD extension, specifically the...

If you're still getting the error when the server is back up, make sure you're using "localhost" as the server name when connecting.

What's the URL for your test page? It's next to impossible to answer questions about coding without seeing the code. Including links to a live page is part of being precise and informative.

Just be careful of injection attacks.

Some premium hosting options allow for more. As for accessing multiple databases from the same script, you could create a connection for each database, but this is unnecessary. The database you specify when connecting is merely the default database. When a query specifies a table but not the...

@tillabong: it's not entirely clear from your post where the problem lies. When applicable, you should always post a code sample (a minimal test case) to clarify. Also, there's no need to make up URLs. You're asking about your site, so why not simply post the URL for a live page? One thing...

Hue's HelloWorld works on Lotus, which means Mono's probably broken on absolut. Check for interesting entries in your error logs in cPanel. Most likely there's nothing you can do, and you'll need to open a support ticket.

The problem is there's a <form> element between #textbox and #send. Since the form doesn't have an explicit height, it's given a height of "auto", so #send's percent height also becomes "auto". Set an explicit height on the <form> to fix: #textbox * { height: 100%; } If by "total width"...

There's nothing in the HTML sample (http://pastebin.com/d787a4991). If by "inherit" you mean how the CSS spec defines inheritance (the value of a property on a child is set to that of a parent), then yes, but only if you explicitly set the height property of the child to 'inherit'. If you mean...

Alternatively, switch to PDO and use prepared statements. Prepared statement parameters aren't vulnerable to SQL injection; no need to escape or unescape quotes. Of course, you'll still need to handle HTML injection with (e.g.) htmlspecialchars or some sort of whitelist filter.

Read the forum rules. This forum isn't for asking for help, even asking for a tutorial. Read the references. A mod_rewrite tutorial will tell you what you want to know.

Re: here it is Looks nicely succinct. The advice is better than a complete description, as the cases that aren't covered aren't useful and would only cause problems. For more on what garikr mentions, check out HowToCreate's "HTML tutorial - The Basics".

To be blunt, the code on that page is a mess. Running it through a validator turns up many of the problems. Another major problem is the amount of presentational markup (such as the <font> tags and "<p>&nbsp;</p>"), which should be removed and CSS used instead. Presentation should be separated...

You only need separate PDO exception handlers if you want to handle exceptions thrown by the different inserts differently. Stick with the second sample you posted, possibly adding an if around the $ins1->execute() Edit: from taking a closer look at the source, the only times the MySQL driver...

The code will most likely work, assuming you're using the PDO MySQL driver and you've set PDO::ERRMODE_EXCEPTION on $dbh. However, PDOStatement::execute officially returns False "on failure", while exceptions are thrown "on error". The difference isn't well defined, but there might be instances...

If the other columns aren't allowed to be Null and don't have a default, then an insert on the second table isn't possible. If any default isn't appropriate, the insert isn't sound. In a properly normalized schema, the only fields that appear in both tables will be the primary key in the first...

A search of the forums turns up: "MySQLdb for python on Stoli". If you're not on Stoli, the situation is probably the same, due to the recent server upgrades.