The description on the Martplug project page that the "Martplug Elegant" theme is based on Omega is somewhat misleading. Martplug Elegant theme appears to be a subtheme of a subtheme called Sigma. Sigma is based on Omega and it appears to be focused toward commerce centric drupal sites. However, the conventions for responsive behavior are not respected like they are when a subtheme is directly based on Omega. And thus the Martplug Elegant theme does not always behave as expected.

In particular the file mobile.css from the Sigma subtheme overrides global.css which is the Omega base mobile-first stylesheet. Global.css doesn't exist in Sigma although it should if Sigma was actually generated from the omega-html5 starterkit. It appears as though the maker of Sigma created mobile.css not understanding how global-->default-->narrow-->normal-->wide would work if left alone. Also worth noting is, when global.css is manually created it is not recognized or respected by Sigma or Martplug. Sigma appears to be breaking Omega's inherent responsiveness. As far as I can tell the css stylesheet modifications in Sigma are entirely unnecessary if Omega is implemented correctly.

Also important to note is that Martplug is not using the typical Omega+Delta+Context combo for its page layout implementation. Panels is used for all page layouts. There should at least be a mention of this in the description for the sake of the Panels uninitiated.

I will have to rethink how or if I should get much more involved in customizing the "Martplug Elegant" theme because of this. I may potentially have to conclude that the profile theme is of no use to me. If so, I will have to create a real subtheme of Omega which is not what I expected to have to do given that this is an installation profile. I assume this is also not what @recidive intended.

I hesitate to call this a bug so I've set the issue to "task" as if this behavior is intended by @recidive then the "task" is to make this information explicitly clear in documentation on the project page.

From martplug_elegant.info: 

name = MartPlug Elegant
description = An elegantly designed theme for your store.
screenshot = screenshot.png
core = 7.x
base theme = sigma

From the sigma.info: 

name = Sigma
description = HTML5 theme based on Omega. Compatible with Drupal Commerce module.
core = 7.x
engine = phptemplate
screenshot = screenshot.png
base theme = omega

Additionaly, I can't find any information regarding "Sigma". Please provide details as to where Sigma comes from and why it is being used as a base for Martplug Elegant theme.

Comments

stan turyn’s picture

stan turyn commented

I'd like to add my vote to this issue. Is Sigma theme a project on Drupal.org? I had issues with image resizing and narrowed it down to Sigma.

recidive’s picture

recidive commented
Status: Active » Closed (won't fix)

If MartPlug Elegant extends Sigma wich extends Omega, so we can tell with all letters that MartPlug Elegant is based on Omega.

I just decided to have Sigma as base theme, so other MartPlug themes could extend it instead of having to deal with themeing all ecommerce elements themselves.

I started implementing Omega, when it was very early (there was no starterkit at that point at all), so some stuff may not be ported correctly according with the several changes that has broken everything.

If something is broken, it's just a matter of fixing it and submitting a patch so it can be applied to MartPlug.

@Stan Shevchuk: it's not a project on drupal.org yet, though we planned to do so. So for now, you should fix this in MartPlug project.

Please fine bug reports individually.

Anonymous’s picture

Anonymous (not verified) commented
Component: Code » Documentation
Status: Closed (won't fix) » Needs work

This issue should not be set to "wont fix" as all I'm asking be done is a simple change in the project page to reflect _the fact_ that this profile does not abide by set standards of Omega base theme implementation. This profile's layout of page structure is not at all controlled by Omega. Martplug's page layouts were built with Panels. Unfortunately, there is no mention of Panels on the project page. Yet there _is_ a reference to Martplug utilizing the Omega theme. This confusion will inevitably be problematic for people who are not familiar with Panels. Though only _after_ they have installed Martplug thinking they're getting a profile with a theme presumably properly built with Omega.

Again this issue is about misrepresenting the make-up of the Martplug profile and that requires a fix of _some_ kind. Whether that fix occurs in documentation or in a proper implementation of the Omega base theme is the maintainer's decision. But setting this issue to wont fix without addressing the problem either by changing the project page or fixing the bad implementation of Omega is IMHO not a quality response.

Anonymous’s picture

Anonymous (not verified) commented
Issue summary: View changes

typo