API page: http://api.drupal.org/api/drupal/modules%21system%21system.api.php/funct...
If a module triggers a theme function in its implementation of hook_entity_info this breaks different things.
It's the cause for various strange bugs:
The cause is always a call of a theme function (or l() which triggers a theme function). In some cases it intializes the theme engine too early in the boot process. In another case it uses an already initialized "wrong" theme.
There're already various bug reports for contrib modules and core which could not be reproduced unless you install a contrib module that uses a theme function in its hook_entity_info(), for example:
We want to file issues for these modules but they're more likely to be accepted as such if the documentation states that theming is not permitted in that hook.
Afterwards we can clear the issue queues of the other modules and core where people reported these strange bugs not caused by these modules themselves.
Is this still relevant?
None.
None.
None.
Postponed: needs info
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The last comment here, 6 years ago, questions whether this issue is still relevant.
I am setting the status to Postponed (maintainer needs more info). If we don't receive additional information to confirm that this still needs to be done, it may be closed after three months.