WordPress MU

I've been a pretty faithful user of Wordpress MU for almost the last two years. I just upgraded from 1.3.3 to 1.5.1, and I'm super pissed.

At first, everything seemed to be great. A couple of broken plugins, that I've been dilligently trying to fix for the last six hours. Then, the other author I have on the system ran into problem 'one'.

He uploaded his images for the post just fine, but when it came to inserting them, it bunged up huge. Selecting the 'thumbnail' option did NOTHING. Problem 2 comes in when the code inserts:

<a
href='http://thewatchtowerpodcast.com/files/2008/06/thestand2.jpg'><img
src="http://thewatchtowerpodcast.com/files/2008/06/thestand2.jpg"
class="alignleft size-thumbnail wp image 180" />
</a>

instead of:

<a href='http://thewatchtowerpodcast.com/files/2008/06/thestand2.jpg'>
<img src="http://thewatchtowerpodcast.com/files/2008/06/thestand2-150x150.jpg"
 class="alignleft"
size="thumbnail"/>
</a>

forget to close some quotes? Why would the class be "alignleft size-thumbnail wp image 180" ???

Then, (problem 3!)one of my plugins (that's supposed to be cool for WP 2.5.1) messed up not only my front page, but my themes widget editing page - cuts it off where it's supposed to appear. I deactivate, reinstall it, and attempt to undo what I figured I did to the options to cause it - and it's still set to the settings I had changed it to, which means I had to go into the db to fix it.

Then I found problem number four.

Why the hell is the entirety of Photo Matt's blog in my database???

Look guys - I most of you are doing this on your spare time, and it's all GPL and what not - but this is the sloppiest bit of programming I have EVER seen, and I'm not even a remotely decent programmer. If it's not ready for release, DON'T RELEASE IT.

There's no need for a rant. If you found bugs please submit a Trac ticket:
http://trac.mu.wordpress.org/

Thanks,
Andrew

Um ... It's a release CANDIDATE, dude. Use at your peril.

No need for a rant?

There's plenty of need for a rant. Bugs are one thing. Having the entirety of other peoples blogs dumped into my db is something else.

When you put something up for PUBLIC DOWNLOAD as a stable release, you are saying, as the authorities surrounding this, that you've created a stable, publicly viable vehicle for people to use. the If it still needed testing, then it shouldn't have been released. I don't even know where to begin to fix all of this stuff, or what I might break in the process! I have hundreds of entries in my database now that aren't linked to a blog id that I've created! I can't create posts properly!

I don't even know how to classify this as a bug! How do I explain properly to you that I have the entire blog of ma.tt in one entry of my <prefix>_options table? Including links to all of his photos! Stuff that doesn't even look like the public should see it!

I want an explanation, not a bug tracked!

Candidate? IT'S ON THE DOWNLOAD PAGE. IT'S RELEASED.

Gee there, no reason, I've upgraded several sites to 1.5.1, and it works just fine.

Maybe you lack the competence for running MU? Hmmm, after throwing a fit like that, that would be my first guess.

So there's a few extra classes. That isn't a show stopper. You want show stoppers, see Windows/Microsoft.

Finally, because a plugin that someone else wrote screwed up your site (lack of competence again?), you wish to blame MU. Sorry, but that's a load of crap.

It's well known, discussed, and documented that at times plugins may be WP compatible but not MU compatible.

Your best bet: stand in the right line to get a clue. You obviously took more turns than necessary in the jerk line instead.

I see you've made a post again as I made my previous one.

Whatever you've done, you've done.

I've installed clean and upgraded 1.5.1 dozens of times. Nowhere is Matt's blog taking up space in any of my databases.

Not sure you really have the skills to be trying to use MU.

Again. The few extra and little things I don't mind. I've gone through this with EVERY release of MU, and had to fix little things here and there. No biggie. I've done just fine with what I consider my own limited resources. I know I'm nothing special, and I said that - but I recognize when somebody missed something they shouldn't have.

And I wasn't blaming you for the plugin - I know better than that. I'm just saying that the previous stability that we enjoyed with earlier versions is completely out the window with this behemoth.

Bu I noticed Lunabyte, you skipped over trying to reason out why Ma.tt's blog is in my db. Want an excerpt?

<p><strong>Friendlier visual post editor</strong> — I’m not sure how to articulate this improvement except to say “it doesn’t mess with your code anymore.” We’re now using version 3.0 of TinyMCE, which means better compatibility with Safari, and we’ve paid particular attention this release to its integration and interaction with complex HTML. It also now has a “no-distractions” mode which is like Writeroom for your browser.</p>
<p><strong>Built-in galleries</strong> — when you take advantage of multi-file upload to upload a bunch of photos, we have a new shortcode that lets you to easily embed galleries by just putting [ gallery] (without the space) in your post. It’ll display all your thumbnails and captions and each will link each to a page where people can comment on the individual photos. I’ve been using this feature on my blog and have already uploaded over <a href="http://ma.tt/category/gallery/">1,200 pictures into 23 galleries</a>. The shortcode has some hidden options too, <a href="http://codex.wordpress.org/Using_the_gallery_shortcode">check out this documentation</a>.</p>
<h3>Developer Features</h3>
<p>Now for the geeky stuff. While we’re excited about the above features, each one represents a new opportunity or API for other developers to take to another level. (The best of which we’ll someday integrate back into WP.)</p>
<p><strong>Salted passwords</strong> — we now use the <a href="http://www.openwall.com/phpass/">phpass</a> library to stretch and salt all passwords stored in the database, which makes brute-forcing them impractical. If you use something like <a href="http://modauthmysql.sourceforge.net/">mod_auth_mysql</a> we’ve <a href="http://wordpress.org/extend/plugins/md5-password-hashes/">created a plugin that will allow you to use legacy MD5 hashing</a>. (The hashing is completely pluggable.) Users will automatically switch to the more secure passwords next time they log in.</p>
<p><strong>Secure cookies</strong> — cookies are now encrypted based on the protocol described <a href="http://www.cse.msu.edu/~alexliu/publications/Cookie/cookie.pdf">in this PDF paper</a>. which is something like <code>user name|expiration time|HMAC( user name|expiration time, k)</code> where <code>k = HMAC(user name|expiration time, sk)</code> and where <code>sk</code> is a secret key, which you can define in your config.</p>
<p><strong>Easy taxonomy and URL creation</strong> — probably best illustrated with an example: I can call <code>register_taxonomy()</code> with <a href="http://trac.wordpress.org/attachment/ticket/6357/taxes.php">a few arguments</a> to register a “people” taxonomy and whenever I edit an image I’ll see a UI like tags has for identifying the people in a photo, and these will be URL addressable with <code>/person/firstname-lastname/</code>. All with a single function call.</p>
<p><strong>Inline documentation</strong> — the vast majority of the new code going into WordPress include inline documentation that explains the functions and documents their arguments.</p>
<p><strong>Database optimization</strong> — we haven’t changed the table layout in this release, which is one of the reasons so many plugins work fine with 2.5. We have added a few new indicies and made a few default fields more flexible based on some bottlenecks we found on WordPress.com, which now hosts 2.7 million WordPress blogs. It should be invisible to the application, just a bit faster on the database side.</p>
<p><strong>$wpdb->prepare()</strong> — now almost all of the SQL in WordPress is prepared first, and the same functions are available to your plugins. This should prevent elementary SQL escaping issues.</p>
<p><strong>Media buttons</strong> — the add media buttons above the post are both expandable, so you could have an “Add Google Map” button if you like, They can be overridden, so if you think you can do the video or audio tab better than we have you can replace the default.</p>
<p><strong>Shortcode API</strong> — the new gallery functionality is powered by the new shortcode API. Shortcodes are little bracket-delineated strings that can be magically expanded at runtime to something more interesting. They give users a short, easy to type and copy/paste string they can move around their post without worrying about messing up complex HTML or embed codes. <a href="http://codex.wordpress.org/Shortcode_API">The Shortcode API is fully documented</a>.</p>
<p>Now you see why 2.5 took a little extra time. <img src='http://wordpress.org/development/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>

Here's another one:

<ul>
<li>Amount of comment editing time</li>
<li>Spam Notification Text (Displayed when comment is detected as spam)</li>
<li>Options for Anonymous Users</li>
<li>Options for Registered Users</li>
<li>Whether or not to display the editing countdown timer</li>
<li>The ability to edit emails</li>
<li>Your choice of spam protection from either Akismet, Defensio or None.</li>
<li>Styles ( Specifically button styles and editor styles)</li>
<li>Character Encoding</li>
<li>Individual Options that only affect you</li>
<li>Ajax Edit Comments Cleanup (This will delete the security keys associated with the comments)</li>
</ul>
<p>So far, I’ve upgraded Ajax Edit Comments on my personal site and the plugin has been working flawlessly so far. I actually prefer this version over the other, primarily because of the interface changes. Ronald has done an excellent job with the new version and I recommend everyone download and give this plugin a try. In my opinion, it is very frustrating to comment on someone’s WordPress powered site and discover that there is no way to edit your own comments. I believe that editing your own comments should be one of those features that should be added to the core of WordPress. But until that happens (if it does) this plugin makes an excellent addition to your blog.</p>
<p>As a side note, Ronald has told me that he coded the plugin in such a way that it would be pretty easy to implement it into the core.</p>";}i:5;a:7:{s:5:"title";s:35:"Donncha: Fifty years with WordPress";s:4:"guid";s:29:"http://ocaoimh.ie/?p=89493722";s:4:"link";s:56:"http://ocaoimh.ie/2008/05/29/fifty-years-with-wordpress/";s:11:"description";s:2471:"<p>Ah yes, them were the days when we had to type blog posts on quaint old keyboards. Can you imagine it? You actually had to write everything letter by letter. Today’s thought entry systems are so much more convenient don’t you think?</p>
<p>That there Matt fella is still the youngster he always was. He may not be quite as fast on his feet but that embedded camera in his skull sure takes some snazzy photos. My camera gives me a headache, especially when the lens doesn’t focus fast enough. Great to see that mind blog integration stuff working out for him though. I can’t believe blogging has come so far in such a short time.</p>
<p>Oh wait! Fifty? It’s only been five. Where have the years gone? Matt noticed that I officially <a href="http://wordpress.org/development/2003/05/donncha-joins-team/">joined the WordPress team</a> 5 years ago today! At the time I was working on the predecessor to WordPress MU, b2++ that was running on <a href="http://blogs.linux.ie/">Linux.ie Blogs</a>. It was a sometimes hard slog. MU was always on the sidelines of the WordPress community and somehow it escaped the attention of the vast majority of people online. I noticed many surprised voices when people found out what was running on WordPress.com!</p>
<p>Two years later and Matt starts Automattic and I come on board to work on WordPress.com and I’ve never looked back. The GPL licensed WordPress and WordPress MU go from strength to strength. </p>
<p>As a final note on this rambling post, if you enjoy using WordPress, head over to gnu.org and read <a href="http://www.gnu.org/philosophy/philosophy.html">their philosophy page</a> to find out what influences Matt and Alex and everyone else who contribute to GPLed software projects.</p>
<p><img src="http://ocaoimh.ie/?voyeur=1" /></p><p><strong>Related Posts</strong><ul><li><a href="http://ocaoimh.ie/2002/02/09/i-went-to-see-behind/" rel="bookmark" title="Permanent Link: I went to see Behind Enemy Lin …">I went to see Behind Enemy Lin …</a></li><li><a href="http://ocaoimh.ie/2007/11/07/donnchas-wednesday-links-2007-11-07/" rel="bookmark" title="Permanent Link: Donncha’s Wednesday Links">Donncha’s Wednesday Links</a></li><li><a href="http://ocaoimh.ie/2005/08/17/whats-this-wordpresscom-thing-anyway/" rel="bookmark" title="Permanent Link: What’s this WordPress.com thing anyway?">What’s this WordPress.com thing anyway?</a></li></ul></p>";s:7:"pubdate";s:31:"Thu, 29 May 2008 17:21:57 +0000";s:2:"dc";a:1:{s:7:"creator";s:7:"Donncha";}s:7:"summary";s:2471:"<p>Ah yes, them were the days when we had to type blog posts on quaint old keyboards. Can you imagine it? You actually had to write everything letter by letter. Today’s thought entry systems are so much more convenient don’t you think?</p>
<p>That there Matt fella is still the youngster he always was. He may not be quite as fast on his feet but that embedded camera in his skull sure takes some snazzy photos. My camera gives me a headache, especially when the lens doesn’t focus fast enough. Great to see that mind blog integration stuff working out for him though. I can’t believe blogging has come so far in such a short time.</p>
<p>Oh wait! Fifty? It’s only been five. Where have the years gone? Matt noticed that I officially <a href="http://wordpress.org/development/2003/05/donncha-joins-team/">joined the WordPress team</a> 5 years ago today! At the time I was working on the predecessor to WordPress MU, b2++ that was running on <a href="http://blogs.linux.ie/">Linux.ie Blogs</a>. It was a sometimes hard slog. MU was always on the sidelines of the WordPress community and somehow it escaped the attention of the vast majority of people online. I noticed many surprised voices when people found out what was running on WordPress.com!</p>
<p>Two years later and Matt starts Automattic and I come on board to work on WordPress.com and I’ve never looked back. The GPL licensed WordPress and WordPress MU go from strength to strength. </p>
<p>As a final note on this rambling post, if you enjoy using WordPress, head over to gnu.org and read <a href="http://www.gnu.org/philosophy/philosophy.html">their philosophy page</a> to find out what influences Matt and Alex and everyone else who contribute to GPLed software projects.</p>
<p><img src="http://ocaoimh.ie/?voyeur=1" /></p><p><strong>Related Posts</strong><ul><li><a href="http://ocaoimh.ie/2002/02/09/i-went-to-see-behind/" rel="bookmark" title="Permanent Link: I went to see Behind Enemy Lin …">I went to see Behind Enemy Lin …</a></li><li><a href="http://ocaoimh.ie/2007/11/07/donnchas-wednesday-links-2007-11-07/" rel="bookmark" title="Permanent Link: Donncha’s Wednesday Links">Donncha’s Wednesday Links</a></li><li><a href="http://ocaoimh.ie/2005/08/17/whats-this-wordpresscom-thing-anyway/" rel="bookmark" title="Permanent Link: What’s this WordPress.com thing anyway?">What’s this WordPress.com thing anyway?</a></li></ul></p>";}i:6;a:7:{s:5:"title";s:70:"Weblog Tools Collection: Removing Width/Height from the Image Uploader";s:4:"guid";s:40:"http://weblogtoolscollection.com/?p=3600";s:4:"link";s:98:"http://weblogtoolscollection.com/archives/2008/05/29/removing-widthheight-from-the-image-uploader/";s:11:"description";s:2571:"<p>Reader Vivien writes in:</p>
<blockquote><p>Is there a way to prevent WordPress from inserting the width and the height for images in the new 2.5 media manager?</p></blockquote>
<p>In short, yes, but it requires you to insert some code into your theme’s <strong>functions.php</strong> file.</p>
<p>Fortunately, there is a WordPress filter we can use called <strong>image_downsize</strong>, which takes in three arguments (a boolean, an attachment ID, and a size string).</p>

It goes on for pages. I can't even search properly through my db because my shell program has a limit on how many lines it can display.

Thanks for your arrogance.

It's part of something with the rss feed as near as I can tell. Though, I've never seen an rss feed stored in the db before. Sound like something I've done?

option_id: 76
     blog_id: 0
 option_name: rss_0ff4b43bd116a9d8720d689c80e7dfd4

I'll tell you what. You'll be getting no help no sympathy from me.

Asshat: Denied.

I think those are the "default" feeds to Planet Wordpress that are stored. Once in the admin you can edit the feeds to whatever you want to show up and not to wordpress plugin and wordpress planet. Nothing to be worried about I don't think. Once you chanage the feeds, you can delete those RSS entries from the db and it won't matter.

Trent

Trent,

I applaud your tolerance and patience with such a post. I would have just copied and pasted:
[blockquote]"WordPress MU is a multi user version of WordPress.

If you're not comfortable editing PHP code, taking care of a complex
webserver and database system and being pro-active about following
developments of this project then run, don't walk, to
http://wordpress.com/ and sign yourself and your friends up to free blogs.
It's easier in the long run and you'll save yourself a lot of pain
and angst.[/blockquote]

From the readme along with a quick note about what a release candidate, the open source community and common courtesy are.

I'll try and be more like you though. It's much more useful.

Trent - there's no reason they should be storing the whole post though, considering the Dashboard just displays titles and links. That's an awfully heavy amount of bandwith and db traffic for no reason.

That sounds like a screw-up to me.

I apologize if my tone has been harsh. I'm tired, cranky, and frustrated with this release - and people making excuses for it.

Lunabyte: GFY.

Being honest, I just skimmed the thread, it has nothing to do with tolerance.

http://en.wikipedia.org/wiki/How_to_Win_Friends_and_Influence_People

I had some problems with a recent upgrade myself (wpmu-1.2.5a to wpmu-1.3.3; coincidentally enough, they related to RSS feeds as well), however, I chose to keep my unsanitary language to myself, and revert my database & code back to the backups.

This is a community of people, who work together for a common goal, so it is paramount that we all maintain a level of respect for one another. Even if a mistake is made, and I'm not 'taking sides' one way or the other... But if a mistake were made, it would've been made with good intentions, and therefore (IMHO) not worthy of vehemence or ill will.

We all have enough stuff going on in our lives, that we don't need the WordPressMU Forums to be a place any of us have misgivings about visiting. We're all (I perhaps naively believe) are here to help one another.

I suggest we either drop this thread if there isn't a question or plea for help (don't delete it! we need it for posteriority or something)... and go have a tira misu or a favorite dessert.

