entity

Drupal 8 core has entities like node, user, taxonomy..etc., which helps to process different types of data based on their usage.

Likewise, we can create custom entity to maintain structured data like customer data, inventory data, products data..etc.,

When is Custom entity needed in Drupal 8?

1) When there are requirements for huge number of fields.
2) When exposing data to different applications. The "UUID" generated will be used as reference for each entry to other applications.

Saludos compañeros y de antemano gracias por la ayuda.

Con la función arg() puedo hacer ciertas consideraciones sobre las rutas en drupal y hasta determinar el tipo de entidad.

¿Drupal tiene alguna función que al ingresar la url detecte de forma directa el tipo de entidad?

Gracias

Hi there,

I'm going to make module that will track the logged in users who viewed the entity.
With this module you will be able to make "People viewed your profile" block like Linkedin does.

What I need:

• Relation user to entity
• Store last viewing date
• Integration with views

Does anyone want to stop me? :) Are there any modules that makes same thing?

Update: Too late, module is ready: Entity Visits

Hi guys, I've created a simple custom field (via field api) that should "emulate" references, but allow to define the "reference" type (using a Taxonomy Term).

Basically, I have an entity_type (Company, created with eck module) that use my field to store employees, and the taxonomy term give me the employee type (commercial, owner, secretary, etc...)

I cant put taxonomy term directly in the user, becose a user can be an employee of two different companies.

We held our Broward Drupal monthly meetup on Wednesday, November 13th from 7:00pm to 9:00pm.

Remote participant(via Skype and Join.me):
Orlando - Debra Wilson, Patricia Mathews

In Person (Greater Fort Lauderdale, Broward County Florida):
Jay Epstein @jeppy64, Ricardo Reyes, Carlos Kosloff and me @hectoriribarne

This month Jay Epstein (@jeppy64) continued to share the entity-based approach he uses to build Drupal sites. He started off by showing how to theme a view using a global field to use html without having to edit any tpl.php files.

This http://drupal.org/node/1603204 document on drupal.org sounds more like a guideline while developing custom modules for personal use or using the UI to create entities.

When i asked about entity naming convention in #drupal-contribute, xano told me that everything ( entity machine name ) should be prefixed with module name.

While checking a project application, it was found that it used "watchdog" as an entity name. Should it be allowed?

Should

1. Is it a must that "Machine name of every entity declared by a module should be prefixed with the module name." ? Or,

Sorry post got created twice. If somebody could delete thise. Please do.

Link to the other post is below.

http://groups.drupal.org/node/293813

I have been using entitycache [1] without problems in D7. However I have not really measured lately does it really improve the performance and is there some issues? And what is the state at the moment about entitycache going to core [2] in D7 or D8?

What I am asking is:

1. Should I use entitycache in projects of any kind? (Like using APC cache ALWAYS because it does not matter is there logged in users or not.)

2. Has anyone measured the impact lately? (If it is in core it does not really make sense using it, right?)

Hey guys i'm being bold here. But i couldn't figure out where to add D8 feature request so i thought i gave it a shot here.

I was wondering if what the pro's and con's are of making forms more entity'ish..

Why not make "all" the forms based on this form.entity type. Adding field (and thus widgets) would be a breeze (from a UI perspective). In core there are a few "fixed" forms like:
- the login form
- the contact form
- the password forget form
- the comments form
- the modules forms (like rating of add to cart)
- e.t.c.