HomeWordPress.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).
Other changes:
- 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:
(P.S.: Download number was reset after server move)
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.
February 12th, 2011 at 5:31 pm
I agree Bahia.
January 27th, 2011 at 4:32 pm
first has great problems with installation, but now its all o.k. Thank you very much and a lot ogf greetings from germany
January 25th, 2011 at 8:35 pm
hi, i really like the idea of rotating header images, but i’m holding off till some of these bugs are taken care of. i hope someone will comment when that happens.
January 22nd, 2011 at 9:17 am
We are using the Atahualpa theme on a private website. Somehow an unwanted dating website link has been placed at the bottom of each page. I’m assuming that one of the plugins we use installed this. Is there any way to figure out which plugin is causing this, short of disabling them one by one?
January 16th, 2011 at 6:25 am
Still having the same problem with version 3.6.1 which gives a server error also after using FTP 8-(
January 13th, 2011 at 1:25 pm
I avoid this update (3.6.1) : result => a beautfiful blank page (same with release 3.6)
January 12th, 2011 at 7:40 pm
@Dave: My fix above also solves that issue.
January 11th, 2011 at 2:43 pm
I just tried 3.6.1 and no further ahead with this version going over 3.4
January 9th, 2011 at 1:24 pm
@Peter Luit: This is probably due to the fact that with WP3.0 the multisite detection code must change.
There is a thread about the issue here: http://forum.bytesforall.com/showthread.php?t=8668&highlight=multisite (it is a Gold support forum).
The key statement is this:
======================================
I helped myself now and manually replaced all occurrences of the String
file_exists(ABSPATH.”/wpmu-settings.php”)
in any atahualpa file with this:
is_multisite()
Now things run smoothly again.
======================================
Yes, I would really like to see this fix in the new version!
January 9th, 2011 at 3:33 am
For multisite, in order to have separate headers I had to have separate theme installations. It would be best if there was an option to choose a single header in addition to rotation.
January 8th, 2011 at 6:37 pm
Hi,
I’d avoid this update for the moment. I tried it today and got the blank grey screen (the html source for the page stops dead halfway through the css definition for table#logoarea (it has the width and border-spacing lines, but nothing beyond and no closing brace).
I got exactly the same error having done a completely fresh install of WordPress with no widgets or customisation of Atahualpa.
I’m happy to pass any debugging info back if you can’t reproduce this, otherwise good luck tracking it down.
Thanks for the update – I know it’s a huge amount of work doing this kind of stuff and I appreciate that. Site is fixed now as I had a backup of the /wp-content/themes/atahualpa directory to hand.
P
January 8th, 2011 at 2:22 am
Here is my problem with WP 3.0.4 it won’t install at all.
Error says:
Warning: copy(/home/******/public_html/wp-content/themes/atahualpa/jsoriginal.php) [function.copy]: failed to open stream: Permission denied in /home/*******/public_html/wp-admin/includes/class-wp-filesystem-direct.php on line 200
Warning: copy(/home/******/public_html/wp-content/themes/atahualpa/jsoriginal.php) [function.copy]: failed to open stream: Permission denied in /home/*******/public_html/wp-admin/includes/class-wp-filesystem-direct.php on line 200
Could not copy file. /home/*******/public_html/wp-content/themes/atahualpa/jsoriginal.php
January 7th, 2011 at 8:55 pm
Should have checked here before updating! My 3.5.3 to 3.6 update gives lots of errors like this below (will try to roll back to 3.5.3): [Using WP 3.0.4]
Warning: include(): Failed opening ‘bfa://html_inserts_body_top’ for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in /www/[#######]/public_html/wp-content/themes/atahualpa/header.php on line 36
Warning: include(): Failed opening ‘bfa://configure_header’ for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in /www/[#######]/public_html/wp-content/themes/atahualpa/header.php on line 53
Warning: include(): Failed opening ‘bfa://content_above_loop’ for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in /www/[#######]/public_html/wp-content/themes/atahualpa/index.php on line 11
Warning: include(): Failed opening ‘bfa://content_inside_loop’ for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in /www/[#######]/public_html/wp-content/themes/atahualpa/index.php on line 15
January 7th, 2011 at 11:02 am
@J.D. I have the same problem (the icons for “post feed” “comment feed” and “email” no longer appear…): the theme looks for the icons in the folder “/images/” in the root (not in “wp-content/themes/atahualpa/images”). I noticed it when using Web Developer for Chrome to check. Uploading the needed images there, it works, but I suppose there is a bug somewhere in the theme.
January 7th, 2011 at 5:56 am
[…] document.getElementById(“fb-root”).appendChild(e); }()); BytesForAll has announced the release of Atahualpa 3.6, a version that apparently does not bring many new features, just some improvements and adjustments […]
January 6th, 2011 at 12:15 pm
I have updated to 3.6. Use Bytes for all SEO options is no longer working. All meta tags, e.g. keywords and descriptions are no longer available on my site using 3.6. If I downgrade back to 3.5.3, meta tags are available.
January 6th, 2011 at 9:56 am
Completely nothing after update. The admin still works but my test site (thanks to myself) produces completely empty files after an upgrade to 3.6.
Please don’t trust the update just yet.
January 5th, 2011 at 8:45 pm
Is there a reason why the menu options on the WP dashboard don’t work anymore? It appears like the page order and exclusions must now be manually controlled by changing the page order and on the atahualpa dashboard.
January 5th, 2011 at 5:49 pm
For some reason the theme update erased my header image and logo from my main directories, but I re-uploaded these and there’s no problem.
My only issue now is that the icons for “post feed” “comment feed” and “email” no longer appear…even though I have selected “yes” for all three and hit “save.”
January 5th, 2011 at 5:20 pm
I just tried updating to 3.6 over 3.4.9 on WordPress 3.0.4 doesn’t work and can’t get a preview either.
Loaded it onto a brand new site and same thing it doesn’t preview and a blank page on activation.
January 5th, 2011 at 4:34 pm
I tried 3.6 on two installs (one fresh and one upgrade) into WP 3.0.4 and it does not work. All I get is a blank screen. 🙁
January 5th, 2011 at 4:12 pm
Unfortunately, this update introduces many markup errors. My blog now has 14 errors and triggers a bunch more warnings with the W3’s online validator. No such problems existed for me with Atahualpa 3.53.
January 5th, 2011 at 1:18 pm
I love this version. Thank so much.
January 5th, 2011 at 12:46 pm
I tried it and my entire website is gray… Tried to delete it and re-install it and it did the same thing…
This is sad because i really like this theme…
“You are using WordPress 3.0.4.”
January 5th, 2011 at 12:34 pm
Only Excerpts doesn’t work. Excerpt length set to 60
January 5th, 2011 at 12:14 pm
Is my observation right that in a multisite setting the rotating header images are the same on every site? I don’t see what has been explained in the settings, like:
– /wp-content/themes/atahualpa/images/header/
– site2/wp-content/themes/atahualpa/images/header/
I cannot imagine that for a multisite setup two ATA installations are needed.
Can anyone explain this?
January 5th, 2011 at 10:08 am
@Patrick: I have seen simular thing with other Themes as well. Sometimes it look like this is depending on the way you install/updates your theme. A direct upload form the dashboard or via FTP. Try both to see if there is any difference.
I uploaded 3.6 in WP3.1RC2, which worked fine via the dashboard. Hope this will help.
January 5th, 2011 at 4:43 am
Hi, version 3.6 won´t be able to make a preview in WP3.0.4. It gives a server error. I didn´t try activating it. Any help?
January 5th, 2011 at 2:22 am
Besides internal technical improvements, one new feature has been added in the header image display. Now ‘random’ can be selected to rotate header images in random order.