Reread what I wrote.

I didn't swear, or use 'unsanitary' language (at first). I pointed out that it was sloppy. I ranted because I am now behind on the work I actually wanted to do because I've been digitally running around trying to put out fires all day.

I post my frustration here, in the hopes that someone is going to recognize the problems, and just answer it instead of making me run around more and wait for the next release.

Instead, I'm met with arrogance, condescension and dismissal.

A release CANDIDATE isn't supposed to be for Public Release - should have kept that in the test beds, or at least noted it somewhere - on the Download Page, in the Readme, somewhere. I took a second and third look around, and it doesn't say anywhere that is a beta, theta, omega, or gamma test. There's no warning on that. When I get to the Download page, and it says that 1.5.1 is ready for release, I believe you.

Something as simple as the insert code for the images shouldn't have been missed. Hasn't anyone else had that problem? If not, how would it have occurred?

The Plugin isn't your problem. That's mine, and I'll have to find something else. I included it because it led me to find the rss feed is dumping huge amounts of data into my database - and that's not something *I* did. And that's new, at least to 1.3.3, because it wasn't there before that. That's inconsiderate coding - there's no need to dump that much data into my db. That's bandwith and space that costs me, and I'm not running MU for tons of people to blog and make money. I run MU because it was the easiest thing to run multiple sites from one control panel.

