Issue #2685045: Related Content uppercase string disappeared on 2.60-rc1 (Reference from string is there)

Making sure that we account for every possible layout and include the theme suggestion for them so we render with our template.

Forgot to add back in options for these if _none is selected. Need to figure out a better way to do this.

Making things a lot more performant by just passing the value that was selected to the render function and adding theme hook suggestions to each options individually so they never get added if there happens to be two render functions added when the info arrays are merged.

The media render function needs some work. Adding these unsets back for now until we can clean it up.

Rewriting the allowed values function and the helper that returns a cached version of the info array.

Cleaning up the render functions for text and snippet and rendering the content here instead of in the template.

This adds the 'field name' to all of the arrays. This makes it much easier to add a custom field for another feature. Otherwise, you end up having to add a drupal_alter just to add the 'field name' anyway.

Adding helper function to cache the info array returned by hook_oa_related_field_info(). Caching allowed values for the fields. Rewriting oa_related_preprocess_entity so it doesn't use hooks built with field names but checks for a 'field name' key in the info array if the bundle uses more than one field that is getting processed.

Adding a new arg for field name and making sure nothing is rendered for related content if '_none' is selected.

Putting the old 'allowed_values' array back for now. If values have been saved already it causes the oa_related feature to remain overridden.

Adding a new file that provides all of our 'hook_oa_related_FIELD_NAME_field_info()' functions. These are used for 'allowed values' and to allow defining new options and render functions. It gives us a hook system now.

Changing select fields, that are used to choose a layout on paragraph items, so the options are now defined by the 'allowed_values_function' and not defined in the settings form.

Updating the preprocess entity function so we can define custom sets of options for paragraph entities to define custom layouts. Adding a function to handle the allowed values for the 'layout' fields on paragraph items.

Mike Del Tito authored Nov 05, 2015 and Mike Potter committed Nov 05, 2015

Issue #2607682 by mdeltito: OA Related: PHP notice generated when content type does not contain body field