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."
If history is any indication, there will be a 2.0.1 release soon. I can wait ;)
"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.
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 ;)
Assembling etherkillers for fun an profit
Yes, true, but if it's not coded right, it can be a big pain to make it work with anything by mysql.
Creating a database independant application needs to be a consideration from the beginning, not an after thought.
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
I have been using Wordpress for almost two years, and every version update adds the features that I want to see. Version 2.0 looks like it already has several new features I never even thought of, like updating the control panel to be slicker and faster. These features will only serve to make Wordpress more valuable to my website. I look forward to installing it later. And, as some users have already pointed out, its open source and fully editable. So if you want to include support for your favorite DB, why don't you go out and do just that? Most webhosts already offer support for MySQL, so I don't see a problem offering this out-of-the-box solution with that backend.
It would be better if PHP had namespaces, then there wouldn't be a need for pq_* and mysql_* hacked function names.
Sadly, I'm stuck with version 1.0.1 because none of the rest will work when using Apache on Windows.
Get your Unix fortune now!
I upgraded to 2.0 when they first released it a few days ago, and am thoroughly impressed with it. Sure, I'd appreciate a spellchecker (fixed with a plugin), but nothing is perfect.
My one gripe with it, though, is it's new rich text editor - TinyMCE. For some reason it refuses to load and throws an error when attempting to do so. I've documented this on my blog.
I worked around this problem by, in the Admin area, going to Users, and deselecting the "Use the visual rich editor when writing" check box.
Its all fun and games until someone loses an eye... then its just fun.
... there are some issues that need to be worked out yet.
... wait until the first point release before deploying to important systems.
My recommendation with all new software releases
You might want to check out typo, an open source blog developed in Ruby on Rails. From the overview: "Supported databases: Mysql, Sqlite, and PostgreSQL"
WordPress MU is multi-user version of the famous WordPress blogging application. It is ideal for people wanting to offer a hosted version of WordPress
http://mu.wordpress.org/
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.
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. It's easy to make a system support multiple databases when starting from scratch. It can be more difficult if the code is already written and hacked up with 'mysqlisms'.
autopr0n is like, down and stuff.
They're referring to the WYSIWYG editor they've introduced for writing entries. I assume it requires support of the designMode attribute. There's a little more here, if you're interested.
Evidently even personal software deployed on single-user virtual hosts has to be enterprise-ready, scalable, mature, and ready for prime time, or something. I guess.
how to invest, a novice's guide
I think that means Safari and older versions of Opera don't support everything that's needed to do WYSIWYG.
I could be wrong though.
Why is it that WordPress has such a fanbase within the geek croud that it is mentioned every odd week on slashdot and simular forums but such powerfull well-built open source blogging tools like b2evolution or the awesome Pivot never get mentioned - even if they reach a major release? I've mostly heard programmers rave about WordPress but it doesn't appear to me as the cream of oss server side goodies, so what is it all about?
Anybody care to shed some light on this for me?
We suffer more in our imagination than in reality. - Seneca
Reiterating a comment I made above, and expanding a little:
Sometimes there is a good design reason for not supporting multiple backends; for example, Textpattern, my personal favorite for blogging/lightweight CMS solutions, has long been MySQL-only, not because of laziness or ignorance, but because Postgres doesn't have fulltext indexing by default (requires either of two contrib modules which don't get built in a standard Postgres install), and Textpattern uses fulltext indexing. There's a development branch of Textpattern which has experimental Postgres support (even though the trunk is MySQL-only, Textpattern does use abstraction in its database interface) which may or may not make that available for the future Textpattern 4.1, but I haven't had a chance to play with it, so I don't know how they're working around that problem.
And while I tend to be fairly DB-agnostic, I can understand that deliberate targeting of MySQL is a good way to keep an application like Wordpress manageable; since MySQL is by far the most common DB available for its target market (shared hosting customers), this pleases the most people while keeping the need to worry about inconsistencies between DBs to a minimum.
2.0 works in windows (on XAMPP), I tried it before moving my blog to it. It's quite nice, I love the "real" preview.
Send email from the afterlife! Write your e-will at Dead Man's Switch.
It just doesn't get any better than this. Well maybe New Years Rockin Eve with Ryan Seacrest.
'Same speed C but faster'