Slashdot Mirror


WordPress 2.0 Released

cyberchucktx writes "Version 2.0 of the Wordpress open source blogging software has now been released." From the post: "In the past if you were linking to a number of posts or pinging a lot of update services, your posting time could appear to slow to a crawl even though everything was instantly done on the backend. We've modified how this works now so posting should be near-instantaneous, like everything else in WordPress."

7 of 105 comments (clear)

  1. If history really repeats itself by SethD · · Score: 4, Funny

    If history is any indication, there will be a 2.0.1 release soon. I can wait ;)

    1. Re:If history really repeats itself by ATinyMouse · · Score: 4, Insightful

      I've been using WordPress 1.5.2 for the last several months to blog about my daughter Bethany who was born in July. I upgraded my daughters blog and my nephews blog to 2.0 last night. I recommend following the upgrade instructions, they list several different times to backup your database and files and not to go any further unless you do. Even though I never had to use the backup, I'm glad I had it. Once the upgrade completed I couldn't browse my blog, but the problem was related to a coding bug with my custom theme. After I fixed it everything has been rock solid.

      Some of the biggest changes I've noticed so far is the admin screen using a Google like dragging and dropping interface for placement of window frames. The added WYSIWYG HTML editor is nice, but when I click on the formatting icons in Firefox none of their actions "stick." I'm pretty sure the problem is related to an extension, I just haven't figured out which one yet. They added a theme preview when picking themes instead of the text one they use to have and categories for your posts can be added on the fly. An even more exhaustive list is here.

      I've only used it twice to post entries since the upgrade, but I'm really happy with what I've seen so far.

  2. Re:MySQL facists!! by shark72 · · Score: 5, Insightful

    "Why not support for PostgreSQL? How hard can it possibly to write code that supports more then DB? It's unbelievable that almost no blogging software supports a real RDBM."

    WordPress is open source. This means that if you like, you can contribute by making the improvements yourself. That's how open source software tends to be improved... each contributor adds the features that they would like to see.

    At the very least, you should give it a try. If you're right, and adding PostGRE is the trivial task that you imply, then it should be a snap, and WordPress will be the better for it. If it turns out to be a little too daunting, then you'll have answered your own question of why it hasn't yet been done.

    --
    Sitting in my day care, the art is decopainted.
  3. Re:MySQL facists!! by vidarlo · · Score: 4, Insightful

    PHP has database specific functions, mostly. Whilst it is not too hard, it is some work. As it is open source, I suggest that you write your own database functions, and make it work. It's your right to fork it. Really. All web hotels I've came across uses mysql, it is the single most popular db for php-stuff. It's for a reason that LAMP is LAMP, not LAPP ;)

  4. Re:Give it a little time ... by RobotRunAmok · · Score: 5, Funny

    wait until the first point release before deploying to important systems.

    It's blogging software. How important can any of the systems be?

  5. Re:Apache for Windows support by chrisgeleven · · Score: 4, Informative

    Not only are you using an ancient version of WordPress, you are using one that has some serious security issues. You need to invest in making it work.

    I have gotten WordPress 1.5 to work on Windows before just fine, even with Apache running in Windows.

    Haven't tried it with version 2.0, but that is due to me moving to OS X and not bothering to boot up the Windows laptop to give it a shot...

  6. RTFA? by eargang · · Score: 4, Informative

    Or you could read the F.A.

    "Improved Abstraction — We've eliminated almost all direct SQL queries from the code and moved them to functions and classes that make the entire program more consistent."

    granted, no clue why they didn't eliminate all direct queries alltogether ("almost?" what you do you mean, "almost"?) but it's a damn good start towards db independence. a basic blog engine shouldn't be using any non-standard SQL calls anyway so support for Postgres should be easy at this point.

    emphasis on should, though. The glass is half empty in my world.