/en/admin/appearance

At very bottom of the page:

"Use the administration theme when editing or creating content" is current turned off by default. This should be turned on by default so all of the proper styling for the ember theme is applied to pages like node edit and WebFrom edit/creation

Comments

sylus’s picture

sylus CreditAttribution: sylus commented
Issue summary: View changes

The default for this is that node editing page get rendered with the front end theme. People are welcome to customize it but the default should stay the same.

StephenOTT’s picture

StephenOTT CreditAttribution: StephenOTT commented

why is it rendered with the front-end theme? What was the thinking behind the default

sylus’s picture

sylus CreditAttribution: sylus commented

Based on the feedback of most (actually all) clients when asked their preference they expect that when editing content that it should be as close to the final render as possible or at least give the illusion. Essentially there is a separation between administrative tasks and editing content.

I get that that there is more screen real estate using the backend theme so I am open to having a discussion on this though.

Flip the argument what is the reason you want to do this in the admin theme aside from real estate?

Keep in mind we are essentially talking about what is the best default option as we don't restrict changing this setting.

joel_osc’s picture

joel_osc CreditAttribution: joel_osc commented

I believe Drupal default is to not have that selected and I don't see a strong case to set it by default. Variations from base Drupal should likely be heavily substantiated to support the deviation. The option is always there if someone wants it. Just my 1.9 cents.

StephenOTT’s picture

StephenOTT CreditAttribution: StephenOTT commented

expect that when editing content that it should be as close to the final render as possible or at least give the illusion. Essentially there is a separation between administrative tasks and editing content.

Isn't this why we have the in-line edit capability/going to have the in-line edits?

sylus’s picture

sylus CreditAttribution: sylus commented

Yes but that isn't in yet only the 2.x branch has inline editing. I can be persuaded to switch to the backend theme by default but before that change is made we would likely have to style the backend theme to fix some paddding issues etc.

If we get aaron to look at this and do some touch ups then I will acquiesce.

Change of getting him to look at it today before 1.3? Or else you guys will have to wait another month.

StephenOTT’s picture

StephenOTT CreditAttribution: StephenOTT commented

Can always wait for in-line editing to come in.

sylus’s picture

sylus CreditAttribution: sylus commented

In line editing wont ever come in 1.x branch I don't think as needs ckeditor instead of wysiwyg etc.

sylus’s picture

sylus CreditAttribution: sylus commented

Alright I made the requested change but had to do a few minor things with wetkit_pages.

Here are the changes:

a) WxT Core patched so node_admin_theme is set to 1 @ http://drupalcode.org/project/wetkit_core.git/commit/3d5a897
b) WetKit Pages patched so Tabs only render on Omega for Basic Page as admin theme has them at top (Glad we caught this) @ http://drupalcode.org/project/wetkit_ember.git/commit/0bfc560
c) A few display issues with Ember for node/edit @ http://drupalcode.org/project/wetkit_pages.git/commit/48c1e40

sylus’s picture

sylus CreditAttribution: sylus commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

joel_osc’s picture

joel_osc CreditAttribution: joel_osc commented

A question about this. In the front-end theme I can control where or if I show tabs at all within a panel region. If I use the backend theme the tabs are back in the template... so if we want to keep the backend theme for editing what is the best approach to get my granular control over tabs again? My use case is that I have a content type that I don't want the tabs to show up on because the user should never be able to view nodes of this content-type.