Originally Posted by lmilesw

Try turning off the fading effect Dona. I believe it currently conflicts with overlaying the blog title on the header image.

thanks - that did it! Let me know when they get a fix for that, I really liked the addition of the fading.

Dona

Originally Posted by lmilesw

Try turning off the fading effect Dona. I believe it currently conflicts with overlaying the blog title on the header image.

Hi Again,
Well, I spoke too soon : (
That did get the title/tag lines on top of the image, but now the images don't rotate!

Is there a way to get BOTH the title/tag lines on the image, and have rotating images?

This feature is working fine in the 3.4.9 (which i have on another site), but that version doesn't have the fade feature (which might to be causing the problem).

Any assistance would be appreciated. Also, I am a newbie, so if you know of a patch/fix, please let me know exactly where it goes.

Thanks!
Dona

Mine rotates fine with the overlay of title and tag line. Can you supply a url?

Since you said yours was working, I checked further and see that on Internet Explorer they do work (though the transitions are very chopping and not appealing).
But, it doesn't rotate on Firefox (which is where I was before).

Here is my URL: www.anewconsciousness.org (titles and tags are still in process until I figure all this out).

Does yours work on Firefox?

Thanks for your assistance!
Dona

Mine does work on Firefox. Maybe a plugin conflict?

Can you tell me where the two grey bars between the header and the rest of the page are created?

I'm sure it'll seem obvious when I'm told, but I can't seem to find them!



coop

Ah ha!

It's the background image referenced in the Body Style. I knew it would seem easy when I found it.

The Ah ha! moments are fun.

I'm trying 3.5.3 on a new install. I have other versions on other sites.

When first loaded, 3.5.3 looks good, as we've come to expect. But I just have to experiment, so I made some changes using the 'Configure Header Area' page.

When I decided to go back to default, clicking the 'Reset Settings' button did not take me back to the 3.5.3 default, but back what looks like is a default of a previous version.

Has this been reported before? Or have I done something unintended?

Is there an easy way to get back to the real 3.5.3 default short of reinstalling?

Thanks.

EDIT:
Of course, I think about more options right after posting. Clicking the 'Reset All Theme Options' does take me back to the start. So maybe the local restore is using different settings from the global restore? I dunno.

Because you can now import settings the reset doesn't work like it did. So if you want to get back to several different default settings here is the process.

• If you have make changes first to to ATO>Export/Import setting and Export & Download Atahualpa Settings File. This will save your current setting.
• Now you can click on "Upload & Import Atahualpa Settings File", navigate to the downloaded Atahualpa 3.5.3 folder and navigate the the Styles folder.
• In there are 4 "default" styles which you can import. Currently a fresh install I believe uses the advertisement style but I would try them all to see what they look like.
• Importing these styles adds CSS and sets many different settings in the Atahualpa Theme Options to give you various looks as a starting point.
• Again once you have made some changes and like what you see just export the settings file. Then you can tweak to your hearts content and still get back to where you were.

Thanks for the rapid reply. You have convinced me to look around more before I dive it on 3.5.3. Thing have changed!

Don't be afraid to dive into 3.5.3. It's the best version yet and works with WP 3.01. Just upload the atahualpa353 folder along with any previous versions folder and you can swap back and forth between versions. Or install on a test site and play around with it. That's what I am constantly doing to get familiar with all the details.

All the details I provide are just for clarity. Sometimes I overdue it with my attempt at clarity and make things more difficult.

Hello.

atahualpa.pot in new release has expired and after trying to translate I faced with broken references.
Where I can to get new .pot file ?

Thanks.

Originally Posted by Fader

Hello.

atahualpa.pot in new release has expired and after trying to translate I faced with broken references.
Where I can to get new .pot file ?

Thanks.

The .pot file is just in the zipfile.

In this zipfile old .pot file (09.07.2009) with incorrent references. I need actually .pot for 3.5.3

Some new msgid/msgstr values are lost also.

I would really appreciate if 3.5.3 were put to the wordpress.org theme directory asap. The class I teach is based on Atahualpa and the 3.4.9 doesn't work with the new WP 3.0 menu structure, and getting these folks to install something via FTP is pushing it.
Thanks

You don't have to install via FTP. Just download and install in WP using the upload button for theme installs.

everyman - from what I understand, a theme is submitted to WordPress and they review it and put it up when they are satisfied with it. So it is in WordPress's hands

STB - you are correct, the CSS needs to be reviewed. I'll take a look and see if I can toss together a patch.

Originally Posted by juggledad

everyman - from what I understand, a theme is submitted to WordPress and they review it and put it up when they are satisfied with it. So it is in WordPress's hands

Exactly. And from what I read elsewhere on the web ... the theme reviewers are behind on schedule reviewing themes at the moment.
Since recently .. it can take weeks before a theme gets approved.

STB - you are correct, the CSS needs to be reviewed. I'll take a look and see if I can toss together a patch.

Thanks a lot juggledad.

lmiles: Wordpress.org still has the 3.4.9 version via Appearance > Theme > Install and there is no upgrade option within Atahualpa

STB and Juggledad: very happy that this is in progress.

I knew that WordPress.org was at 3.4.9. I was just thinking that for your students you could have them download the theme from wordpress.bytesforall.com and then use the upload button at the top of Appearance > Theme > Install for the time being.

Originally Posted by lmilesw

I knew that WordPress.org was at 3.4.9. I was just thinking that for your students you could have them download the theme from wordpress.bytesforall.com and then use the upload button at the top of Appearance > Theme > Install for the time being.

Oh, duh... thanks!

=============================
THIS IS NOT A BUG - see post #49 (juggledad)
=============================


reporting bug in Ata -> Add HTML/CSS inserts -> body tag.

header.php, line 47:

<body <?php body_class(); ?><?php if ($bfa_ata['html_inserts_body_tag'] != "") { echo ' '; bfa_html_inserts($bfa_ata['html_inserts_body_tag']); } ?>>

should be

<body <?php body_class(); ?>><?php if ($bfa_ata['html_inserts_body_tag'] != "") { echo ' '; bfa_html_inserts($bfa_ata['html_inserts_body_tag']); } ?>

or indented:

<body <?php body_class(); ?>
<?php if ($bfa_ata['html_inserts_body_tag'] != "")
{
echo ' '; 
bfa_html_inserts($bfa_ata['html_inserts_body_tag']); 
} 
?>
>

should be:

<body <?php body_class(); ?>>
<?php if ($bfa_ata['html_inserts_body_tag'] != "")
{
echo ' '; 
bfa_html_inserts($bfa_ata['html_inserts_body_tag']); 
} 
?>

(See also: this now closed thread. might want to post this info there too)

STB
the original code is CORRECT, your change will introduce an error. If you go add something to ato->Add HTML/CSS Inserts->HTML Inserts: Body Tag, it needs to be inside the <body....>. IE it you added

onLoad="alert('The page is loading... now!')"

to ato->Add HTML/CSS Inserts->HTML Inserts: Body Tag then the body tag needs to be

<body class="home blog" onLoad="alert('The page is loading... now!')">

with your suggestion you would get

<body class="home blog logged-in"> onLoad="alert('The page is loading... now!')"

causing the words

onLoad="alert('The page is loading... now!')"

to show as the first line on the page.

In that other thread, the plugin had an error

Ahhh .. my bad!
My apologies for creating confusion and putting you through extra work sorting that out juggledad.
Feel free to delete these posts.

I see where I went wrong. I misread the purpose of that field, although its clearly explained.
Code there is put inside the body tag itself .. not in the body.
For code to be placed inside the body.. the next 2 fields (body top and body bottom) should be used.
Sorry!

About the other thread. In hindsight, what I think happened there .. (rather than the plug-in having an error) .. is the thread starter put his plug-in /'javascript counter code' in the body tag field, while it should have been in the 'body bottom' field .. which caused the extra ">".