WordPress.org has changed the submission process for themes and also added quite a list of new requirements. Also, themes aren’t reviewed by Automattic employees anymore but by volunteers, i.e. theme and plugin authors.
This has various implications, one being that providing backwards compatibility with older WP versions has become an impossible task because the sheer existence of some older functions (pre WP3) will trigger an alert of the automated submission script at WordPress.org and the theme will be denied automatically.
So from now on Atahualpa will be ready for the current and the past WP version, but not for older WP versions. WordPress clearly does not want theme authors to provide too much backwards compatibility and rather see people upgrading to the new WP version all the time.
Consequently this 3.6 version has some old code removed and will very likely break with anything older than WP 3.0! So don’t use Atahualpa 3.6 if your WP version is older than 3.0!
One rather big change in 3.6 is that the PHP eval function that was used for custom code inserts (all the text areas in the Atahualpa admin where you can put PHP code) is now replaced by PHP stream wrappers. (“Eval” is also not allowed anymore).
- fixed many PHP notices
- replaced many deprecated WordPress functions with their new equivalents
- dozens of little changes requested by the new WordPress.org submission script, and by reviewers
Right now 3.6 is still in the queue3.6 is now available at WordPress.org but you can also download it here:
Check out the BytesForAll Forum to discuss Atahualpa with other users
ADDED Jan 6 2011: A new version will follow within 2 weeks max to fix the issues posted below in the comments, and on the forum. There were so many (like 50+) changes in this version due to the new WordPress.org requirements. Now that these changes and fixes are done I can finally focus on user issues again.
ADDED Jan 8 2011: Please see http://forum.bytesforall.com/showthread.php?t=12048 for a fix for issues related to favicons and CSS.