Add option for 3.3 "scale images" feature in media uploader to be default state
Pretty simple, an option under Media settings that changes the default state of the media uploader to always scale the original to the largest size setting. That way you don't have to click that button every time but more importantly WP installs on sites where clients don't want to manage every little thing can be that much more automated.
This won't happen for 3.3 (which does have a revamped media uploader). HOWEVER. Once you check the box for it in 3.3, WordPress does remember that going forward.
Right, I have the 3.3 beta and the remembered state is good but still allows for potential trouble if a client unchecks it out of curiosity or whatever. I'm aware we're past 3.3 feature additions but wasn't sure how else to refer to that radio button other than as the 3.3 scale images feature ;). Thanks for the response.
I don't think it'll be defaulted honestly, that's too iffy.
I'm fairly sure you can write a function to force it to always stay checked though.
I agree that defaulting to it checked for any new install is the wrong move, I'm just looking for an option in the Media settings that would set checked state as default for that site. That would allow you to still uncheck it when necessary but wouldn't trip the save state, so next time it would be back to checked. Hopefully you follow what I'm getting at.
I'm going to force it on sites where it's needed once 3.3 goes live but I think making the default state for a site an option would add flexibility.
Right, that's what I meant :)
Like you can add
update_option('image_default_link_type','file'); to your functions.php to force set all images to default to FILE lines. I suspect there's a similar option for this.
Yep it can be done in functions.php but I thought it was a good idea for core, something that would benefit others--hence posting here in ideas ;). Cheers
For those wanting to know how to check it by default, this seems to work:
set_user_setting ('upload_resize', true);
We withdrew the feature from 3.3 due to confusion about what/when resizing would take place, and core team decided it would be better as a plugin.
RSS feed for this topic
This topic has been closed to new replies.