So I reiterate - I apologize if my initial post was overtly harsh. I meant no personal insult to the individuals behind it.

However, I don't apologize for my responses to the people who decided to question my competence or call me a 'Jerk' or an 'Asshat' because they got called out on missing the mark on this bloated release, or what I was talking about. I've handled all the previous releases, and rather well, I think for someone that doesn't do this for a living, nor has any formal training - and I don't have time to keep up with every build and release and bit of news with it.

That's a huge expectation on your part.

I'm done with it though. I didn't need a backend with flashy image uploads and all kinds of spiffy little features that don't work. I wanted something nice and light, easy to use and modify, like it used to be. I'll find something else.

Take care,
NR

NoReason,

I don't know if you thught about it, but the "insert code for the images" could be a issue from the core of WP, that is merged into WPMU.

As I know there are stil several issues with images for WP, even if some where solved in the 2.5.1 release of WP. All the problems will follow into WPMU automatically.

ok, I admit it. It was me.

@NoReason

I hope you realize that you've attacked innocent people. I understand that you're frustrated but you can't blame others for that. Can You even imagine how much time was spent to develop this platform. There are tons and tons of code included in it. Btw, You know how are things with WP. No one forced You to use it and you were probably warned to use it at your own risk. No offense but I really don't like people who are always right.

