I think the template suggestions probably need to be prefixed with module name to avoid conflicts with other module and/or theme implementations. Currently, this will conflict with anything else that allows for the template node--page.tpl.php, for example.

Current

(from line 278, entity_panels.module)

$variables['theme_hook_suggestions'][] = $entity_type . '__' . $bundle;
$variables['theme_hook_suggestions'][] = $entity_type . '__' . $entity_id;

Suggested

$variables['theme_hook_suggestions'][] = 'entity_panels_'. $entity_type . '__' . $bundle;
$variables['theme_hook_suggestions'][] = 'entity_panels_'. $entity_type . '__' . $entity_id;

Comments

maximpodorov’s picture

maximpodorov commented

Maybe it's better to allow to use the same template for panelized and rendered in core entities. If so, the only thing to fix is to wrap $content by render() in the template. What do you think?
BTW, is it correct to add theme suggestion by view mode?

The module was a quick solution which can be improved in many ways. So new thoughts are welcomed.