Upgrade debacle: 3.7.12 > 3.7.24

  • csrollyson

    (@csrollyson)


    10 years, 11 months ago

    I have used atahualpa for many years for several blogs, and I’ve customized it a lot. Wordfence screeched that I was out of date, so I upgraded from *12 to *24. Here is what happened:
    -The entire header/menubars gone on home page, category list, blog posts
    -header area but not logo showed on archive and tag pages
    -Tag page warning: “array_rand() expects parameter 1 to be array, null given in /home/rollyson/public_html/wp-content/themes/atahualpa/functions/bfa_header_config.php on line 276” . I found this but couldn’t figure out how to address it.
    -all widgets gone, but I found them in the appearance/widget pages under inactive; all my sidebars were empty, so I dragged a couple into the sidebars, but these didn’t display consistently

    In short, my website was “headless” for over a day and only a domain backup saved me; the back end wasn’t affected.

    Related, I have tried many times to export settings under atahualpa export, but it never works; it returns a blank screen, so I guess I need to figure out how to use Cpanel or ftp to back up settings before upgrading.

    Does anyone know what file(s) the settings file is supposed to export?

Viewing 3 replies - 1 through 3 (of 3 total)
  • juggledad

    (@juggledad)

    10 years, 6 months ago

    When you do an export (Atahualpa Theme Options->Export/Import) it should create a file in your download folder of the theme options that you can use to import with.

    Thread Starter csrollyson

    (@csrollyson)

    10 years, 6 months ago

    @juggledad thanks for the info. Yes, that is the the theme help says, but it doesn’t work for me.

    juggledad

    (@juggledad)

    10 years, 6 months ago

    There was an issue where a couple items – if un set, wouldn’t export. I could try walking you thru editing the export file or if you go to the dedicated theme forum – http://forum.bytesforall.com – and open a thread and attach your export, I can fix it for you.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Upgrade debacle: 3.7.12 > 3.7.24’ is closed to new replies.