Add new comment

Posted on by Nick Veenhof.

The big problem here is that entities are all very distinct from each other and can serve very different purposes. Looking at the file entity, the support for the file entity is very different and needs a contrib module to support this case. The same is valid for nodes, comments that are attached to these nodes and users.

Also, the core entity api wasn't flexible enough yet (no criticism) to support this automatic any-entity indexing case. The dependency story is only 1 factor in the decision process. As a sitebuilder, you agree to depend on the modules you choose and also which modules you install to fit your use case.

It is still based upon assumptions and I agree this might not fit every use case.
This will probably change in Drupal 8 where entities are really first class citizens.

Until that time it would be a good idea to start 1 contrib module for apachesolr that depends on entity_api and allows a generic indexing method for arbitrary entities and fields. This way the best of both world would be combined.

Does this answer your question?

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.