Customizable Themes for the WordPress CMS
Atahualpa 3.4.2 with 5 changes or fixes, see the changelog for 3.4.2 at http://forum.bytesforall.com/showthread.php?t=2355
Please ask questions at the FORUM
I finished this in the middle of the night as I wanted to release this as promised, for the sake of novelty.
This version might very well have issues beyond those mentioned in the thread listed above.
Atahualpa 3.4 had rather huge changes and also several bugs, mostly related to the new external CSS feature.
See the changelog for 3.4.1 at http://forum.bytesforall.com/showthread.php?t=2255
Please ask questions at the FORUM
The Javascript rotation for header images is missing in 3.4.1. Wait for 3.4.2 on Sudnay 7-12-2009 or apply this fix to 3.4.1: http://forum.bytesforall.com/showthread.php?p=996
post #27
This release has many improvements, see the changelog at http://forum.bytesforall.com/showthread.php?t=1581
Please ask questions at the FORUM
The first 143 (not just: 13) downloads had a little error ( see comment #1). Sorry, please download again, it is fixed now ( for real, tested).
Or, delete this line in functions.php:
include_once (TEMPLATEPATH . ‘/functions/JavaScriptPacker.phpp’);
Plus see if you have the them twice now: /atahualpa34/atahualpa34/. Delete the directory /atahualpa34/atahualpa34/. This also fixed in the download now
Some new features are:
Looks like wordpress.bytesforall.com is PR8 now? Nice
Please ask questions on the forum, see link at top of this page. Posting code is much easier there.
See changelog for 3.3.3: http://forum.bytesforall.com/showthread.php?t=1009
This release has many bug fixes and improvements. But there’s still some work to do so you might want to wait for the next release in a few weeks if you aren’t in a hurry and your current version works well for you.
Here is a preview: http://wp27.bytesforall.com/
The featured content gallery was somehow not working on my nginx server, I couldn’t figure it out today, but it worked on Apache & Atahualpa 3.3.3 & WP 2.7.1 (= config of the link above)
Edit: First 1-2 downloads had the Featured Content Gallery code still at the top of index.php, please download again or delete it from your downloaded index.php.
One more bug, a (potentially) relatively serious one was found (the <BODY> tag might be messed up under certain conditions). If you already installed 3.3.1 there’s no need to update again, it’s enough to apply the patch below
Changed files:
Several users asked: Will my settings be lost if I update. Answer:
3 bugs where found within hours and I had to release another version. The following files are changed since 3.3, it would be sufficient if you upload just these:
These were the bugs:
To update from an earlier Atahualpa version, I recommend this technique: Upload the new 3.3.1 version as i.e. /atahualpa331/. This way you can keep your existing version and change back in case something goes wrong. You’d be running both Atahualpa versions at the same time. The older version at /wp-content/themes/atahualpa/ or /wp-content/themes/atahualpa3/ or similar, and the new version at /wp-content/themes/atahualpa331/
Both versions would share the same Theme Option settings (as those are saved in the central database). But each theme version would have its own theme files. If you edited theme files in the older version, you’d have to apply these edits on the files of the new theme version as well. If you were using custom images, you’d have to copy or upload them to the new version’s directory as well.
After you uploaded the new theme version, activate it at Appearance -> Themes. To distinguish between 3.3.1 and i.e. 3.2: In 3.3.1, the theme description (which you see below the screenshot) says “Over 20 language files …” whereas 3.2 lists the languages as “DE, FR, JP …”. Or, simply hover over the Theme name and watch the browser’s status bar for
“…&template=atahualpa331&stylesheet=atahualpa331&….”
You can run more than 2 theme versions at the same time, too.
Since 3.3 the Atahualpa theme links to wordpress.bytesforall.com and another site of mine, themeframe.com, instead of www.bytesforall.com. Themeframe is a new theme (framework) I am working on, the themeframe.com domain will be updated within the next days. The credit links in the footer are also differently worded based on page type.
A jump from 3.2 to 3.3 because this version includes many bugfixes and improvements. See changelog
( 309 users downloaded version 3.3)
The Feedburner/Google issue is fixed, plus a few more minor bug fixes, a few more options, and 10 new languages thanks to:
See http://forum.bytesforall.com/showthread.php?t=109 for the changelog for version 3.2
I had to make one rather major change: The dynamic CSS is back from style.css.php to header.php & style.css, as it was in Atahualpa 2.x. This CSS location change makes 3.1.8 more browser safe than former 3.x versions because IE6 would sometimes (every 20th pageview or so) not load style.css.php.
If you added custom images via CSS, i.e. background images via url(images/myimage.gif) then you would have to change those to url(/wp-content/themes/atahualpa3/images/myimage.gif) unless you made those changes directly in style.css (then url(images/myimage.gif) would keep working).
See http://forum.bytesforall.com/showthread.php?t=78 for the changelog for version 3.1.8
Version 3.1.8 comes in 4 additional languages thanks to:
Test drive Atahualpa at http://wp262.bytesforall.com/ and see how it deals with big images and “unbreakable strings” when you resize the browser window.
Here http://wp27.bytesforall.com/2008/05/a-post-with-many-comments/ you can see the changes to the comment submit form, the toggle feature for “You can use these tags” and the styled CommentLuv inserts (“Flynns last post…”).
I will try to catch up with the open comments within the next days. I find it easier and more organized to answer questions at the BFA WordPress Forums so consider opening an account there.
I am leaving for 2 days in the mountains. I’ll answer the remaining comments and forum questions until Jan 2-3 and release a new Atahualpa version a few days later. Happy new year and see you in 2009…