I am not able to access:

Appearance=>Atahualpa Theme Options

When I click each category (for example Header=>Header Image) editing option does not appear

you have not given enough information to be able to help you. please be more descriptive. take a look at http://forum.bytesforall.com/showthread.php?t=6606

Using:

Atahualpa 3.5.3
WP 3.03

ATO = Atahualpa Theme Options

When I click on Atahualpa Theme Options=>none of the settings appear for any of the options, so I cannot view, edit, export or import settings.

Here is a screenshot of what appears when I click AHO=>New Menu:

http://library.gc.cuny.edu/AHO.JPG

disable all your plugins and see what happens

Thinking it might be a perms issue. What file(s) bring up options and what should the perms be set to?

disable all your plugins and see what happens

Did not resolve...

what else have you changed?

nothing. all I did was upgrade to WP 3.03 last week and noticed loss of access a few days later. So, today I thought an incompatibility may have existed and upgraded from Atahualpa 3.49 to 3.53.

well I'm running 3.03 and Atahualpa 3.5.3 fine. If you switch to twenty-ten does it work?
What version of php?

Does what work if I activate twenty-ten ? There are no theme options in twenty-ten .

I am using: PHP Version 5.2.6

check your error log to see if anything shows up when you try to access the theme options.

Here are the errors:

[Mon Dec 20 16:45:07 2010] [error] [client 146.96.33.237] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/mrl365/wp-content/themes/atahualpa/functions/bfa_ata_admin.php on line 459, referer: http://library.gc.cuny.edu/wp-admin/themes.php

[Mon Dec 20 16:45:07 2010] [error] [client 146.96.33.237] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/mrl365/wp-content/themes/atahualpa/functions/bfa_ata_admin.php on line 459, referer: http://library.gc.cuny.edu/wp-admin/themes.php

[Mon Dec 20 16:45:07 2010] [error] [client 146.96.33.237] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/mrl365/wp-content/themes/atahualpa/functions/bfa_ata_admin.php on line 459, referer: http://library.gc.cuny.edu/wp-admin/themes.php

[Mon Dec 20 16:45:07 2010] [error] [client 146.96.33.237] client denied by server configuration: /var/www/html/mrl365/wp-content/themes/atahualpa/options/jscolor/jscolor.js, referer: http://library.gc.cuny.edu/wp-admin/...=functions.php

This is odd since several people have upgraded to 3.0.3 with no problem. Did you do the upgrade manually or do it automatically? Do you have a backup of the database from before the update?

My suggestion, if you have a backup, is to install the backup to a new database, install the old version of wp and atahualpa. Then update atahualpa to 3.5.3 and do an export of the settings

Next make a backup of the existing db.

Next you could go into the existing db and delete the bta_ata4 row from the wp-options table. Then see if the the backend of atahualpa runs. If it does, import the settings and see if everything is ok.

You could also check with your host to see if anything has changed at there end.

Very peculiar. I spent the morning rebuilding and after rebuilding was able to get to the theme options for a while and now similar symptoms.

Tried different installation without plugins and even tried to roll-back to earlier versions of theme and no access to AHO, seems like an incompatibility with Wordpress 3.03.

it's got to be something at your host, others have it running.
It could be the php version you have (I've got 5.2.9) or a php/apache variable or you could be running out of php memory.

I have PHP Version 5.2.6

Right you told me that already. I wonder if the new version of wordpress is taking just that much more memory and if you are running out. This wold make sense if another theme works.

Do you know how much php memory you have and who is your host?

Host it myself and memory defined in php.ini:


memory_limit = 32M ;

No 64M did not do it.

Wondering if it has to do with the fact that I have implemented via:

http://codex.wordpress.org/Giving_Wo..._Own_Directory

and there is some peculiar mod_rewrite issue....

Were you using Atahualpa before you went to 3.5.3 and did it work?

what are the permissions for the following

FOLDERS (s.b. 775)
atahualpa
atahualpa/options
atahualpa/options/jscolor

and the FILE (s.b. 644)
atahualpa/options/jscolor/jscolor.js

Regretfully did not make a difference.