blogsterfiles

Thank you @mika …I have to run out at the moment and will have to re-create it when I return, but the error message starts the same and references various php pages and line. Searching the specific errors, all the forums indicate the errors are because of blank lines at the end of the file or \<?php\ was not closed i.e. \?>\ … WordPress no longer uses the close tag on many pages and the blank trailing lines have never been a problem before.

The define is going above the line /* That’s all, stop editing! Happy blogging. */, as I have always placed it. Bear in mind, I’ve done this dozens of times over the past few years and nothing has changed in the method used. I’ve literally spent hours on the phone with multiple people sending me links to their’s and WP codex instructions walking through it. Each time they have concluded it is a WP issue, not the install or their servers.

Thanks very much, will follow up with the error messages when I return.

Thanks very much @mclmarcos …Your code added at line 658 solved the problem for me!

LOL…yep I get it. ?? You gave me a great clue too pirate girl. I still ran into a bit of trouble today. After my earlier fix (step 1 & 2 above) images displayed great in the gallery and in posts but they rendered as txt instead of images whenever I drilled down to the generated sub-domain image URLs. So I went to wordpress trac and read and read. I found two other lines of code that did what my edit had done so I copied the entire contents of the ms-file.php (Changeset 15473) and pasted it into my test sites ms-files.php. Images still did not show, so I added ob_clean(); near the bottom, just above readfile( $file ); (same as step 2 from above) …and VOILA!!! I now have what seems to be a fully functional WP 3.0.1 multi-site on my Media Temple VPS! A caveat for bystanders though, I’m just thrashing around in the dark so I don’t recommend anyone follow my meager efforts, however, perhaps you can do something with this info or pass it along where it might do some good. Whew…glad to put this one to bed. Thanks for sticking with me. ??

@telegram …Did you solve your image problem? If not, there may be an answer for you here. Check the last few posts there and if you don’t mind, let me know if the solution (editing ms-files.php) is any help. I’m a novice, so I’m interested in knowing if this works for anyone else. Thx

@andrea_r People are drawn to WordPress like flies to honey because it’s great; open source, free of purchase cost, incredibly adaptable to the needs of many, and is supported by great people such as yourself whom give freely of their time helping others. The image problems that arise for some when creating a network in 3.x are varied, as are the fixes. I think everyone knows by now that most problems are caused by folks just not following instructions, while some need proper deployment of server settings, tweaking of .htaccess and httpd.conf (vhost.conf on Media Temple), etc.

When I talked to my computer guy this morning, he scolded me (again) for using WP at all. He thinks it’s a bad deal. You on the other hand think I shouldn’t be here because it’s complex and I don’t know enough to deal with it. You are right, but in Pirates of the Caribbean, when Jack Sparrow was accused of lying or stealing, his only defense was to utter the word, “Pirate”. My answer to all objections to me or anyone using WP for any reason is (in the spirit of Jack Sparrow), “Honey”!

After all is said and done, it appears the cure on my Media Temple VPS was in WordPress code (ms-files.php) and not in my server or failure on my part to follow instructions. To narrow the trouble, I was working with a bare-bones, spanking-new install of 3.0.1. Now that I am past this monstrous image roadblock, I am in the process of testing Buddypress and various plugins. If anyone is interested, let me know and I’ll gladly share whatever I learn. In the mean time, whether it’s across all servers or not, it bites, itches, and requires scratching, so I’m calling it a bug. ??

Never give in. Never give in. Never, never, never, never–in nothing, great or small, large or petty–never give in, except to convictions of honor and good sense. ~Winston Churchill 1941

This has been a pox on my existence. I believe this problem IS a WordPress BUG!! I finally got my programmer to look at the problem and all these posts this morning. He worked on the blog for about an hour and now everything is working. He laughed when I said people here are saying it is not a WP bug. In any event, this is what he sent me and it is now finally working:

The problem is in the wp-includes/ms-files.php

1. Put double quotes into the header function on line (41ish)
Original: header(‘Content-type: ‘ . $mimetype ); // always send this
Fixed: header(‘”‘. ‘Content-type: ‘ . $mimetype .'”‘); // always send this

2. Call ob_clean before the readfile on the last line:
ob_clean();
readfile( $file );

This is exactly the same problem I’m having. I loaded a fresh install (3.0.1) with the default theme and no plug-ins, so it is not likely your theme. You might want to look HERE. @gazouteast had some good advice and I’m waiting for an answer to my comment/questions.

WP is wonderful when it works, and a goldmine in the fact that with limited coding skills we can usually get a site up for a few hundred dollars and some sweat equity vs thousands to hire a pro.

In my case, as with many others, images are being uploaded and any ‘real’ file path serves up images. i.e. https://jethro.foundersbench.org/wp-content/blogs.dir/2/files/2010/08/oldglory-420×260.jpg works fine, but the WP generated file path does not: https://jethro.foundersbench.org/files/2010/08/oldglory-420×260.jpg

In desperation, I just moved to a new VPS at Media Temple. My computer guy set up WPMU for me in a new test domain on the new VPS and after testing for about a month, we set up another brand new domain and loaded 3.0.1 fresh out of the box only to have images break (again) on sub domains as soon as we converted to multi-site.

I read these forums for days trying EVERYTHING without success until finally my programmer gave me several hours of trouble shooting. I asked him if he was sure Apache was reading .htaccess and he said, that was the first thing he checked. It is being read and the files are redirecting correctly to the file processing script but the process crashes at some point after that. He is not a WP programmer and has no interest in pouring over unfamiliar code, but he said this problem will persist until someone involved in the project recognizes there IS a WP problem here.

WP may be a victim of its own success since it attracts so many newbies, but as long as all those unresolved Google comments linger (yep, hundreds conservatively), it will reflect badly on WP without regard to whether it is a WP problem or a diabolical conspiracy of the world and its idiots.

@gazouteast you can see you’re not the only one letting a little frustration escape into the ether! ?? Can you provide an example of the links that were banjaxed, and how they were malformed? Thanks much in advance for your help if you can!