My site has been running v3.4.4 of this rockin' theme on WP2.9.1 for a while. When 3.4.6 came out I tried upgrading, but the background for the top level of the Page Menu (div#menu1) stopped loading, so the entire Menu wasn't shown, so I went back to 3.4.4.

Now I'm trying to update to 3.5.1, and encounter the same problem with the Page Menu. (The widget title box background graphic works fine, so I've kept its path to 3.5.1's folder.)
I have tried:
1. Looking for other threads about something similar to this
2. Verifiying with the recent Juggledad's colored menu cheat sheet that the div name is correct
3. Leaving the HTML/CSS insert path using the 3.4.4. theme path and also tried both of the newer themes' paths.
4. Verifying that the graphic has been copied to the correct paths in the two newer theme's folders
5. Deleting WP Super Cache's cache and disabled the plugin
6. Trying the site in IE and FF, on different computers
7. Flushing my browsers' caches
8. Verifying that the folder permissions are the same the entire path

Thank you for trying to help.
It's an active site, so I can't leave it in its broken state running 3.4.6 or 3.5.1, and I don't know how to make a copy of the site available at a different URL path in the remaining time I have to work tonight.
I'll try to keep this thread on my monitor tomorrow (US-Pacific), if anyone needs to see it broken.

when you upgraded did you copy the /wp-content/themes/atahualpa/images/pagemenu.png file to the new atahualpa351/image folder?

Thank you for responding.
Yes, I verified that the graphic has been copied to the correct paths in the two newer theme's folders.

without seeing the site on 3.5.1, not much I could do.
Do this, swap to 3.5.1 and then EXPORT your settings (ATO->Export/Import) and swap back to your current version. Then send me the export file and I'll take a look. I'll be gone for a bit but will check in later

Here are the settings after temporarily Enabling 3.5.1.

you have a mixture of addresses point to where the images should be
ATO->Style & edit HEADER AREA->Horizontal Bar 1: Styling (and bar2) point at atahualpa/images
while ATO->Style & configure SIDEBARS->LEFT sidebar style points at atahualpa351/images/

ATO->Style WIDGETS->Widget Title Box uses atahualpa/images
ATO->Style POSTS & PAGES->POST Container: STICKY uses a fully qualfied path pointing to another site
The footer uses atahualpa/images and the
CSS inserts which style the menu, use atahualpa/images

Are all the images in both places??

For clarification:
The folder for v3.4.4 is .../themes/atahualpa/
The folder for v3.4.6 is .../themes/atahualpa346/
The folder for v3.5.1 is .../themes/atahualpa351/

v3.4.4 is working without problem, even though some sections of the theme look for graphics at /atahualpa/ and other sections look for graphics at /atahualpa351/.
I've triple-checked that every path that is being used for a graphic has the appropriate graphic, and as I began (but haven't yet finished) setting paths to /atahualpa351/ and found they continued to work in all theme versions, I kept them pointing to /atahualpa351/.

In v3.4.4 everything works correctly as currently set.
In v3.4.6 and v3.5.1, the Widget Title Boxes work correctly no matter the path, but not the graphics around the Page Menu.
In v3.5.1, the Widget Title Box works correctly, but not the Header images or the Background for the Page Menu bar.

The path at
ATO->Style POSTS & PAGES->POST Container: STICKY is the v3.4.4-generated default path; I haven't made any posts Sticky.

I've left the site set for v3.5.1 for a while. It's a live site, but doesn't get a lot of traffic.

you don't display the header image via the %image, in the earlier version I thought I saw a whole java script that was doing the image. Could it be that you modified some of the atahualpa code in 3.4.4?

I had made two modifications to the v3.4.4 code:
1. Updated header.php between the <?php } ?> and </head> to fade-rotate the header images using DynamicDrive's Ultimate Fade-In Slideshow.
Now that v3.5.1 is able to do that itself, I have kept /atahualpa351/header.php unchanged.

2. Commented-out the code for the credits line shown in the footer, after seeing Flynn's post a while back that he doesn't mind. I've made this same change to v3.5.1.

For v3.5.1, aside from item 2 all the .php files are stock. I forced that by re-uploading them yesterday afternoon.

But to have teh rotating/fading headers in 3.5.1, you must add %images to the ATO->Style & edit HEADER AREA->Configure Header Area or atahualpa won't build anything for the header.

Thank you for the reminder to put %image (not %images, in case anyone else is reading this and might get confused) back.
That shows better that the Page Menu bar is missing from where it's supposed to be according to the ATO->Style & edit HEADER AREA->Configure Header Area setting: between the two bars shown immediately below the Header images.

In it's useful, here's an updated Export of the settings.

(Once the Page Menu bar was working, I was going to look around the theme options again before possibly looking like a dope in the Header Information & Styling forum. )

I've set the site back to v3.4.4 for now, until I see you need it changed back again or something else is figured out.

I expect to make a donation soon, and hopefully the Condo Assoc. Board will let me pre-order ThemeFrame for the site. Checking Flynn's news over the past few months, ThemeFrame looks very impressive, especially considering the pre-order price.

here is somethingt to try, change teh CSS Insert to point at the full path to the image, ie
background:url(http://www.murrayhillwoods.com//wp-c...s/pagemenu.png)

Well, I'd like to say that worked, but no bueno; same as before: no Page Menu bar shown in v3.5.1. Shows okay in v3.4.4 with that new path, though.

Mind if I poke inside? If not send me a pm with an admin I'd and pw

The offer is appreciated, especially considering your workload today.
PM $ent.

I deleted the 'bfa_ata4' record to grab the settings again from 3.4.4 and everything looks ok now. you must have gone to 3.4.7-3.4.9 at sometime and there were some problems creating the 'bfa_ata4' records. Please check the site out now.

Thank you- it does look correct with v3.5.1 enabled.

I never did end up installing v3.4.7 - v3.4.9- just 3.4.6 and stopped until v3.5.1... oh well.
Trying the "Delete the option 'bfa_ata4'" was something I considered, but I hadn't yet read about the extent of what it really does, and also it hadn't been suggested yet.