- Envato Staff
- Reviewer
- Community Moderator
- Venezuela
- Has been a member for 4-5 years
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Microlancer Beta Tester
- Sold between 10 000 and 50 000 dollars
- Exclusive Author
Hey guys I found this article about WordPress 3.1 common problems, is worth the read – http://sillybean.net/2011/02/common-problems-in-wordpress-3-1/
For example: You might need to update your register_post_type() call because the entire capabilities array changed in WP3 .1 – http://codex.wordpress.org/Function_Reference/register_post_type#Arguments
I had also a few issues with the WordPress Importer plugin but I solved it by creating the upload/{current_year}/{current_month} folders and giving the proper permission. I had to do this twice locally and in my server.
--- If you find a bug please report it here so everyone can see how to fix it.
- Sold between 250 000 and 1 000 000 dollars
- Exclusive Author
- Interviewed on the Envato Notes blog
- Author was Featured
- Item was Featured
- Beta Tester
- Author had a File in an Envato Bundle
- Author had a Free File of the Month
Mmm, the register_post_type args array hasn’t changed since 2.9… the only new argument is has_archive that comes with the 3.1, but I don’t see any difference…
Don’t know man, i tested our theme in 3.1, no problems found.
Change that “You need to update…” to “You might need to update…” 
- Envato Staff
- Reviewer
- Community Moderator
- Venezuela
- Has been a member for 4-5 years
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Microlancer Beta Tester
- Sold between 10 000 and 50 000 dollars
- Exclusive Author
ParkerAndKent said
Mmm, the register_post_type args array hasn’t changed since 2.9… the only new argument is has_archive that comes with the 3.1, but I don’t see any difference…
@ParkerAndKent The capabilities array
@jvanoel Same for me, only that tiny issue but nothing to worry 
- Sold between 250 000 and 1 000 000 dollars
- Exclusive Author
- Interviewed on the Envato Notes blog
- Author was Featured
- Item was Featured
- Beta Tester
- Author had a File in an Envato Bundle
- Author had a Free File of the Month
Ivor said
ParkerAndKent said
Mmm, the register_post_type args array hasn’t changed since 2.9… the only new argument is has_archive that comes with the 3.1, but I don’t see any difference…@ParkerAndKent The capabilities array
@jvanoel Same for me, only that tiny issue but nothing to worry![]()
oh ok, the capabilities… I usually leave the default ones… so I don’t need to update 
LOL the most confusing change for me was when i saw that the custom fields box is removed ???
After asking Mr. Google few questions, i found out that they have just hidden that box and that it can be returned by clicking “screen options” in the top right corner, while writing posts 
- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 50 and 99 items
- Exclusive Author
- Has been a member for 4-5 years
- Item was Featured
- Referred between 500 and 999 users
- Sold between 250 000 and 1 000 000 dollars
One thing to note, also. A lot of people use prettyPhoto in their themes, and it appears the new version of jQuery 1.4.4 (which is updated in WordPress 3.1) is not compatible with older versions of prettyPhoto. So, if you slapped prettyPhoto in your theme a long time ago before prettyPhoto 3.0, you might be having problems with lightboxes coming up in WordPress 3.1
... Not sure if I’m 100% right on that, but doesn’t hurt to give that a check on your themes.
- Sold between 250 000 and 1 000 000 dollars
- Exclusive Author
- Interviewed on the Envato Notes blog
- Author was Featured
- Item was Featured
- Beta Tester
- Author had a File in an Envato Bundle
- Author had a Free File of the Month
ThemeBlvd said
One thing to note, also. A lot of people use prettyPhoto in their themes, and it appears the new version of jQuery 1.4.4 (which is updated in WordPress 3.1) is not compatible with older versions of prettyPhoto. So, if you slapped prettyPhoto in your theme a long time ago before prettyPhoto 3.0, you might be having problems with lightboxes coming up in WordPress 3.1 ... Not sure if I’m 100% right on that, but doesn’t hurt to give that a check on your themes.
I confirm this, the new jquery version is broking all the themes of the world 
It’s a good idea to always deregister the jquery version that comes with wp and register the one tested and used with the theme.
- Envato Staff
- Reviewer
- Community Moderator
- Venezuela
- Has been a member for 4-5 years
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Microlancer Beta Tester
- Sold between 10 000 and 50 000 dollars
- Exclusive Author
ParkerAndKent said
It’s a good idea to always deregister the jquery version that comes with wp and register the one tested and used with the theme.
+1
- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 50 and 99 items
- Exclusive Author
- Has been a member for 4-5 years
- Item was Featured
- Referred between 500 and 999 users
- Sold between 250 000 and 1 000 000 dollars
@ivor
Do you know when TF is going to be adding in the option for us to designate if our themes are compatible with 3.1? I just went in to edit a theme, and it looks like it still only goes up to 3.0. ( I know WP 3 .1 was just posted, but I have emails and comments pouring in… )