NoReason,

first things first. Your generated code you pasted displays the difference between old and new. The new code is as expected and better written than the old code. Why? Because it uses CSS to style the content with, instead of using (x)HTML. The old code of yours is having a property that doesn't exist as well. So be happy, now you got proper code!

Error #1 - I can't find the "thumbnail" option in either WP 2.5.1 or WPMU 1.5.1.

Error #2 - You got several classes because they've tidied up the code and uses CSS to style your content with. Which is a good thing. Not a bug.

Error #3 - Try and rename the directory of the plugin/theme showing up erronous in the backend. If it removes the problem, it's a problem with the plugin/theme. (And yes. The backend code of WP could manage such troublesome plugins/themes better but still primary cause with the plugin/theme.)

Error #4 - Uh? I've installed WP 2.5.1 on a handful servers. Works as expected. I've installed WPMU 1.5.1 on four different servers. Works as expected. I have no trace of any content in the DB's after installation. Is it due to a faulty plugin, since it's certainly not in the 1.5.1 package you and I amongst many others have downloaded and installed.

So.

I cannot replicate the "bugs" you write about. Try and fill us out with how you install & manage your installation upto the point where those "bugs" appear and someone might be able to help you out.

This is also crucial in order to fix any bug appearing in the codebase, since you seem to be the odd one out there who has all those "bugs". The rest of us haven't.

