ZachMatthews

Yeah it will resize more or less automatically if you simply adjust the size of the original. I’ve got 1140 X 225 running on my site here:

https://www.itinerantangler.com

So, the bbPress bulletin board plug in currently available for WordPress does not have its own PM unit. The suggestion by the bbPress developers is to use BuddyPress, the social networking plug in, but that is like killing a fly with a sledgehammer. Buddypress is just as resource intensive as bbPress itself, not to mention awkward, poorly designed and full of conflicts when it comes to theme integration.

I’ve gotten around that by implementing your excellent plug in and partly integrating it with bbPress.

https://www.itinerantangler.com/blog/board/forums/users/zachmatthews/

That’s the page where I did a little minor integration with bbPress to put a link over to your PM plug in.

It would be AWESOME if you could tweak this to run within the bbPress framework. I don’t think it would be all that hard to get the PM box to display within the profile screen like the other bbPress profile mechanics. If I was a little stronger with php I would try to do it myself.

But if you could integrate your PM system onto that bbPress profile page, AND implement a pop-up notice message and maybe add some code for users to see an inbox counter on their main browsing page, I bet your downloads would skyrocket. And we would be eternally grateful. I know a lot of people who have complained in the bbPress forums about the lack of a PM system but like I said, those guys love BuddyPress, which is a bad solution.

Same problem, but wait, there’s more! I also cannot use BBCodes for links, but even worse, the existing link functionality is disabled so now the old link button doesn’t even bring up the HTML link.

This needs to be fixed right away.

Ha! Unbelievably, I was able to fix it on the first try.

width: auto;
height: auto;
max-height: 750px;
max-width: 750px;

Use that CSS for whichever img tag you are trying to adjust, and obviously size the pixels to what you want. That resulted in vertical and horizontal images retaining their correct aspect ratio with the longest side (vertical or horizontal, respectively) being limited to 750px.

Zach

Has anyone ever solved this?

The problem is WordPress (and the forum plug-in bbPress) both use the “width” value of an uploaded image to determine the screen real estate the image is given, whether the image is originally in landscape (horizontal) or portrait (vertical) format.

This results in a horizontal image of, say 600 pixels, being displayed significantly smaller than a vertical image, which will be given a width of 600 pixels *but a much larger height*.

The fix would be for WordPress to recognize whether the image is vertical or horizontal in size and to use the *longest side* to determine the screen real estate.

I can’t figure out how to do this in CSS. However LOTS OF OTHER FORUMS have solved this problem. Hell, even YaBB figured this one out.

So it has to have a fix.

Anyone?

I am having this exact same problem. Looks like you are also using the pinboard theme?

Anyone have any solutions to this? From what I can tell the smooshed up page is incorrectly calling to the .threecol CSS tag instead of the proper .onecol tag (which is what the appropriately-spaced sub forums are using).

Looks like I am ok at this point. My thumbnails did not survive the import process but I am batch uploading all my old graphics into the Media Gallery and they are being processed as thumbnails, which allows me to set feature images. A little bit of tedium but well worth it at this point. I think the key must have been getting .htaccess set right, as you thought all along Ipstenu. Thanks again for your help.

Ok I just tried one more thing: I uploaded an image using the Media Gallery uploader rather than via the post function. This time it did generate a thumbnail and I was able to choose it (once the thumbnail was visible) as a feature image in a test post:

https://www.itinerantangler.com/blog/podcasts/

And it displays on the main gallery page in the proper Pinboard theme as a featured image is supposed to.

Which leaves me I guess trying to figure out how to locate the missing image files in the Media Library. It looks like the importer populated it with all of the right images, but those images are not themselves being thumbnailed.

I suppose I could go through all 200 of them…

Swapping to the 2011 theme does allow the individual posts to be displayed, *but they have always been displayed if you clicked through to each entry.* Twenty-Eleven doesn’t require featured images and frankly isn’t the blog I’m looking for.

I swapped the child theme to Snapcase next, which is the theme running on the parent blog, and which relies on featured images (which incidentally work correctly on the parent blog). Unsurprisingly the Snapcase theme did not display any post content either, until you clicked through to the individual entries. In other words it behaved exactly like Pinboard, which is the theme I am trying to make work in the child.

So the bottom line seems to be that the child blog is not allowing or recognizing feature images. If I can get the feature images function working in the child I anticipate being able to choose any theme I want.

Thanks again,
Zach

With respect, the Theme I choose should have absolutely nothing to do with the issues I am seeing on the Administration pages involving the media library and the inability to set a feature image.

The parent blog, which is the Photoblog page on the overall site, is working just fine. I can set a feature image, and that feature image shows up both as a small thumbnail on the individual post page and also as an actual featured image in the post as viewed by the public.

In the child blog, which is the /podcasts/ page, I *cannot set a featured image* using the Administration page, regardless of how many times I select the image and regardless of whether I try to set it from the Gallery or from a URL link. It simply doesn’t show up on the Post page in the administration tools–instead I continue to have a ‘Set Featured Image’ link.

