Wordpress 2.7 ready on 10 November 2008
Most of us are Wordpress Junkies and it’s exciting news when we hear about new releases. Wordpress 2.7 will be ready for deployment on November 10, 2008 and it’s looking better than ever! There are some screen shots below and if you’re interested in more technical details, click here and read about it on the Wordpress Blog.
Looking impressive isn’t it?!
About the author:
Christopher is the founder of iMod - Most of his time is spent building websites and pushing the limits with Search Engine Optimization. You can follow him on Twitter @ChristopherM
Chris M has written: 4147 posts.
Oct 18th, 2008 at 11:32 am
Hi, Haven’t been here for some time. I had a look at Wordpress yesterday and I think it looks really good. Can only hope the insides will work as well. Wordpress really evolved from blog only software to a very good CMS piece of software. Pity that it still does not integrate with eg. SMF Coppermine etc.
Oct 18th, 2008 at 2:57 pm
Ye Rustig, where have you been hiding? ;)
I agree, the platform has evolved more than I think anyone realised that it would have. There’s been talk about it turning into a CMS for a long time, but it’s really reaching the bar now!
Oct 18th, 2008 at 5:12 pm
I’m running the latest bleeding edge version and the dashboard doesn’t look like that for me.
@Rustig: you can find info online about how to integrate SMF coppermine with WordPress.
Oct 18th, 2008 at 7:22 pm
2.7 is being released shortly, it’s 2.6.2 that we’re all running..
Oct 18th, 2008 at 7:25 pm
Richard: The new visuals are being applied to the 2.7 bleeding edge version bit by bit now that we’ve finished the design. You should see your wonky sized blue menus and modules replaced gradually with the pretty gray stuff Chris linked to; each nightly build will have a few more pieces until the live version looks just like the screenshots (which are photoshop comps).
Oct 18th, 2008 at 7:35 pm
Hi Jane, nice of you to pop around, really appreciate it!
We all look really forward to seeing the new vesion!
Oct 18th, 2008 at 9:10 pm
Who’s Jade, Chris? Your mom? Haha.
Oct 18th, 2008 at 9:14 pm
@Jane Wells: Thanks for the info. I was wondering if I was doing something wrong.
Chris, you’ll have to amend your blog post. WP 2.7 is not yet ready for deployment. You’re looking at photoshop pics, not the real deal.
Steady on there, chap. We’ve got a few more months to go. WP 2.7 is due out only in December. :)
Oct 18th, 2008 at 9:23 pm
Actually, Richard, 2.7 is due to launch November 10, 2008.
Oct 18th, 2008 at 9:23 pm
Jane works at Automattic doing user experience stuff for WordPress and related projects.
Will update shortly mate
Oct 18th, 2008 at 9:45 pm
Uh huh, Chris. Except you said JaDe, not JaNe.
@Jane: I see you’ve brought your release date forward then, not that there ever was any firm release date given, though.
Oct 18th, 2008 at 9:49 pm
Damn ‘n’ and ‘d’ are too close together on the keyboard! :P
Oct 18th, 2008 at 9:59 pm
uh huh, like Z and P. :)
Oct 18th, 2008 at 10:00 pm
Nah, those are far apart!
Oct 19th, 2008 at 12:12 am
Richard: Sorry to correct you again, but…. :)
Since 2.1, WordPress release dates have been set many months in advance, and dates for the next 3-4 releases are always displayed here: http://wordpress.org/about/roadmap/
Oct 19th, 2008 at 3:08 pm
@Jane Wells:
That’s the first time I’ve heard of that url, even though I regularly read the blog feeds that show up in my WP dashboard.
What I would like to know is when WordPress intends moving their code to PHP 5.2.x and rewriting the core code using classes?
Writing a new plugin for WordPress would then be a matter of extending an abstract plugin class. Ditto for themes. Instead of having a theme split into multiple files, you can contract that down to one php file containing the theme class (which extends an abstract theme class) and the css file.
A class based WordPress core code would be much simpler to maintain and extend. It would make WordPress a much more robust software package.
I’d also like to see them dump phpmailer, which has not been updated since 2002, and switch to using swiftmailer which is so much more advanced. I’ve used swiftmailer in a number of projects.
Better yet, they could write an abstract mail class that they extend which would allow one to graft in a new mail send class simply by replacing it with one’s own preferred mail abstract class.
Using classes for everything allows third party developers to hack the core code by replacing entire class files with their own.
It would be a huge advance forward for WordPress but it requires that it be recoded from scratch. A good way to get rid of detritus in your code.
Oct 21st, 2008 at 11:31 am
Actually I’ve found a blog which is completely object oriented and uses classes throughout, almost in exactly the manner I described above.
It’s called Habari.I remember hearing about this from Skippy, an erstwhile WordPress contributor who left the WP project after becoming disillusioned with how decisions were made.
Skippy was the original author of the wp_db_backup plugin which is so useful and popular that it was included in the WP 1.5 core installation and then subsequently removed when WP introduced an updated export function. Skippy was aggrieved by the decision to remove his plugin, especially when Matt Mullenweg’s less than useful “Hello Dolly” remains firmly ensconced in the core distribution.
Habari appears to have matured considerably recently, with a number of tech blogs writing about it recently, including ReadWriteWeb.
From reading the documentation, it seems much easier to extend via plugins and themes (both of which have classes that you extend) than WordPress. The habari core code supports either a single or multi site installation.
Unlike WordPress, Habari requires a more up to date installation of PHP (version 5 or higher) plus PDO must be available.
I’ve downloaded a copy and as soon as I get a chance, I’m going to install it on a test blog and see whether I prefer it over WP. If I do, I might switch all my blogs over to it.
I’ve gone through some of WordPress’ core code and found it not so intuitive because of the complete lack of class definitions. WordPress core code is comprised of functions liberally dispersed in a multitude of files. Extending WordPress is hampered by the lack of class structures. Plugins routinely break in new versions. Installing new plugins adds weight to one’s WP database which remains even after the plugin has been uninstalled. Because of the lack of a plugin class (which a developer extends to create a new plugin) to neatly control the activity of plugins, each WP plugin developer can do things which erode WP’s performance over time.
In my opinion, WordPress needs a complete rewrite using classes using PHP 5 or higher. They could make WP 2.x the last version to run on PHP 4 and remake WP 3.x to run on PHP 5 or higher. But I doubt they intend such a radical overhaul any time soon. PHP 4 support has already ceased and the last version (4.4.9) released.
Nov 2nd, 2008 at 5:31 am
Thank you for your website :-)
I made on photoshop backgrounds for youtube, myspace and even more
take care and thank you again!
Nov 2nd, 2008 at 11:14 am
My pleasure createmo :)