bloggus - yes, I have.

"No offense but I really don't like people who are always right."

That's funny.

Error #1:
Click on 'Add Media'. Upload an image or two. Once you have images in your gallery, click on the gallery tab in that pop up. select the image, and go down through the options: Title, Caption, Description Alignment, Size (which is where 'thumbnail' appears), etc. Then hit the 'insert into post' button. It's right there.

Error #2: The several classes don't appear to have been encoded properly - whether or not that was done right or not, the 'thumbnail' option should have selected the alternate images the uploader created - I had to manually go in and find out what it had created. Same problem has existed since 1.3.3 - except the filename had to have .thumbnail added in e.g. - imagename.thumbnail.jpg. I'm surprised that this error is still in the code, especially considering it's been altered between major releases. I love CSS - that wasn't the problem here though.

Error #3: For the third time - not your problem. I had to delete it anyways. Support for third party plugins is not expected, nor was it.

Error #4: From whatever database management tool you run select statements from, run this on any of you options tables (my prefixes were wp, so it was wp_1_options, wp_2_options, etc):

SELECT * FROM wp_1_options\G (or ; if you prefer)

and in each of those tables you'll find the entirety of the Planet Wordpress RSS feeds - and not just titles and links, but full-on posts, including gallery listings of Ma.tt's most recent blog about greece. - That's coming off of the wordpress install, not any plugins I'm running. It's duplicated in each of my options tables (which were fresh installs as of 1.3.3). If it's pulling down fresh content though, I have to assume 1.5.1 is doing it as well.

