OK, so I've got Ubercart 2 installed and working on a freshly updated Drupal 6 site featuring photos that I'm hoping to sell prints of.
Each photo is a node and I've successfully converted the "photo" type nodes into products by creating a class of the same name. I've also created the attribute "Print Size," with options like 8x10, 11x14, etc., and I've added that attribute to the class "photo."
As I've discovered, this does not automatically attach the attribute and its options to the existing nodes, which is disconcerting since I've already got dozens of nodes that need to have these options. It's also disconcerting to think that if I ever change the prices of those options in the future, I can't simply change them in one place and have them automatically reflected in all products of the same class, which, in my opinion, is how a system like this should logically work. (No offense to the creators intended; it's a great system and I know what a monumental effort it is to create something like this.)
I've done some searching and this is a concern that appears not uncommon. However, I haven't come across a workaround short of manually manipulating the database. Neither have I been able to dig up a project issue that clearly addresses this concern so I can monitor any progress.
Can anyone point me to something I've missed in either case?



The way the system is designed seems to be that when you define the attribute and its options these are on defaults that will be available when you first attach them to a product, so you're correct in saying that updating attribute option defaults will have no effect on the attribute options you've already attached to products.
The only way I know to do a mass product update like what you're talking about is via sql. It is a pain, but if you're familiar with databases at all it isn't too hard.
Edit: I take that back, I've just looked at the database and see that product attributes and options are stored in different tables (?!), thus making it quite difficult to update via the database. I have no idea why product attributes and options would need to be in seperate tables, options cannot exist without an attribute and attributes have no purpose without options after all.
If they were in the same table it would have been incredibly straight forward. Sorry I can't be of more help.