WordPress 3.1 is finally out! With regards to my plugins compatibility with WordPress 3.1, I have not had the chance to test it it. I will be doing it soon =)
The long-awaited fourteenth release of WordPress is now available. WordPress 3.1 “Django” is named in honor of the jazz guitarist Django Reinhardt. Version 3.1 is available for download, or you can update from within your dashboard.
This release features a lightning fast redesigned linking workflow which makes it easy to link to your existing posts and pages, an admin bar so you’re never more than a click away from your most-used dashboard pages, a streamlined writing interface that hides many of the seldom-used panels by default to create a simpler and less intimidating writing experience for new bloggers (visit Screen Options in the top right to get old panels back), and a refreshed blue admin scheme available for selection under your personal options.
There’s a bucket of candy for developers as well, including our new Post Formats support which makes it easy for themes to create portable tumblelogs with different styling for different types of posts, new CMS capabilities like archive pages for custom content types, a new Network Admin, an overhaul of the import and export system, and the ability to perform advanced taxonomy and custom fields queries.
With the 3.1 release, WordPress is more of a CMS than ever before. The only limit to what you can build is your imagination.
(No video yet for 3.1, we’re going to add it later.)
By the Numbers
There were over two thousand commits to the codebase in the 3.1 cycle! For a more comprehensive look at everything that has improved in 3.1, check out 3.1’s Codex page or the more than 820 closed issues in Trac.
Now is the time to drop by our development channels if you are interested in being involved with 3.2, as the agenda will be under discussion shortly. We’re hoping to get the 3.2 release out in a shorter development cycle (3.1 took too long) and include some fun improvements around plugins and the speed of the admin. (Don’t worry, we’re still planning on using PHP.)
We’re All in This Together
WordPress is the result of the combined effort of people from all over the world united with a common goal: to make the best darn web software for publishing your story on the web and sharing it with the world. There are more than 180 people who helped out with development during the 3.1 cycle
Download: WordPress 3.1
(332 votes, average: 3.95 out of 5)
Upgraded yesterday to 3.1.1 and just discovered that the Polls plugin is broken. xD
When I click the “View Results” button, nothing happens.
Although I do have your other plugins installed, i didn’t have the chance to properly test them. You can check the Poll bug yourself by going to my weblog.
See ya.
Nothing to do with the upgrade, your file is not even there http://pheroes.net/wp-content/plugins/wp-polls/wp-polls.php
Ensure that it is chmod to 644
Sure its there. @@
Its probably chmod. I also had problems with some other directorys since the upgrade.
WP must had reset everything. =3
Thanks anyway for the hint. \o
Ok, what i’ve done so far:
– Deactivated all plugins, except WP-Polls;
– Returned WordPress to default template;
– Checked if and were in the right place;
– Restored all poll templates to default;
– chmod all folders inside wp-content to 755 and all files to 644;
– Made sure wp-polls.php existed and all files were in the right place;
Checked all the above a dozen times, and still WP-Polls doesnt work on WP 3.1.1. Also I get the same problem with WP-PostRatings. I would really appreciate any help.
Note: I’ve returned to Mystique template and temporarily deactivated the polls, but if you need any information or the polls back up for testing, just mention it.
Btw, sorry if im posting on the wrong place, and thanks in advance for any help.
Check if there is any .htaccess which is normally hidden? Since you said the files is there, some permissions must be messing around preventing the script from being access vai the url
I uploaded empty .htaccess files to all folders beginning with wp-content and forth and it made no difference, then i deleted them. Also wp-polls.php was viewable (error 500) when I deleted the main .htaccess file, and re-uploading it made WordPress once again thinks the file doesnt exist.
I also deleted the plugin and reinstalled with no success in eliminating the bug.
I checked if the encoding could be causing some incompability, but I couldnt get it to work with any of them.
Well, thanks of all the time spent but I give up. u.u
See ya. \o
I don’t think is a char encoding issue, more like a permission issue or a conflict with plugin/theme.
As you mentioned, the file is there, so something in WP or your theme/plugin or just server permission of the folder/file is filtering the request before it actually hits the wp-polls.php.