Atahualpa 3.3.1 is available here http://wordpress.bytesforall.com/?p=69

Changelog 3.3 -> 3.3.1

• DONE: Auto image resizing didn't work anymore for the image height
• DONE: Post titles were linked to the wrong Permalink URLs
• DONE: The font-weight of widget list items could not be changed

Plus another bug was found. Either update to 3.3.2 at http://wordpress.bytesforall.com/ (only 1 file changed: header.php)

or apply this patch http://forum.bytesforall.com/showthread.php?p=3922

Applying the patch is sufficient if you already have 3.3.1. Uploading the new header.php from 3.3.2 would work, too

Thanks for rolling out a fix so quickly. I realize how complex this theme is. It would be nearly impossible to not have a few bugs slip through. I really appreciate the quality of this theme and the level of support you provide.

I do have a suggestion for a future release. I want to have headings at the top of category and archive pages. I just edit the code and add them, but it would be better if I didn't have to edit the code.

So, you could add suport for this by creating an option to turn on archive headings.

Now that we can put PHP code in the theme settings, a more flexible solution might be to add a new div at the top of multi post pages where we could insert code. This would be basically like the kicker, but would appear only once at the top of multi-post pages.

Thanks,
Brad

I'll do something like that in the next version. There are definitely areas where the theme isn't flexible enough. Also, manual file edits shouldn't be required anymore at some point.

I'm just now updating from 3.2 to 3.31. This will be my first ever theme update -- with Atahualpa, or any other theme for that matter.

I understand that all the options I've set in "Options" are stored in the database and will be "moved automatically" into 3.31.

But, the changes I've made in index.php, header,php, etc. are another matter.

What is the best way to go through and re-do those changes where needed? Looking at the /atahualpa directory on the server I can see that all the files have a "last modified date" of 2/7/2009 except for header.php, footer.php, index.php and functions.php which have been modified more recently.

Is there a systematic, sure-fire approach to this process that guarantees I won't miss a change I've made?

I've tried to be consistent about leaving comments in files where I've made changes. but my knees are still shaking.

I suggest that you upload the new version as /atahualpa331/ and run both the old and the new version at the same time. That way you can always go back to the previous version while carrying over your file edits.

You'd have to find all your file edits files in the old version and re-apply them on the new version.

I am going to add "hooks" in the next versions. With hooks, you'd have all your custom code in a single file, instead of many little edits spread over multiple files.

Originally Posted by Flynn

I suggest that you upload the new version as /atahualpa331/ and run both the old and the new version at the same time. That way you can always go back to the previous version while carrying over your file edits. ...<snip>..

I'm not sure I understand how you mean this. WP won't let me effectively have two themes installed at the same time -- will it? Even IF they are two versions of the same theme.

Hi Flynn,

having upgraded to 3.3.1 I noticed the following things around localization:

1. the date format is no longer picked up (no entry for it in the .pot file although still in the php-files - shows up again when building a new template). This has been the case since 3.2:

#: comments-paged.php:82
#: comments-paged.php:118
#: legacy.comments.php:80
#: legacy.comments.php:121
#: functions/bfa_comment_walker.php:114
msgid "F jS, Y"
msgstr ""

2. The following strings don't appear any longer, not even in the php-files:
Register
Site Admin
Login
Logout

Why? Now there is e.g. no "Register" link now even if enabled in the dashboard.

Best regards,
Uvius