No sidebar ? about unyson HOT 8 CLOSED

And why the full width template is not full width... I thought it will remove the left sidebar.
I tried to unregister secondary nav and primary sidebar without success.

from unyson.

Hi @vguenichon,

Q: And why the full width template is not full width... I thought it will remove the left sidebar.
A: I suppose you mean this template: http://screencast.com/t/Fil4wnn91N. Unyson frontend is based on default wordpress theme Twenty Fourteen. Full width page template for this theme is working in this way. We made a mistake when started with Twenty Fourteen. We plan in future to create a custom template.

Q: I give it a try actually and I discovered there's no main widgets area... even in the testlab site.
A: Like you can see int his screenshot: http://screencast.com/t/nZPUHPGK7ry it is possible to create specific widget area for specific page, category. From my point of view a default widget area is not relevant it can be created when it is needed.

Q: But there's still a container (secondary) for a sidebar (primary) in the frontend.
A: In order to add/remove sidebars it is needed to make small changes for your theme: https://github.com/ThemeFuse/Unyson/blob/master/scratch-parent/framework-customizations/extensions/sidebars/config.php
Unyson Docs link: http://unyson-docs.themefuse.com/en/latest/extension/sidebars/index.html

from unyson.

I understand the different choices a company had to do. These were just questions, and with your answers I can imagine further how I should apprehend the development of my child theme.
Thanks for your very fast feedback !

from unyson.

One more thing : Is there a way for me to modify the config of the sidebars without editing the parent theme ? Should I copy the file with the same hierarchy ?

from unyson.

Is there a way for me to modify the config of the sidebars without editing the parent theme ? Should I copy the file with the same hierarchy ?

Create the file with the same hierarchy

child-theme/framework-customizations/extensions/sidebars/config.php

and overwrite any config key

$cfg = array();

$cfg['sidebar_positions'] = array(...);

from unyson.

It was the way I planned to do it ;-) This subject is closed !

from unyson.

Well, it's not closed at all.
Modifying the config of the sidebars extension in the framework does just change the possibilities on the creation of sidebars.
But for now, I want to unregister the primary sidebar, which exist in the frontend (there's the container) and the menu location (the whole left sidebar), without hiding it with CSS. I tried to achieve it with some common wordpress functions but it doesn't work at all.

function remove_some_widgets(){
    unregister_sidebar('primary');
}
add_action( 'widgets_init', 'remove_some_widgets', 20 );

function wpse_remove_parent_theme_locations(){
    unregister_nav_menu( 'secondary' );
}
add_action( 'after_setup_theme', 'wpse_remove_parent_theme_locations', 20 );

from unyson.

I get rid of that by creating new templates... that will do the trick in a more stable way, especially when the parent theme will be updated

from unyson.