WordPress 2.6.1 Beta 1

With 2.6.1, we’re continuing our trend of releasing a dot one release about a month after dot zero.  We want to get fixes for the inevitable dot zero bugs into your hands without a long wait.  If you’re happy with 2.6, you can ignore 2.6.1.

If you are an IIS or i18n user, we’ve fixed a few annoying bugs that might be bothering you depending on your hosting setup.  If you are an IE user who uses Press This, we fixed some image insertion problems for you.  Check out the full list of almost 50 fixes and see if 2.6.1 has something to offer you.

If 2.6.1 looks interesting or if you just want to help us test and make sure we didn’t break anything else, go grab the 2.6.1 beta 1 package.  If all goes well, expect the final 2.6.1 release before WordCamp San Francisco rolls around.

53 thoughts on “WordPress 2.6.1 Beta 1

  1. Has the View Site Link in the Admin been changed to open in a new Window? Having changed this myself it makes thing alot easier and quicker when needing to view a change by cliking this.

  2. That is quite a bit of silver polish going on an already rather shiny 2.6 release 🙂 I appreciate the .1 (etc) releases because it lets me resolve merge conflicts in small chunks, I’m off to grab it now.


  3. Any plans to fix the annoying bug with 2.6 where it cannot remember that you’re logged in, asking for you to sign in on every single visit to your admin panel?

  4. hi,

    when do you plan on fixing the mass delete in blog posts? it is very annoying because one cannot delete many posts at once. One has to go and open every post one wants deleted.

    also, when i make a post in “unpublished mode” it does not really go into that, it is still published and accessible to everyone who has a direct URL.

    i hope you do something about it, these are very simple features but has been overlooked for the longest time.

  5. Pingback: Paul Gossen
  6. Gareth, we had View Site opening in a new window for a while during 2.5 development and a lot of people hated it. So, it probably won’t be coming back.

    James, if clearing your cookies doesn’t help, then you have a bug I haven’t seen reported.

    Get it From Boy!, mass delete works fine for me and I haven’t seen a single mention in trac of this being broken.

    Elan, we are sticking with the unified insert image, which in my opinion completely blows away the old one.

    If you have problems, report them on trac so they won’t be overlooked. Don’t assume everyone else is having the same problems; that often isn’t the case. The problems mentioned here have not been reported in trac, so I don’t know about them. 🙂

  7. How about the Permalinks issue, where unless you use the default “?p=xxx” format, everything returns 404 errors?

  8. Well the reason why I liked the old insert image button is because it remembers old entries. I do a lot of picture tutorials so having it remember http://www.domain.com/images/dfdfdf01.jpg i can just view the cached url entry and change the image name #. Now I have to keep entering the entire URL which just makes it annoying as all hell. Please at least give the option in settings to add the old insert image button back.

  9. @Elan remembering the “form data” is actually a function of the browser and it works the same in both the old and the new Insert Image dialogs. Also double-clicking in the empty field would bring up a list of all remembered entries in most browsers.

    There are some browser settings to control that, perhaps have a look there. I’ve quickly checked it again in FF and IE and it seems to work fine.

  10. Just noticed it took that entry and now it’s cached under the Link URL part but it doesn’t cache it under the Source where it should be caching it since that is where I entered the text.

  11. There’s been a fair number of 2.6 users along with myself and 3 others I know of personally that although their actual sites seem unaffected except for comment posting time (slow with 2.6), have experienced significant Admin slow downs and complete hangs at times when switching between Admin pages.

    No real reason for it has been found with the exception of the more plugins that are enabled for the affected users, the slower the Admin runs but no specific plugin is causing the problem. All error logs associated with an affected site are clear (frustrating to say the least).

    In running 3 sites on the pre-2.6.1 builds the problem appears to be eliminated (Matt recommended using these builds to see if the problem went away). So this new release may be a bit more useful for those running on good old LAMPS servers than one might think.

  12. Pingback: ActiveBlogging
  13. “Any plans to fix the annoying bug with 2.6 where it cannot remember that you’re logged in, asking for you to sign in on every single visit to your admin panel?”

    Yes, that is really annoying, the cookie thing didn’t solve it for me for some reason.

    I’m going to try this beta version as I just upgraded a short time ago and all my categories and tags are missing – queries for categories bring up tons of 404 pages – quite depressing as going in and messing with tables isn’t really an option I’m not all that advanced in that regard.

    I imagine it can’t be any worse than it already is.

Leave a Reply