AAQ: More space for troubleshooting.

I ran into this again last week. The field isn't big enough for the unmodified data, since there are a lot of printing preferences. I fixed this with a one-two-punch:

1. I raised the limit on the text field by about 20 times. The database was already unlimited, this was just a problem with the form.
2. I stripped out the print fields on the client side before form submission. We are already hiding them when we display this information, and no one has complained about it (to me), so it should be fine.

Especially now that we are hiding this field, this error will be confusing for users and likely very frustrating.

r?