Here are a couple screen grabs:

https://www.itinerantangler.com/temp/medialibrary.png

https://www.itinerantangler.com/temp/featureimage.png

As you can see the thumbnails are grayed out in both. If I go to ‘rebuild thumbnails’ using either the Regenerate Thumbnails plug-in or the AJAX Thumbnail Rebuild plug-in, I get error messages saying the files can’t be found.

I have confirmed that my server populated the files over, however, when I did the import. There are plenty of pictures in /blogs.dir/2/files/12/.. etc.

What I think is happening is that somehow the Media Library in the child blog is unable to locate its image files despite having set the .htaccess correctly (as evidenced by the fact that I can now upload pictures to the Media Library, even though the thumbnails are not generated).

So I am at my wits’ end here. I appreciate your help.

One other thing: if I ‘view’ the individual attachment from the Media Library link, as opposed to just going to the actual file location, this is the result:

https://www.itinerantangler.com/blog/podcasts/2013/01/04/test-post/attachment/1034/

I feel like I am getting somewhere, but I still have issues with the media library and I still cannot seem to set a featured image, which is key fot the theme I am using.

I can now upload an image to the media library, and that image is searchable by its (redirected) link. For example:

https://www.itinerantangler.com/blog/wp-content/uploads/2012/12/jaystreamsmall.jpg

That picture showed up in the media library after I created a test post simply linking to it.

However, my media library still has no thumbnails. I downloaded a plugin called ‘Regenerate Thumbnails,’ and this is the error message it throws:

‘Debugging Information

Total Images: 1
Images Resized: 0
Resize Failures: 1

“jaystreamsmall” (ID 1034) failed to resize. The error message was: The originally uploaded image file cannot be found at’

Note that it doesn’t actually produce the file location, which tells me something is still not being redirected within the media library.

Overall setting up a multisite has been ridiculously difficult. I am really surprised as I thought WordPress was billing itself as a content management system at this point, and of course having different themes in different areas of a blog is a pretty straightforward request…

Any help would be greatly appreciated. I think if I can sort out the media library thumbnail linking issues I will be able to set feature images and my theme will probably work as promised.

This sounds like a wp_config.php issue somehow, so just for reference, here is my complete config file (minus the passwords):

<?php

/**
 * The base configurations of the WordPress.
 *
 * This file has the following configurations: MySQL settings, Table Prefix,
 * Secret Keys, WordPress Language, and ABSPATH. You can find more information
 * by visiting {@link https://codex.www.ads-software.com/Editing_wp-config.php Editing
 * wp-config.php} Codex page. You can get the MySQL settings from your web host.
 *
 * This file is used by the wp-config.php creation script during the
 * installation. You don't have to use the web site, you can just copy this file
 * to "wp-config.php" and fill in the values.
 *
 * @package WordPress
 */

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'USER_wordpress');

/** MySQL database username */
define('DB_USER', 'USER_USER');

/** MySQL database password */
define('DB_PASSWORD', 'PASSWORD');

/** MySQL hostname */
define('DB_HOST', 'localhost');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

/**#@+
 * Authentication Unique Keys and Salts.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link https://api.www.ads-software.com/secret-key/1.1/salt/ www.ads-software.com secret-key service}
 * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
 *
 * @since 2.6.0
 */
define('AUTH_KEY',         'put your unique phrase here');
define('SECURE_AUTH_KEY',  'put your unique phrase here');
define('LOGGED_IN_KEY',    'put your unique phrase here');
define('NONCE_KEY',        'put your unique phrase here');
define('AUTH_SALT',        'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT',   'put your unique phrase here');
define('NONCE_SALT',       'put your unique phrase here');

/**#@-*/

/**
 * WordPress Database Table prefix.
 *
 * You can have multiple installations in one database if you give each a unique
 * prefix. Only numbers, letters, and underscores please!
 */
$table_prefix  = 'wp_';

/**
 * WordPress Localized Language, defaults to English.
 *
 * Change this to localize WordPress. A corresponding MO file for the chosen
 * language must be installed to wp-content/languages. For example, install
 * de_DE.mo to wp-content/languages and set WPLANG to 'de_DE' to enable German
 * language support.
 */
define('WPLANG', '');

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 */
define('WP_DEBUG', false);

/* Multisite */
define('WP_ALLOW_MULTISITE', true);

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
$base = '/blog/';
define('DOMAIN_CURRENT_SITE', 'www.itinerantangler.com');
define('PATH_CURRENT_SITE', '/blog/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

SCRATCH THAT.

My host had set my wp-config.php file to turn on debug mode and they clearly forgot to swap it back out.

If anyone hits this problem, just switch this back:

define(‘WP_DEBUG’, true); <–ERRORS ON

define(‘WP_DEBUG’, false); <–ERRORS OFF

Zach

Oh and you can actually see the error even as a regular user here:

https://www.itinerantangler.com/blog/

Sigh. I feel like I am going backwards getting WordPress up and running.