The solution, though a bit of a hack, is to write styles for the div container that use the !important rule, which will override any inline styles. Here’s what the fix should look like:


#my_auto_complete {
position: relative !important;
top: -10px !important;
left: 0px !important;
}


Effectively, you create your a background image the maximum width that you expect the box to be, as you would do with sliding doors. However, instead of cutting off the left side (or right side, as you prefer), you keep the image intact. Instead, you simply align the image to the left on the outside and the right on the inside, leaving enough padding for the image edges to show through.

Here’s an example of the technique in action.
Update: Example now works in FF3, FF3.5, IE7, IE8 and Safari 3 and 4!

The only caveat here is that this won’t work for images with transparency, and only saves you one download (ostensibly). This technique could be expanded, however, to have the hover states of the button in the image as well (as in the sprites technique), or for all four pieces of the image, used in rounded corners and custom border styles. I wouldn’t recommend either of those for particularly large boxes, though, as you’d need a really large image for those, which doesn’t optimize well.


symfony doctrine:migrate --env=staging frontend 119


where “staging” is whatever the environment is you want to use (to match the name in the database.yml file).


$myobj = new Doctrine::getTable('MyObj')->find($request->getParameter('my_id'));
$myobj->property = 'New Value';
$myobj->save();


This is really straightforward, but if you don’t include the find() inline with the getTable() call, you’ll get an obscure “Unknown method saveTableProxy” error, which there seems to be no documentation for anywhere on the internet. It only took a couple of hours of trial and error to get this figured out.

In general, I’d still recommend Doctrine as an ORM, but the lack of consistent and clear documentation, with dreadfully obscure object methods, make for a very steep learning curve.

When using trigger_error(), you can use the expectError() as follows:

$this->expectError( $errorMessageToExpect, 'My message about this test case' );
my_code_that_causes_an_error();


Note that there is an internal queue of errors in SimpleTest, so it will expect precisely one error for each call to expectError().

If, however, you’re using throw you use expectException instead:

$this->expectException( $exceptionclass, 'My message about this test case' );
my_code_that_throws_an_exception_of_type_exceptionclass();


You can specify the class of exception to expect in the first parameter – the usual type would be Exception, of course. If you set the first parameter to false, it defaults to this type.

1. Each item must have a unique id.
2. The item id must contain an underscore (_)
3. The item id cannot begin with an underscore or a hyphen

Using myname_## should work fine, as long as ## is a unique integer in each case. Technically, it must match the following regular expression:

/^[^_\-](?:[A-Za-z0-9\-\_]*)[_](.*)$/