We tried using views accelerator on a view with a large table of data. Most of the data was shown correctly but some did not including:

  • Single-value entity reference field using relationship - was configured with entity reference relationship and showed a field from the referenced entity (showed empty)
  • Multiple-value entity reference field not using relationship - was not configured with entity reference relationship and showed the default format from the referenced entity which contained multiple values (it showed the node ids for the referenced entities but not the node titles)
  • Date field - date format looked off (showed time even though it wasn't configured to show time)

I have not tried to reproduce with another view but I found that removing views accelerator from the cache setting did fix the issue.

Comments

kristen pol’s picture

Title: View with entity reference data not showing up correctly » View with entity reference and date data not showing up correctly
rdeboer’s picture

Hi Kristen,

The module offers its users to trade off rich rendering in return for speed. Its philosophy is: don't pay (in terms of CPU cycles) for something you don't use.
It does not offer you to have your cake and eat it too.

As the FAQ on the project page says:
Performance acceleration established by this module comes from simplifying the post-execution and formatting/rendering of view fields. You may find that for some fields the simplification is taken a little too far. Entity Refs for instance, render as their target ids.

So Entity Refs are not the greatest fields to use in combination with this module.

I suspect simple improvements may be possible for the Date fields. We can work on that together, if you wish. But again, if the module was to bring back full rendering of Dates in all cases, then it would be a return to Views as it is and not offer any speed improvements.

If the visual rendering of Entity Refs is really important to you, e.g. they're not in the View to be passed on to another subsystem, like a map, then this horse is not suitable for your course.

I guess for greater flexibility it would be nice if the module was extended to be switched on/off not just on a per-View basis but also on per-field basis. Then you could NOT accelerate Entity Refs (and fully render them as per normal), but accelerate other fields in the View.

kristen pol’s picture

Status: Active » Closed (outdated)

I'm closing out some of my old outdated issues... this one is almost 6 years old o_O.