Thanks! This explain clearly! In short, entity system is a OOP thing, if you're familiar with .NET, Entity is the Object base class in drupal.
@bluepresley93153 жыл бұрын
In your diagram of an Entity at 6:10, if "properties" are, by definition, applicable to every bundle of the entity type, shouldn't the properties you have listed fall under Node and not under Article? Leaving only the fields to exist under Article? Thinking about this from a programing perspective, if I were to define an entity type in code, I would have to define the properties that would be a mandatory part of every every bundle that is subsequently created, almost as if we're enforcing an Interface contract.
@eojthebrave3 жыл бұрын
That's a good suggestion. Thanks. More like a standard UML class model. Which, would make even more sense for Drupal 8+ where entities are typed, e.g.) `Node` extends `Entity` and `User` extends `Entity`.
@deovratj19909 жыл бұрын
Thank you very much for such a great explanation!!
@attila_szilagyi8 жыл бұрын
This was very clear, thank you.
@DarktekG9 жыл бұрын
Thx for this guide :), thats why now Drupal 8 only use entities, amazing :D
@devangjalgaonkar49729 жыл бұрын
Really great tutorial. Thanks!!!!!!!
@asian005111 жыл бұрын
Thanks!! Simple and Great tutorial!
@vertovalex8 жыл бұрын
Отличное видео, спасибо.
@kumbackquatsta11 жыл бұрын
i'm building a review site with review, maker, location custom content types. they are all related. i'd like to create views of makers and locations etc. i'm not sure if entities is what i'm looking for? also, using an entities approach, does that mean i can put multiple content types on one create content form?