I didn't swear, or use 'unsanitary' language

Instead, I'm met with arrogance, condescension and dismissal.

I suggest you reread the title of this thread as well as your first post.

I will give you this much though. As to error 1, some specific details would be helpful. The software won't provide a thumbnail is the image is too large in filesize or width/height. That's been a known programmed limitation of the software for quite some time now and is probably what you're hitting. Images that are too large are not given the option for thumbnailing.

And "Matt's posts" are the rss feed that shows up on each blog's dashboard from Planet Wordpress. That's normal as noted and is found within regular wordpress as well. The RSS feeds are cached.

I have to say though I would hate to be your clients.

It create the thumbnails. Image size is not the problem. But the insert code doesn't seem to know that two additional images were created from the original upload - so that if you hit insert, it's still inserting the actual image instead of the thumbnail.

Let me spell it out for you specifically:

When you select 'thumbnail' it should insert imagename-150x150.jpg into the <img> tag, not imagename.jpg

It created the thumbnail files, so why isn't it inserting the thumbnails?

The rss feed cache?

Don't dismiss it - that's *not* normal, or it shouldn't be. Why is the full post cached in my db, instead of just a link and title, when the full post appears nowhere in my dashboard? That's problematic if I was running a huge site with hundreds of users - That's tons and tons of duplicated, unnecessary data in the database. Heck, I consider it problematic for my little system.

