Wordpress Themes - WP Forum at BFA

Wordpress Themes - WP Forum at BFA (http://forum.bytesforall.com/index.php)
-   Old Version fixes and change logs (http://forum.bytesforall.com/forumdisplay.php?f=37)
-   -   Changelog 3.3 -> 3.3.1 (http://forum.bytesforall.com/showthread.php?t=1016)

Flynn Mar 30, 2009 10:52 AM

Changelog 3.3 -> 3.3.1
 
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

BradBrown Mar 30, 2009 11:49 AM

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

Flynn Mar 30, 2009 12:01 PM

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.

Shepherd Jim Mar 30, 2009 03:21 PM

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.

Flynn Mar 30, 2009 05:30 PM

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.

Uvius Mar 30, 2009 05:47 PM

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

Shepherd Jim Mar 30, 2009 05:54 PM

Quote:

Originally Posted by Flynn (Post 3845)
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.

strangelove Mar 30, 2009 07:01 PM

Jim,

I might be able to help here. I just uploaded the 3.3.1 update to my directory:
/wp-content/themes

where now there is two versions of Atahulapa:

/atahulapha3
/atahulapha331

Then under the admin panel APPEARANCE -- THEMES
I select either the new or the old version.

I immediately noticed that upon selected the new 331 version my custom header images disappeared -- more on this later,

EDIT: the obvious now struck me -- must move any custom header images from /atahulapha3/images/header to /atahulapha331/images/header

Dr. Strangelove
www.strangelove.com/blog
Watching YouTube

Ramoonus Mar 31, 2009 04:44 AM

Successfully updated from 3.2 to 3.3.1
yeeha :)

Joe Bonner Mar 31, 2009 09:48 AM

Quote:

Originally Posted by strangelove (Post 3863)
Jim,

I might be able to help here. I just uploaded the 3.3.1 update to my directory:
/wp-content/themes

where now there is two versions of Atahulapa:

/atahulapha3
/atahulapha331

Then under the admin panel APPEARANCE -- THEMES
I select either the new or the old version.

strangelove,

I tried this, but in the theme editor, they both have the same name (Atahulapha).

Do I need to edit something else inside the atahulapha331 directory?

I should add that it's obvious after clicking between the two which is which, but if there's a way to distinguish between the two, I'd be happy.

Thanks!

bcorrigan Mar 31, 2009 11:46 AM

Joe, they do have the same name, but they are ordered by name I believe. So Atahualpa 3.2 is before Atahualpa 3.3.1. Flynn, it would be useful if you could put a reference to the version in the info that shows up on the themes install page in WP Admin, like you did with version 2.21.
-Bill

paulae Mar 31, 2009 11:50 AM

I'm wondering if it would be OK to wait until the next release? I'm not having problems with the things fixed in this version, so, while I'm just about ready to launch our new site with the "old" version, I'd really rather not add any more stress right now!

So if I stay at 3.3, will I be able to upgrade at 3.3.2?

Shepherd Jim Mar 31, 2009 12:23 PM

I seem to be having a variation of the same problem: not knowing IF I've successfully updated to 3.31.

I created a new subdir hatchtown.com/wp/wp-content/themes/atahualpa331 alongside the existing hatchtown.com/wp/wp-content/themes/atahualpa

After unzipping, I uploaded all the 3.31 files into the new atahualpa331 directory.

On the WP Dashboard I see "Current Theme -- Atahualpa 3.2 by BFA WebDesign" and down in "Available Themes", along with "WordPress Classic" and "WordPress Default", I see just plain "Atahualpa" (note: no "331") .

If I click on the inactive Atahualpa I get a black-framed preview, I click on "Activate" and I return to the Dashboard view which reports "New Theme Activated -- Visit Site". BUT, it STILL says "Atahualpa 3.2" is active and plain "Atahualpa" is inactive.

Help! What's going on?

For the life of me I cannot see that anything's changed? I can see that I have new/different files in the /atahualpa331 subdirectory, but there's no indication they're being used.

Flynn Mar 31, 2009 01:37 PM

At Site Admin -> Appearance -> Themes

Hover over the title "Atahualpa" and watch the browser status bar for "...&template=atahualpa331&..." to distinguish between the Atahualpa versions


All times are GMT -6. The time now is 04:58 AM.

Powered by vBulletin® Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.