Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The module currently only works on nodes, and it uses the current route to load the node ID in order to get the entity ID.
This should be changed, in being able to load any entity type, and not use the route, so we can use this module in views.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | viewsdisplayafterpatch.png | 51.46 KB | littlepixiez |
| #4 | nodedisplayafterpatch.png | 36.61 KB | littlepixiez |
| #4 | viewsdisplaybeforepatch.png | 41.42 KB | littlepixiez |
| #4 | nodedisplaybeforepatch.png | 32.09 KB | littlepixiez |
| #2 | jeditable-2925474-module-should-be-entity-type-agnostic-1.patch | 3.89 KB | staalex |
Comments
Comment #2
staalex commentedThis patch ditches node loading, and uses the entity manager to load any entity type, by its ID.
This also allows the module to be used in views.
Comment #3
staalex commentedComment #4
littlepixiez commentedI couldn't actually get the jeditable field formatter to show up on any entities (using the alpha or dev branch) in their "Manage Display" or views until I applied this patch - I was scratching my head for ages! I can also confirm that it works on normal nodes and on my custom entities in both their displays and in views. Thank you for the patch.
Comment #5
nehajyoti commentedI have not tested the patch myself but as per mentioned in Comment #4 by @littlepixiez if patch is working fine, committing the patch to 8.x-1.x branch & making another release with alpha2.
Comment #7
nehajyoti commented