jeffinsf

Functional, but ugly, with unknown results when I switch to the next tag

[jeff@port16 wp-content/themes/twentyten]$ svn sw -r 15464 https://core.svn.www.ads-software.com/trunk/wp-content/themes/twentyten
U    style.css
U    functions.php
U    loop.php
U    page.php
U    languages/twentyten.pot
U    editor-style.css
U    header.php
U    attachment.php
Updated to revision 15464.

From the svn documentation:

In other words, if a user knows that the branch work needs to happen on only a specific subdirectory, she uses svn switch to move only that subdirectory to the branch. (Or sometimes users will switch just a single working file to the branch!) That way, the user can continue to receive normal “trunk” updates to most of her working copy, but the switched portions will remain immune (unless someone commits a change to her branch). This feature adds a whole new dimension to the concept of a “mixed working copy”—not only can working copies contain a mixture of working revisions, but they can also contain a mixture of repository locations as well.

Any “clean” way to en masse resample past images from within WP?

I’d rather have the then-current settings picked up for image size, quality, filenames, etc., rather than doing it with an external script and hard-coding the values in.

Follow-Up Summary

Seems that, even with GD installed, images uploaded prior to the installation don’t have alternate sizes “magically” created.

It appears that there are two things happening here. The first is that my quick check of the code suggests that if GD wasn’t properly installed and configured when the image was uploaded that you won’t see the image-size options enabled. This comes from looking at wp-admin/includes/media.php

function image_size_input_fields($post, $checked='') {

                // get a list of the actual pixel dimensions of each possible intermediate version of this image
                $size_names = array('thumbnail' => __('Thumbnail'), 'medium' => __('Medium'), 'large' => __('Large'), 'full' => __('Full size'));
                foreach ( $size_names as $size => $name) {
                        $downsize = image_downsize($post->ID, $size);

                        // is this size selectable?
                        $enabled = ( $downsize[3] || 'full' == $size );'

appears to be the function that determines if the buttons are enabled.

A definition of image_downsize() appears in wp-includes/media.php

/**
 * Scale an image to fit a particular size (such as 'thumb' or 'medium').
 *
 * Array with image url, width, height, and whether is intermediate size, in
 * that order is returned on success is returned. $is_intermediate is true if
 * $url is a resized image, false if it is the original.
 *
 * The URL might be the original image, or it might be a resized version. This
 * function won't create a new resized copy, it will just return an already
 * resized one if it exists.
 *
 * A plugin may use the 'image_downsize' filter to hook into and offer image
 * resizing services for images. The hook must return an array with the same
 * elements that are returned in the function. The first element being the URL
 * to the new image that was resized.
 *
 * @since 2.5.0
 * @uses apply_filters() Calls 'image_downsize' on $id and $size to provide
 *              resize services.
 *
 * @param int $id Attachment ID for image.
 * @param string $size Optional, default is 'medium'. Size of image, can be 'thumbnail'.
 * @return bool|array False on failure, array on success.
 */
function image_downsize($id, $size = 'medium') {

which suggest to me that thumbnail (or other sizes) aren’t likely to “magically” appear when GD is installed and things are restarted.

The second thing is that the wordpress.com behavior of https://blogname.files.wordpress.com/year/month/filename.jpg?w=128&h=96 does not seem to be a “stock” feature of either wordpress or wordpress-mu.

Problem definitely can exist with GD installed, php -m reporting it present, and server returning a generated image from a script like that just above.

c.f., https://www.ads-software.com/support/topic/226550?replies=7#post-992291

Have you checked the permission on the wp-content/ directory if you haven’t uploaded yet, or the wp-content/uploads directory, if you have? I personally create the wp-content/uploads/ directory manually, so that the WP install stays mainly unwritable by the webserver.

For FreeBSD, I use

# chown www:www uploads
# chmod 755 uploads

Your user and group may be different on another platform.

(I’ve seldom had the Flash uploader work for me either.)

php -m
[PHP Modules]
date
gd
libxml
mysql
pcre
Reflection
standard
xml

[Zend Modules]

I’ve reinstalled everything, and am running 2.7.1

The little test script (and a few others that I have found) run fine, returning a constructed image.

I still don’t get image resizing on any of the blogs here, including one that has been imported from wordpress.com with its media, that does properly render reduced-size thumbnails in its galleries from that site.

I also do not have an option to select among the different size images when placing from the gallery (the radio buttons are there, but none are active other than to select original size).

The problem exists for both JPEG and PNG images, including those of moderate size (well under 1 MB).

Seems to be affecting others, including

Thumbnail Image option = Greyed out…2.7 wordpress

Any suggestions as to how to debug this?

TIA,
Jeff

7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan  1 14:37:25 UTC 2009     [email protected]:/usr/obj/usr/src/sys/GENERIC  i386

GeoIP-1.4.5_1
apache-2.2.11_3
autoconf-2.62
autoconf-wrapper-20071109
awstats-6.9,1
expat-2.0.1
freetype2-2.3.7
gd-2.0.35,1
gettext-0.17_1
gmake-3.81_3
help2man-1.36.4_2
jpeg-6b_7
libiconv-1.11_1
libtool-1.5.26
libxml2-2.7.3
m4-1.4.11,1
mysql-client-5.1.30
mysql-server-5.1.30
p5-Geo-IP-1.35
p5-Net-XWhois-0.90_4
p5-gettext-1.05_2
pcre-7.8
perl-5.8.9_1
php5-5.2.8
php5-gd-5.2.8_1
php5-mysql-5.2.8
php5-xml-5.2.8
pkg-config-0.23_1
png-1.2.34
portaudit-0.5.12
portmaster-2.7
postfix-2.5.6,1
t1lib-5.1.2_1,1