You need to determine if the error is caused by jumping from WP 2.9.2 to 3.0.4 or Atahualpa 3.5.3 to 3.6.4. If you did a manual install of 3.6.4, you can just reactivate 3.5.3 and test again, otherwise I'd suggest you do a manual install of 3.5.3 and test it to see if it is one or both that causes teh issue.
there have been many changes in both WP and Atahualpa
If you like my help, please consider donating
. I am happy to provide greater detail on this and other topics if you hire me. Please send detailed support requests to me as a private message, thank you.
Juggledad | Forum Moderator/Support