WordPress 2.7.1, a maintenance release, is out. If you are using WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements.
Some of the fixes and feature improvements include:
- Post and Page revisions do not respect time zone offset
- Invalid comment feeds
- XMLRPC returns category name instead of category description
- Theme preview fails when theme in subdirectory
- Tag cloud order priority
- Hierarchy issues with wp_list_categories
- Namespace missing in Atoms-Comments Feed
- Canonical redirect of feed URLs
- Contributor level users could delete all spam
- Allowing Word 2007 to retrieve categories
- “Selected” argument doesn’t work for “none” and “all” options in wp_dropdown_categories template tag
- Draft Saved current time doesn’t match timezone while editing
- IE7 bug fixed for approved and unapproved comments in All Comments list
- Multiple categories feeds repaired
- Empty feeds for MT imports
- Post drafts published in the past
Some additional security measures were taken in this release to make protect it from future vulnerabilities as part of the ongoing work by WordPress to make it as safe and secure as possible.
According to the WordPress Download Counter, WordPress 2.7 has been downloaded 1,872,184 times since December 10, 2008.
Site Search Tags: wordpress, wordpress 2.7, wordpress 2.7.1, wordpress version, wordpress released, wordpress update, wordpress upgrade, wordpress news
Subscribe 
Via Feedburner 
Subscribe by Email 
Visit
Copyright Lorelle VanFossen, the author of Blogging Tips, What Bloggers Won't Tell You About Blogging.
39 Comments
Lorelle,
the fact that the counter is at 1.8 million answers my question wether the counter gets a reset on ever 2.x or ever 2.x.x.
Anyways I have 3 main WP sites, #3 got the notice ONLY, the the other two got the notice sometime around 1am or so (I tend to be up late at night). I am guessing something from my installation pings (I think that’s the correct term?) a WordPress server to check on the most up-to-date version?
Let’s have fun with WordPress…..let’s see who can get a screenshot closest to 2 million mark but has to be minimum 2 million.
@Miroslav and WPDesktop: I only referenced the counter as that is the only official measurement. Yes, people download it once and then spread it across many blogs and there are also installers. The counter is always reset on major upgrades, not minor.
As for not getting the ping for alerting you to the upgrade, you might want to bring that to the developers’ attention. Since you got the 1 million, are you really going to try for 2 million, Miroslav? Cool.
Hi,
Actually download rate is much bigger then the current (1,872,184 times since December 10, 2008 ) because there are hundreds of ways to install WordPress i.e. about all webhosting companies have built-in one click install and many other tools so those installation hits doesn’t add to wordpress download counter.
Brilliant – all great software should have the ability to automatically update and mine worked a treat – chapeau. I don’t see it noted, but did they fix the post scheduling? Myself along with many others simply had messages ‘missed schedule’ or some such when we moved to 2.7…
@billn: Yes, there are links in this post to the Draft and scheduling, and in the trac, so it looks like drafts and scheduled posts have been fixed.
I wrote about WP 2.7.1 too. I love maintenance release, even thought 2.7 worded just fine.
I’ve been writing a Weblog on wordpress.com for over a year now and I come to see that the expansion and development of this system is growing enormously. Hi5 to WordPress, on it’s growth and development.
Cheers,
Eddie Gear
I’ll check this mant release later this week, as another user reported, 2.7 works just fine, but the features and security fixes are well worth the upgrade.
cheers.
With the build in upgrade function, it makes smooth and easy
Unfortunately, lots of people are having problems with the auto upgrade. Check your file permission, the list of compatible hosts on the WordPress Codex and the WP support forums if you are having problems.
Funny. I seemed to be unable to upgrade automatically and I have messed up with manual upgrade. Oh dear, I guess I will keep on playing with WordPress 2.7.1.
@Sarah: If you are on WordPress.com, you do not upgrade. WordPress.com will take care of it for you. If you are using the full version, then delete everything except the
wp-contentdirectory and manually upload the files with FTP, the “old” method of upgrading. Should take only a few minutes depending upon how fast your FTP access time is.Pity the upgrade does not turn off the auto correction in the editor ! This “feature” plays havoc with my HTML and is driving me berserk !
Sorry, forgot to mention it is for another self hosted blog on writingconsultation.com. It is totally down now. I messed with the whole thing. I guess I don’t understand the guidelines on wordpress.org about upgrading. Have to start all over now. Anyway, this is my first upgrade. Rather sad but I will learn from the mistakes. So, just delete everything except wp-content. What about index/.htaccess /wp-config? Ah.. scratching my head..
@Sarah: If you are upgrading from WordPress 2.7, leave the .htaccess and wp-config files. If you are upgrading from older versions, the .htaccess file can stay but the wp-config file should be upgraded to the new version as it has security improvements. Instructions are within the wp-config file on how to get the new access keys.
I should have been more specific. Delete everything that is a WordPress file, except your wp-content folder. The .htaccess file is used by WordPress but you may have customized it so don’t delete it as it isn’t a strictly WordPress file. Do not delete your images, files, or other non-WordPress items.
I know one thing about this release. It is just awesome. I don’t understand all the changes but I know one thing – I feel my dashboard faster and downloading pic using the flash is quicker than 2.7.
The auto upgrade works awesome. In less than 5 secs, my blogs already 2.7.1 !!! I love wordpress!!! Thank you whoever involved! 😀
I was unable to upgrade automatically and I had to proceed with the manual upgrade to go from WP 2.7 to 2.7.1, but I am on 2.7.1 now.
Oh yes… except the wp-content folder. I still remember the day I used shell to do all this upgrading. wrongly typed, done in a matter of seconds. Lucky I have local backup of everything.
Nice for this new version !
Thanks Lorelle. I finally got it right.
Hi there,
Tried the automatic update and got an error. Not sure if it’s in conflict with the automatic upgrade plugin or the server was unreachable. Probably the latter, no doubt we’ll sort it out. Thanks so much for the wonderful software. Can’t imagine using anything else. 😉
Jobe Roberts
If the error said something about PKUNZIP, it was the plugin for the automatic upgrade. Disable that plugin and you should be good to go.
Auto update doesn’t work, at least not for me. Sits there 5 minutes, then times out with a took too long to connect 404 type error and you don’t know if he did anything or not, or even worse: updated only partially. I’ll stick with manual update.
I’m sure that all of you having trouble with the automatic upgrade have been on the WordPress Support Forum to check for information and help on resolving the issue.
I had issues with the upgrade on some sites so documented the fixes. Hope this helps some of you:
Fatal error: Cannot redeclare pclziputilpathreduction – disable or better yet, remove the WPAU plugin.
Get the unpacking message that says your site has upgraded, but then it hangs – delete the .maintenance file 2.7.1 puts into your site root.
Some sites will need to temporarily adjust file permissions to allow WP to write the new files.
If you are using the Kubrick theme and have not renamed it, do so before the upgrade or your changes will be lost.
Those are all the issues I came across when updating several different sites. Not one site had all the issues and some had no issues at all. It’s a pretty painless upgrade for most people.
There are more details about these on my blog if you really need more info. Hope this helps.
Please post these tips on the appropriate section on the WordPress Support Forum, if you haven’t already, so others may get help and respond to these points. Thanks.
WordPress with all its updates is not a good blogging platform for anyone who runs multiple blogs, add on to that some issues with older blogs showing funny symbols in it every time a update is done makes it the worse blogging platform in the World. Numerous other issues make this blogging platform useless but who the hell has the time to go into all the mess ups done by this group of idiots. One update a year would be nice but will never happen.
The funny symbols are probably because you don’t have the character code set appropriately, or pasted content directly from a word processor, a no-no.
I’m sorry that you aren’t a fan of WordPress, but I’m thrilled that millions are upgrading painlessly, and have for several years, but now it’s much easier with the auto-upgrade feature. Hope the service you are running has your total support and that you are a part of their active support community.
WordPress is in fact the most complete, dynamic and original free blog system on the internet, i just hope they do never stop developing it.
I cannot figure out how to place a toggle capability between HTML and Visual in the author/admin side of COMMENTS section in my blog. I can toggle between HTML and Visual in the post sections and page sections, using WordPress tabs, but NOT the COMMENT section. It’s all HTML and no TABS at all. I’m lost. How do I fix this?
I’m confused. There is no HTML/Visual editor options in the WordPress Administration Comments Panel. There never has been. There are only a few HTML tags used in blog comments and they are shown in the Comment Editor. Other than links and the occasional bold, I rarely use anything HTML tags in blog post comments. Do you need more than that? Maybe there is a Plugin that will add the Visual Editor to comments, but I’ve not seen one.
I can’t get the automatic upgrade to work. Don’t know if I’m just not typing in the right information. I have looked on the WP site for help several times but just get frustrated all over again with how hard it is to find help with anything for WP. Tons of information there but like looking for a needle in a haystack every time.
As the instructions say, if you can’t get it to work, try uploading it manually. Be very specific and give all the information you can when posting to the Forum. Yes, there is tons of information, but if you are specific, you can usually find it.
If you do an automatic backup from within WordPress admin do a backup of your “content” folder… above all if, like me you have built your theme on the back of the “default” theme. Updating overwrites any file supplied in the basic WordPress distribution. Suffice to say that I was pleased that, for once, I had been thorough and backed up everything in as many ways as I could think of, so I could get back to where I should be !
Thanks Lorelle, I’ll keep to the forum for silly issues. The upgrade works great thanks!
@Jobe: There are no silly issues nor dumb questions – just not enough time in the day for me, while traveling, to answer all questions on WordPress. The WordPress Support Forums are awesome and often faster to respond that I am. 😀
I have a question regarding .htaccess file. Should I delete it or keep it while upgrading from 2.6 to 2.7.1?
Moreover, I upgraded a test blog to 2.7.1, and it does not have the .htaccess file at all. Is this supposed to be so?
Do you know if you have an .htaccess file or not? If you are using “pretty” permalinks (links with names not numbers) then you are and you just don’t know it. If you are upgrading, leave these things alone. You don’t have to do anything to them. But you can totally screw things up if you mess with your .htaccess file.
@billn: A plugin to fix Missed Schedules http://blog.5ubliminal.com/48 .
13 Trackbacks/Pingbacks
[…] WordPress 2.7.1 was released yesterday. This is a maintenance release that fixes some minor bugs and provides some preventive security measures. Lorelle lists the changes in this release in her post on the WordPress 2.7.1 release. […]
[…] realita bude asi jiná). Přehledný seznam nejdůležitějších opravených chyb naleznete např. zde, podrobný přehled potom v oficiálním repozitáři WordPressu. V oblasti češtiny se toho moc […]
[…] read more Share and Enjoy: […]
[…] maintenance probably involves upgrading to WordPress 2.7.1, server improvements, and possibly the reported news of some “cool gallery features” […]
[…] WordPress 2.7.1 has been released this week. Even though it is a maintenance release, I strongly suggest you to upgrade to it. If you are already using WordPress 2.7, you can take advantage of the automatic built-in upgrade of WordPress. If you are not, then you should immediately do that because your blog is becoming more vulnerable to some serious security threats day by day. With this addition 68 WordPress bugs were fixed. You can check the fixes and feature improvements at Lorelle On WordPress. […]
[…] Lorelle on WP: WordPress 2.7.1 Released – WordPress 2.7.1, a maintenance release, is out. If you are using WordPress 2.7, take advantage of the automatic built-in upgrade. If you are… […]
[…] WordPress 2.7.1 Released: WordPress 2.7.1, a maintenance release, is out. If you are using WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more details about the release on my blog. […]
WordPress 2.7.1 Available For Download…
I just received an email from Matt Mullenweg (creator of WordPress) that the update from 2.7.0 to 2.7.1 is available for download. This is big news for most blog authors who wait for a stable download after a major release and it came so quickly, almos…
[…] WordPress 2.7.1 Released: WordPress 2.7.1, a maintenance release, is out. If you are using WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more details about the release on my blog. […]
[…] WordPress 2.7.1 Released: WordPress 2.7.1, a maintenance release, is out. If you are using WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more details about the release on my blog. […]
[…] WordPress 2.7.1, a maintenance release, is out. If you are using WordPress 2.7, take advantage of the automatic built-in upgrade. If you are not, then consider upgrading to WordPress 2.7. Sixty-five files were modified with 68 bug and feature fixes and improvements, and I covered more details about the release on my blog. […]
[…] WordPress 2.7.1, uma manutenção libertação, está fora. Se você estiver usando o WordPress 2.7, tirar partido da built-in automático actualização. Se não estiver, então considerar fazer o upgrade para WordPress 2,7. Sessenta e cinco arquivos foram modificados com 68 bugs e funcionalidade correções e melhorias, e eu abrangidos mais detalhes sobre a libertação no meu blog. […]
[…] has updated it’s blogging platform to version 2.7.1. Touted as a maintenance release, reports indicate at least 68 bugs have been fixed in this release. Users can download the new code from […]