ThePLD

Yep…that’s where I figured it out…I thought I would post it in themes for better visibility…

Whoops! I wasn’t aware and didn’t find anything one it. Sorry about that…

Found the problem (at least for many users I suspect). TwentyTen (and probably some other themes as well) has the following style set for the content div:

#content img {
	margin: 0;
	height: auto;
	max-width: 640px;
	width: auto;
}

The auto width and height are causing the problem…

I think this is a bug. When using the resize, WP is simply setting a width and height to the image. The problem is that the image still has the original style class of the image you picked. This class overrides the parameters set when resizing the image. In other words, if you picked the “large” version of your image (let’s say 600px wide) but then resized it by 50% (300px wide), WP would spit out something like this (watered down version):

<img style="large-image" width="300" height="300" src="my_pic.jpg" />

So, the width and height are ignored as the style class has higher priority.

I was about to tell you that is what I have for the value…but I checked it right before I replied and noticed I had a typo in the path. So thanks for making me take another look ??

Take care…

This will exactly solve my problem…if I can get it working. Right now I upload an image and insert it into a post. The problem is that it never actually uploads the picture. The path of the picture is correct (if I view the page source), but it is not actually in the directory. I am guessing it is an issue with my $uploads[‘basedir’]. Should this be the path to my upload directory from root?

Much thanks!

Thanks, ipstenu…

So, the question begs…if they are the same, why do you need both? The same goes for the Upload path. 99% of the time it would be the directory path from the URL path. The other 1% of the time it could be configured in wpconfig…

This would be a beautiful thing. I have been working on it, but have not found a solution.

Anyone else?

I was so close to getting it working that I thought I could do it without the plugin. I will just do it your way ??

Thanks again…

Hey, Andrea. Thanks for the reply.

I don’t see any new folders. Out of curiosity, I went ahead and created another new site. Interestingly, the backend was accessible until I went into “Edit” and changed the domain to the alias (with “Update siteurl and home as well” checked). This makes everything copacetic except for the “Backend” link. The href of the link isn’t changing. I think WP just doesn’t like the alias in the domain. I am obviously missing something that tells it where the admin is located. Trying to get to the admin via the subdomain (obviously) doesn’t work either.

I hope that makes sense without being verbose…

I will move my question to a new post as this appears to be resolved.

…Not trying to take over the thread, but this might (or might not) shed some light on the issue??

We have setup 3.01 with subdomain based sites and are experiencing the same (or similar) issue. Meaning, everything works great except logging into the backend of the sites. We get the login screen but it simply loops and will not allow us to login.

What’s interesting is that we are NOT using the plugin (no wildcard access) but rather setup everything manually.