New nodes within a Group don't default to mercury editor until after saved

Problem/Motivation

Create nodes that use mercury editor within a group default to the admin theme when first created. Mercury Editor only takes over when you Edit an existing node.

Assumptions

• the group module (3.3.x) is installed and enabled
• a content type that uses Mercury Editor is enabled within a group type

Steps to reproduce

• navigate to the Content library of a group. /group/[group-id]/content i.e /group/11/content
• click the +Add new content button
• click the Group node (content type) link for the content type that has the mercury editor field
• See how page loads with admin theme instead of mercury editor.
• Go into edit mode for any node in the group and mercury editor loads by default.

This works as expected:

• Go to /node/add/[content-type]
• Mercury Editor launches by default

Proposed resolution

When creating new nodes that use Mercury Editor, the page creation should launch with Mercury Editor regardless of whether the node is associated with a group or not.