This template in version 2.6 gives me a notice: unindentified index 'footer'. Fixed by replacing the file by page.tpl.php from version 2.2 (though some css in the footer is broken). Don't know if it is important but just to let you guys know.

Comments

jsacksick’s picture

jsacksick commented
Project: Commerce Kickstart » Shiny (Administration theme)
Version: 7.x-2.6 » 7.x-1.x-dev
dudenhofer’s picture

dudenhofer commented

I think something is missing from your update. Are you sure you have the latest version of Shiny? The footer region was added in the 1.1 release. You might also check that you've updated everything. In Commerce Kickstart 2.6, there is a commerce_kickstart_admin theme that is a subtheme of Shiny. It holds things that are specific to Commerce Kickstart. It should have been enabled when you ran your updates.

I'd say double check those two things and let me know if you still have the issue.

dudenhofer’s picture

dudenhofer commented
Status: Active » Closed (works as designed)
bskibinski’s picture

bskibinski
Primary language Dutch
Location Breda, The Netherlands
commented
Issue summary: View changes
Priority: Minor » Normal
Status: Closed (works as designed) » Needs work
Related issues: +#1811122: Contexts appear that shouldn't

I think there is an issue with adding a footer region in the admin interface (as seven and rubik themes also don't have them)
This is also related to the issue "Contexts appear that shouldn't".

The footer probably has the same machine name as most front end themes. This seems to be conflicting with at least the module "context", as you can't set the theme in context, it probably looks at machine names.

So I think changing the footer machine name to something more unique (footer_admin_shiny) would resolve some issues.

Great looking theme by the way! ;)

bskibinski’s picture

bskibinski
Primary language Dutch
Location Breda, The Netherlands
commented

Just tested it, and changing the machine name does fix the issue with context.
Changes made in:
shiny.info
page.tpl.php
template.php (at the bottom)
I renamed it to footer_admin_shiny so there will never be conflicts with other admin themes.

dudenhofer’s picture

dudenhofer commented
Status: Needs work » Closed (works as designed)

I still think the appropriate thing for you is to create a sub-theme of Shiny and remove/change your region in your sub-theme. For the most part, just editing the block's configurations are going to be sufficient - Select "None" for the Shiny region, or set the page display settings for the block to exclude admin* pages.

There are plenty of ways to do this without changing the template files on everyone. Some might actually prefer having the footer blocks the same in both areas. If you need to better ensure that no one mistakenly places a block in the footer region, then I think a sub-theme is the way to go, then you can customize it all you want.