Well, we have just finished testing with 3.2 and except for a little custom widget styling in the backend where all good for this amazing looking version
.
Plugins and Themes are 3.2 ready 
The only problem I have found so far related to an outdated version of Nivo Slider.
I have tested WordPress 3.2 compatibility for my “Capstan Business Premium – WordPress Theme” i have not fond any issue at all at the movement.
100% Compatible
You may see it in action [link removed ~]
My themes are 100% compatible also, tested them myself and got confirmation from clients already… Regards
umm… you do know that you could have tested all of your themes with WP 3 .2 prior to it’s public release.
Anybody can download the latest development version and it’s something that is encourages by WordPress.
A developer should always be a step ahead of his customers.
christopherjon said
umm… you do know that you could have tested all of your themes with WP 3 .2 prior to it’s public release.Anybody can download the latest development version and it’s something that is encourages by WordPress.
A developer should always be a step ahead of his customers.
Yeah, your right. But testing on a RC isn’t the way it only should be. You can test the most of it but everything we have build has to be checked on wp final releases since thing can change from RC ti final.
So that’s why we develop always on the latest version and do a final check after the final release is out.
- Author had a File in an Envato Bundle
- Author had a Free File of the Month
- Author was Featured
- Bought between 10 and 49 items
- Exclusive Author
- Germany
- Has been a member for 3-4 years
- Interviewed on the Envato Notes blog
- Item was Featured
Yep, everything 100% compatible here as well 
- Envato Staff
- Sold between 100 000 and 250 000 dollars
- Support Staff
- United States
- Author had a Free File of the Month
- Microlancer Beta Tester
- Beta Tester
- Interviewed on the Envato Notes blog
Everything working great except for one issue.
I was using a shortcode that used a DIV wrapped in an anchor tag. This is valid with HTML5 and worked fine in WP3 .1.
On upgrading, I found that WP 3 .2 tinymce was scrubbing all the anchor tags that didn’t comply to pre-HTML5 standards. So when the shortcode was being placed into the text editor via a tinymce button, it completely removed the entire anchor tag I was using around a div.
I ended up just rewriting the shortcode to comply.
