Custom meta fields not showing on child themes of standalone.

[parallelus]

When creating a child theme of a Runway standalone, the meta fields created are not showing up.

Details are available here: http://runwaywp.com/support/topic/meta-field-options-away/

Additional details: http://runwaywp.com/support/topic/custom-field-doesnt-works-properly-on-child-of-standalone-theme/

[lesninsky]

Looks like this happens due to our limitation for child theme, when a parent template name should be only "runway-framework".  Should I disable this limitation to make content types functionality always working?

[parallelus]

The way it should be, the meta fields created need to show on the standalone and any child of that standalone theme. They already show for the Runway child themes. The only limitation where we should be checking for a parent them to specifically be 'runway-framework' is where editing and developer capabilities exist. The basic functionality of the meta fields are end user level so they need to work in a child of a standalone.