Instead of merely storing NID and MLID, it should be trivial to store MLID, ENTITY_TYPE and ETID. This would allow JOINs to tables other than node.

CommentFileSizeAuthor
#1 entity_index.zip4.71 KBcasey
#1 menu_entity.zip2.66 KBcasey

Comments

casey’s picture

Status: Active » Needs review
StatusFileSize
new2.66 KB
new4.71 KB

My attempt to accomplish this.

casey’s picture

agentrickard’s picture

I wonder if we should just release both and let Darwin sort it out. I'm open to either solution.

casey’s picture

Ok lets do that.

Just came up with another idea: Instead of the entity_index module we could also create a module that adds a (hidden) field to entities that contains the entity uri. That immediately would open up more possibilities (available to views, formatters, exclude certain entity types, etc).

agentrickard’s picture

Wondering how that fits in to the work here:

http://drupal.org/project/efq_views
http://drupal.org/project/entity

casey’s picture

I found another way to fulfill my needs: http://drupal.org/project/menu_link

agentrickard’s picture

I see that and wonder if it removes the need for this module. I suppose not, since this one supports its API hooks.

Which of the 3 modules are you moving forward with? All?

casey’s picture

Probably only the latter. I suspect it will be pretty easy to mimic those API hooks. I'll maybe even incorporate those hooks; I'll let you know here.

agentrickard’s picture

Status: Needs review » Postponed

I'm going to hold off on this for now, release, and link to the other projects on the module page.

vuil’s picture

Issue summary: View changes
Status: Postponed » Closed (outdated)

I close the issue as Closed (outdated) because there is not activity for the last 11 years.