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
Yeah, it would be great if PHP had some PostgreSQL functions.
there's more than one way to do me.
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 believe that most hosting companies don't support PostgreSQL, but rather support MySQL on average (unless you have your own server). So as it would not be that hard, which they could most certainly add, they probably have just not got around to it. Just my opinion.
Just a side note, MySQL 5 is definately a RBDM
-- Brought to you by Carl's JR
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?
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!
Does MySQL 5 support transactions AND full text searches on the same tables?
--jeffk++
ipv6 is my vpn
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"
Hahahahaha! I get it. It's because most OS software developers Just Don't Get It when it comes to databases. They read a text file that teaches them "SELECT * FROM SomeTable;" and suddenly they're DBAs, except they're not. Fortunately for them MySQL sucks in such a fashion as to give them a false feeling of confidence that they're shit is going to work. As long as they actually don't do anything mission critical they're fine.
LAMP is LAMP for the same reason people drink wine out of a box, sleep on 100 TC sheets, and run Linux: because they are good enough even though they miss the boat in a number of fundamental ways.
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.
Well, as I said... feel free to fork Wordpress, or submit a patch. Noone is denying you that right. And after all, most open source SW is made to fit ones need. Including everything I make. I'm kinda selfish. I make modifications to suit myself, but I share them. Most contributors do open source because it suits them.
Assembling etherkillers for fun an profit
I had been using the ChenPress plugin for WYSIWIG editing and I found that it had some issues 2.0 solves them. I also like the fact that you can increase the size of the text editing window. In the past when I was writing a post, it seemed that the window was way too small.
http://www.stockmarketgarden.com/
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.
Nothing wrong with The L and the A but MySQL+PHP (which run fine on windows and IIS, by the way) is the visual basic of the early 21st century. A shitty, limited system for people who don't really know how to program. These LAMP fascists are just trying to shoehorn everyone into using their crap by making it seem like they're part of some integrated system when really the last two components are cheap 'good enough' hacks for people who don't know what they're doing.
And really, there is zero difference between LAMP and WAMP, I've never had trouble getting open source PHP/MySQL programs to run on windows servers. There's nothing Linux or Apache specific at all.
autopr0n is like, down and stuff.
I've been meaning to check out ruby on rails at some point.
autopr0n is like, down and stuff.
sigs are for fools and trolls. no signature is *always* appropriate. you should turn them off in your preferences.
There are no trails. There are no trees out here.
B> I recently upgraded the software linked to in my sig to support PostgreSQL in addition to MySQL. Non-trivial, but the afternoon was worth it. Granted, it's a smaller application than Wordpress, but in doing so, I've created a framework I can use in any PHP application, and add support for additional RDBMSs as well. A worthwhile exercise.
You are not the customer.
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
Yeah, it's too bad PHP doesn't support some sort of database abstraction layer. ;-)
Realistically, if you design an application from the start with even just a little bit of, well. . . design, and consideration for portability and future growth, database independance is not very difficult.
Unfortunately, it's been my experience that most people don't really think beyond the next few hours when they're coding, which means that making things better later on is a huge chore.
Topher
While I don't know about Wordpress, I'm a fairly active Textpattern user and the reason for the lack of Postgres support in the past was always that Textpattern's search function relies on full-text indexing, something Postgres doesn't quite do natively (it requires either the fulltextindex or tsearch module, neither of which are built by default). There's now a development branch of Textpattern with Postgres support, though. I haven't looked at the code, but it may be that they're working around it somehow.
Typo's a bit of a beast, though, in most shared hosting environments. And there was that nasty memory leak in Rails it exposed a while back...
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
Hahahahaha! I get it. It's because most OS software developers Just Don't Get It when it comes to databases. They read a text file that teaches them "SELECT * FROM SomeTable;" and suddenly they're DBAs, except they're not. Fortunately for them MySQL sucks in such a fashion as to give them a false feeling of confidence that they're shit is going to work. As long as they actually don't do anything mission critical they're fine.
And you must be the ultimate authority on what is "mission critical" for who? I guess you've reviewed all applications on this planet (especially company internal ones) that use MySQL, so you'd know.
Ebay uses some serious "mission critical" database server, yet their site is shit slow most of the time. I guess those "mission critical" database servers are not that good either. I reckon Ebay should move to Postgres - it's silver bullet solution for all database needs. It also cooks and washes dishes.
Everyone uses what suits them best. Some people use Windows, some people use Postgres, some people use MySQL, and some use flat-text files.
I've seen quite few MISSION CRITICAL applications in banks that still use flat-text files. Do you want me to give them your contact details, so that you can "open their eyes"? I'm sure they need your expert advice...
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.
Use Textile. It's intuitive, simple and quick.
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'
Why didn't you submit it to Slashdot?
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
Funny, I was impressed by the WYSIWYG editor the first time I see it and install its beta on my localhost. Now that I've use it several times on my localhsot, and even tried to mimick the same behaviour by installing tinyMCE plugin for my wp 1.5.x What should you do if you want to tweak the HTML in your editor? Of course, switch to HTML view. And then you'll just edit the HTML rite? Wrong! You have to parse your HTML spaghetti (it's like a long line of HTML code without any line break) yourself, and then locating the point in which you want to edit or insert your own markup. What about "code" formatting? I cannot recall how bad it was, but I prefer the old add-manual-code-tag method. I use that method with geshi, disabled auto tag completion (closing), thus I can get a fancy colorful code markup. Still, with a lil bit deficiency: double quote and single quote are translated into fancy one. Til now, I still use 1.5.x. I'm still looking for more reason to move to 2.x, beside those ajax stuves.
Can it use SQLite as a backend? Running MySQL or PostgreSQL is overkill and unwarranted for these kinds of applications.
I hate to reply to this because it looks like a troll, but oh well.
If you like Postgress so well, why don't you add the functionality into Wordpress? I personally don't see the need for the arguement of PostgreSQL vs MySQL because I've honestly never threw anything at MySQL that it couldn't handle. Whats the old addage? If it isn't broke, don't fix it....
Now before everyone jumps on me, I realize that PostgreSQL can make my life much easier in some respects. But c'mon people - if you want it, code it yourself. I've hand coded functionality into Mambo & Wordpress. I've also fixed other peoples problems in both as well. Heck, one time (at band camp...) I hand coded a CMS - that wasn't fun at all, but I couldn't find something that would work the way I wanted.
Stop yelling at the masses that create something for free and do it yourself.
Well said.
And there was that nasty memory leak in Rails it exposed a while back...
As I understand it this bug in Rails was fixed and no longer affects Typo - since you bring it up I suspect you know more about it than I do? Please clarify.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
large, non-technical IT companies have the absolute worst programmers. I'm sure most of those companies have huge archives of VB code too. Really, you make my point.
autopr0n is like, down and stuff.
The leak was in Rails 0.14.1, and it was patched in Rails 1.0RC3; a write-up and links to full details are here. Typo was, so far as I know, the only Rails app which ever managed to trigger it. And I'd say that's because, well, Typo's a bit of a beast. But then I don't particularly care for Rails for any sort of content-management; its application orientation means that for "CMS-style" tasks like blogging you have to bring in all sorts of components (like login generators and admin interfaces) which add overhead. If you're going to do content-management with a framework, use something like a href="http://www.djangoproject.com/">Django which is far better suited to that task (where Rails was extracted from a web application -- Basecamp -- Django was extracted from a newspaper site).
It's not about supporting Postgressql. They should have used an existing DB (access) abstraction. ADOdb is very nice and still fast. Starting with such an abstraction helps supporting a different database. Instead they've written something with all the bells and whistle - there are even benchmark methods in their DB class.
b4n