I can understand why it is undesirable to modify any piece of the core; however this particular change does not effect any of the regular function (unless the agent is determined to be an iPhone. Here is the part it effects:
`
$UA = isset($_SERVER['HTTP_USER_AGENT']) ? $_SERVER['HTTP_USER_AGENT'] : "";
$iphone = stristr($UA, 'iPhone') ? true : false;
if($iphone){
setOption("image_quality", 70,false);
setOption("thumb_quality", 50,false);
}
$thumb_quality = getOption('thumb_quality');
$quality = getOption('image_quality');
$thumb_crop = getOption('thumb_crop');
$thumb_size = getOption('thumb_size');
$thumb_crop_width = getOption('thumb_crop_width');
$thumb_crop_height = getOption('thumb_crop_height');
$image_default_size = getOption('image_size');
`
So essentially, it is just like having two sliders in the admin panel for image_quality and two for thumb_quality, one for the default theme and one for the custom theme.
The reason this seems necessary is that the non-persistent setting for this particular property does not work, it only effects the current function, not those that get called up to do the actual custom image creations. Of course, persistent do work but they change the options for all themes.
If there is another way, please let me know.
----
As far as the thumb_quality property not being used for custom thumb image functions, is there any way around this? This isn't a big deal, if not.