Using Fivestar in Views causes the node update date to change [#3339062]

Hello! If the rating stars of the Fivestar module are displayed in Views, then I see an incorrect node update date:

Published
Last saved ( all languages ) 02 / 03 / 2023 - 18 : 55

If the stars of the rating of the Fivestar module are displayed using the fields, then the date of saving (change) of the node corresponds to the last publication date:

Published
Last saved ( all languages ) 01 / 30 / 2023 - 22 : 30

Thus, with each vote through the Views output, the node update date changes for me.

I need the correct date because the Views on the main one displays the nodes in the update order. At the same time, I can't display Fivestar module rating stars not in views in some content types.

How to fix it?

Comments

Comment #1

3 February 2023 at 21:18

gpf created an issue. See original summary.

Comment #2

ivnish CreditAttribution: ivnish commented 4 February 2023 at 06:33

Assigned:

gpf

» Unassigned

Comment #3

TR CreditAttribution: TR commented 4 February 2023 at 21:36

Version:	8.x-1.0-alpha2	» 8.x-1.x-dev
Status:	Active	» Postponed (maintainer needs more info)

I'm not sure what you're saying.

If someone rates a node by using a Fivestar field on that node, then the node is being changed. The "last updated" time of the node should change every time the node is rated.

Is this not happening?

Comment #4

gpf CreditAttribution: gpf commented 6 February 2023 at 17:15

If this is intended, then in this case I will not be able to display only the materials updated by the admins on the main page. Fivestar creates spam from node updates as hundreds of users are constantly voting and rating nodes.

Comment #5

TR CreditAttribution: TR commented 6 February 2023 at 23:28

This is the way all entities with fields work in Drupal. Right? If a field is modified, any field, then by definition the entity containing that field has been modified, so the timestamp is updated for the entity. Fivestar isn't explicity updating the entity timestamp, that is being done by core Drupal.

Do you expect the entity timestamp to be updated only when the Body field is modified (for example in the case of a node)? How is Drupal supposed to know that you only want changes to some fields to be reflected in the timestamp, and not changes to other fields?