Just like that, it does not log the event properly when this "Content is going to be viewed" action is selected.

Looking into the database I see that cached field is "", so no message showing, and also the created event date is the node creation date (maybe a problem with rules).

Any ideas?

Comments

icecreamyou’s picture

icecreamyou commented
Status: Active » Postponed (maintainer needs more info)

Do you still experience this problem with the dev build? (You may need to rebuild your new Rule from scratch after upgrading.)

orlando-rincon’s picture

orlando-rincon commented

Still not working with the dev build, I rebuilt the Rule and same thing, may be a problem with languages?, page is in english and spanish.

icecreamyou’s picture

icecreamyou commented
Version: 6.x-2.0-beta1 » 6.x-2.x-dev
Priority: Normal » Minor
Status: Postponed (maintainer needs more info) » Active

Hmm, actually, I think this was a design choice. Two reasons: (1) content views aren't stored persistently anywhere, which means they can't be regenerated; and (2) Activity Log tries to find the timestamp of the entity it's dealing with instead of using the current time so that actions can be triggered programmatically (for example while regenerating). But I suppose it's probably worth adding a specific exception for the "view content" action... I can't think of any other actions where this might be an issue.

icecreamyou’s picture

icecreamyou commented
Status: Active » Fixed

Committed fix to dev. This at least fixes the timing issue. You will have to rebuild your rule in order to take advantage of this change.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.