Active
Project:
Model Entities
Version:
7.x-1.0-alpha2
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Aug 2012 at 22:30 UTC
Updated:
25 May 2016 at 16:11 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
camdarley commentedI have exactly the same problem.

admin/content/my_entity is empty and show admin/content/comment menu item...
I replaced carefully all "model" by my custom entity name in each module files.
I can add entity types without issue.
Comment #2
camdarley commentedOk, I juste understand why it wasn't working: I renamed "model_handler_model_operations_field.inc" in "myentity_handler_model_operations_field.inc" instead of renaming it "myentity_handler_myentity_operations_field.inc". This prevented the view to install on the module activation.
@euroba : check if your entity view is present in your view list.
Comment #3
oribi commentedSimilar problem but it only happens when I create multiple entities. Works fine when only enabling one entity. Everytime I enable another custom entity, the previously enabled entities view gets removed/replaced by the new one.
I other words when enabling multiple entities using the model module file-renaming and text-replacement method, only the last installed entity has a view. There seems to be a duplicate identifier issue...
Anyone else experienced something similar?
Comment #4
vegantriathlete@oribi I think you are talking about an issue that is different from the OP's -- #2566811: MODULENAME.views.inc should be renamed to MODULENAME.views_default.inc