When I started out with this stuff, I was doing online GUI for one of North America's largest white-label hosts. Having that amount of crud in the DB - especially on a scaling mulit-user platform, would have gotten someone fired.

You get what you pay for, I guess.

You get what you pay for, I guess.

?

It's open source, relax.

I can see if you were actually paying for this software. If you were that good at doing online gui, you would have seen that testing anything before putting it on a production box would have been your first priority.

I think you need to take a step back, rethink your options, and purchase a package where someone can hold your hand and listen to your needs.

Your rants really make me pissed off because there was as lot of hard work that has gone into this project to mold it to the way the community wants it to work. If you can't see that, you're just a novice with a title.

@NoReason - Yes it is.

I also hate when my bad English plays tricks on me:)

What I meant to say was; "I don't like people who always think that they are right"... or something like that.

Btw. that 'thumb' problem is probably caused by some other plugin you are using. That's my opinion. It's working fine on my installation. Only once I had a problem with creating thumbs and that's because images were saved in 'grayscale' mode instead of 'RGB'.

Oki, now I understand.

Error #1
I can't get image uploads working on my current install that I'm toying with.

Error #4

I just stripped 426 992 bytes from my wp_options table. That was the rss entries mentioned above, that got stored directly in the vanilla version of the database. The fields had id of 88 to 92 from a vanilla installation.

That explains why the DB per blog skyrocketed after I had entered admin first time after install compared to directly after installation without logging into admin.

With 100 blogs, it would mean 42MB of extra DB space used for nothing but Matt's blog entries. Anyone wanna explain how this is a good thing? :)

GFY, huh there reason?

That's funny.

Keep it up, have a day.

One day, you may have a clue. Although I won't be betting on how soon.

Nope, still no help from me. It's a shame you came out so pathetic and then continued. Else your questions could have been answered completely by the 3rd post. Shame, eh?
<roll eyes>

"How do I explain properly to you that I have the entire blog of ma.tt in one entry of my <prefix>_options table?"

Because it's in the dashboard feed. The entries in the dashboard from WP planet get cached in your database. It's been like that since... for ever? It's what you'd find on a stand-alone WP isntall too.

Now, I'm not saying that's a good thing, but there you go. A non-yelling post would get better answers and some learning instead of the pissing contest most threads degrade into.

ansd to reiterate: Donncha works on MU. Just him.

Are there room for improvements? Oh, plenty. I know. But this kind of thread will not get *any* of them fixed.

I'm not even a remotely decent programmer.

well, when you become a decent programmer, maybe you can code your own blogging platform. until then, get off Doncha's back and fix your own problems. you could have just posted the bugs in track and STFU rather than getting your rocks off here in the forums. there, you've had your shine - offer something or go away. can a keymaster just close this thread?

My upgrade went perfect. The only times my upgrades have not been perfect are when I messed up and thought I had upgraded all the files and hadn't. It has always been my fault unless I was running an RC on a test server, then I have seen bugs.