AVIA in blog and posts

Thanks, I see.

I didn’t found this AVIA activation for blog/posts in the revision history and I didn’t wanted to update without reason since we have made some minor changes and we don’t have a child theme :( I don’t know of a good practice to get child theme into an existing and used installation :(

It not really much. We needed more alternate colors and so we have overwritten this:

$avia_config[‘color_sets’] = array(
‘header_color’ => ‘Logo Area’,
‘main_color’ => ‘Main Content’,
‘alternate_color’ => ‘Alternate Content (gelb)’,
‘alternate_color2’ => ‘Alternate Content 2 (beige 1)’,
‘alternate_color3’ => ‘Alternate Content 3 (beige 2)’,
‘footer_color’ => ‘Footer’,
‘socket_color’ => ‘Socket’
);

If you would have the possiobility to have more than one alternate color, so I would not need any changes anymore :)

Well, I just tried to do this. This caused bigger problems than I though. You are writing in your codumentation “Now you’ll need to re-set your menu options and any other WordPress theme specific options that are tied to which theme you are using. Even though you are technically still using the same parent theme (with the same options), WordPress sees using a child theme as different than the parent.” … this is a bigger task :( I cannot do this on a live page. Any idea how to do this programmatically?

I manged it by a third party child theme plugin… Never mind.