DrupalCon Baltimore: 161 sessions, many voices, infinite possibilities. Earlybird rate ends Friday.
Makes all system entities available to the oEmbed provider.
Install module and go to:
to retrieve the oEmbed code for an entity with ID 123 and type user.
As a third URL argument, the desired view mode can be specified. This view
mode is passed on to any default or custom viewer functions.
Make sure to set the proper permissions, allowing the access to the desired
entity types for the various roles.
It is possible to define custom callback functions to handle both access and
viewing of the entities by using the hook_oembed_entity_handlers_alter() and
implementing callbacks with the same structure as the provided default
functions that handles access and viewing.
Notice that different entity types behave different, and therefore, the default
functions might be unable to handle certain entity types. In this case, you
need to implement your own viewer and/or access callbacks in a custom module.
By default, this module will overrule all other URLs registered by the
oembedprovider module, which means that node/123 will also hit the handlers of
To prevent this, set a drupal variable named
"oembed_entity_aggresive_path_disable" with the value of TRUE.
The entities will then still be available as by using URLs like
To keep the URL references from oEmbed consumers working, this module
automatically redirects any requests to /entity/TYPE/ID to its corresponding
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Content, Content Display, Import/Export, Media, Multisite
- Downloads: 345
- Last modified: November 28, 2014
- This project is not covered by the security advisory policy.
It may have publicly disclosed vulnerabilities. Use at your own risk!