I created three layouts each consisting of a layout.inc file and and layout.tpl.php file, each inside it's own folder, which are inside the layout folder in my omega subtheme. I put layout.scss files each in their own folder, inside the layouts folder in the sass folder of the subtheme. Ruby created the appropriate css files in the css folder in the subtheme.
So far so good.
Under the subtheme settings in the UI their is a place to turn on the Layouts Extention, which I have done. However I am only able to choose one layout not multiple layouts. (I assumed you should check each of the layout you want to have active in the subtheme... but maybe I am only allowed to choose one because that is suppose to be the default???)
Under contexts, I add the context choose Context_Omega for the response however there is no menu to choose a layout instead there is a message "Either omega isn't active or the omega cache is empty."
It looks like that text is generated by Context_Omega after it checks the settings for Layout Extension...
Do you know if I am missing a step? Any ideas about how to troubleshoot this issue?
Comments
Comment #1
attiks commentedYou have to load a page using your omega based theme, once you created the context. The problem is that the list of possible layouts is build by omega, and the first time we don't have a list to use in context.
Comment #2
smerth commentedI have now been able to get a drop down menu under contexts and choose the different layouts for different contexts. However the layouts are not loading.
I know that context is working because all the other reactions to those contexts are working but the tpl.php and layout.inc files are not loading for a given context...
Can you think of any reason why this might be?
Comment #3
smerth commentedIf I choose a layout from the LAYOUTS_EXTENTION_CONFIGURATION UI then that layout gets applied to all pages regardless of the context. So I think the layout.inc and tpl.php files are ok for each layout but somehow the context is not able to switch the layouts... I am stuck...
Comment #4
attiks commentedCan you enable the context inspector block and check the reaction, it should show 'context_omega_reaction_omega_layout' containing a child element 'layout'
Comment #5
fubhy commented@attiks: The problem is that you are reading from the cache entry directly. Instead, you should include the omega.inc file and invoke the API function to build the cache if it does not exist yet. Will post a patch in a minute.
Comment #6
attiks commented#5 I pushed something to git, see http://drupalcode.org/project/context_omega.git/commitdiff/6408f47?hp=bd...
I guess this is what you meant?