Notice: Undefined index: three_33 ...

I am also confused by the vagueness of this section of the instructions.
Does anyone know what this means?

In footheme_preprocess_html() you will find some stuff about responsive stylesheets and IE conditional
stylesheets - follow those instructions carefully - they are easy and involve renaming some CSS files
to match your theme name.

Hi there,

My suggestion is just an educated guess, but this is what I have done. Maybe someone will confirm or correct this.

Having followed all the previous readme instructions I was also confused by this one that you mention, because footheme_preprocess_html() (in the child theme's template.php file) doesn't contain any further instructions that I can see. So I searched my sub theme folder for files containing "footheme" and only found footheme.css. This I changed from footheme.css to the name of my sub theme new.css Then I went back into the child theme info file (my new customised one), and in there changed the reference to "footheme.css" to the renamed new.css

I wonder if there are any other references to footheme.css contained in files within my sub theme folder that also need changing?

However I suspect the steps I describe above may not be necessary, as I still continue to get 8 error messages starting "Notice: Undefined index: three_33 ..." and "Notice: Undefined index: four ..." so I'm going to revisit my sub theme's info file and see if I've missed some of the settings in pixture_reloaded.info under the header "theme settings list", as suggested here

Update: I'm using Pixture Reloaded. I solved the error messages by adding "the whole Gpanels section" in pixture_reloaded.info to my renamed footheme.info file, as described here: http://drupal.org/node/1770176

I still don't know if the renaming of files related to footheme_preprocess_html() in the template.php file is necessary, or whether I even did the correct thing renaming footheme.css in this regard. Any feedback would be interesting.

I came back to report my solution... It looks like Nitty-Gritty beat me to it.

Spacerex, to get rid of the error you are getting, you just need to copy the "Gpanels" region from your theme's .info file into your footheme.info file. (or what ever you renamed it to)

They don't specify it clearly in the readme file, but that should be done along with copying the theme Regions over.

Here's the code from the pixture_reloaded theme to add to footheme.info:

;----------// Gpanel Regions

  ; This theme uses Gpanels from Adaptivetheme core. You can add more Gpanel
  ; regions - see the "gpanels" directory in AT Core:
  ;
  ; adaptivetheme > at_core > layouts > gpanels
  ;
  ; Note that this Pixture Reloaded already uses the three-3x33 and four-4x25 Gpanels.
  ;
  ; To set the responsive layout options for Gpanels see your themes settings on the
  ; Appearance settings page for Pixture Reloaded.

  ; 3x33 Gpanel
  regions[three_33_top]    = AT Three column 3x33 - top
  regions[three_33_first]  = AT Three column 3x33 - left
  regions[three_33_second] = AT Three column 3x33 - center
  regions[three_33_third]  = AT Three column 3x33 - right
  regions[three_33_bottom] = AT Three column 3x33 - bottom

  ; 4x25 Gpanel
  regions[four_first]  = AT Four column 4x25 - 1
  regions[four_second] = AT Four column 4x25 - 2
  regions[four_third]  = AT Four column 4x25 - 3
  regions[four_fourth] = AT Four column 4x25 - 4

I just wanted to say thanks, guys. This worked for me too with correctly enabling my custom Footheme via Sky.

That fix worked for me too. Might be overkill, but here's a patch adding explicit instructions to the README so other users might the undefined error notice if not all the correct regions are defined..

Since the patch is reformatted for the extra words and line breaks, it might not be immediately obvious what it does, but it simply changes this:

2. footheme.info - first rename this file to match the folder name you chose in step one. Next you can change the "name", "description" and "version" to whatever you want. Then you need to copy and paste in some stuff from your base themes info file - the "regions list" and "theme settings list" from your chosen base theme. The ones there now are from Corolla so just replace them. If you're using Corolla then you can do nothing, or just change the name and description.

Into this:

2. footheme.info - first rename this file to match the folder name you chose in step one. Next you can change the "name", "description" and "version" to whatever you want. Then you need to copy and paste in some stuff from your base themes info file - the "regions list" (including "Gpanel regions" if applicable) and "theme settings list" from your chosen base theme. The ones there now are from Corolla so just replace them. If you're using Corolla then you can do nothing, or just change the name and description.

It just adds: (including "Gpanel regions" if applicable)

I'd also like to thank the contributors on this page. I spent the better part of this morning trying to get at commerce installed -- and the fix offered here did the trick. Thanks again.

Yes, thanks. I am using Corolla but had to copy the Gpanel regions into the .info file to get rid of the notices. I appreciate the tip.

Copying the gpanel regions into my subtheme .info file worked for me also.

I'm using the at_commerce theme (another subtheme of adaptive theme). I created a subtheme of the at_commmerce theme, copied the gpanel region settings from the at_commerce theme's .info file into my subtheme's .info file and the notices are gone.

Thanks to everyone here, especially nycguyjason for this solution.