Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-21458

[eZRecommendation] Trashed objects recommended

    Details

    • Type: Bug Bug
    • Status: Confirmed
    • Priority: High High
    • Resolution: Unresolved
    • Affects Version/s: 5.2-dev
    • Fix Version/s: QA tracked issues
    • Labels:
    • Environment:

      Server OS: CentOS 6.4
      PHP: 5.3.3
      Database: MySQL 5.1.69
      Browser: Firefox 20.0
      Interface: [Admin]

      Description

      Trashed items being recommended they don't actually show on the template, however if the trashed item is the choice (for example top clicked) the yoochoose response will be that object id.

      Steps:

      1 - Create article A
      2 - Create article B
      3 - Create article C
          - summary: add recommendation
            - scenario: top clicked article
      3 - Create some event clicks on article A
      3 - Create some event clicks on article B (make sure article B is the top clicked)
      4 - Open article C
      5 - Verify that article B is the top clicked
      6 - Send article B to trash
      7 - Open article C
      8 - verify that there is no recommendation article
      9 - verify on debug.log that the response was sent with the trashed article B id
      

      ( however if the object is hard deleted it wont be chosen )

        Issue Links

          Activity

          Hide
          Gaetano Giunta (Inactive) added a comment -

          This could be fixed in the deleteeventtype.
          But then we need to add a new event (and document it in the workflows) to intercept "restore from trash" which needs to be transformed into a send-again-to-reco-engine call - and we would loose history (accumulated popularity of that object).

          2nd option: filter out objects-in-the-trash at display time.

          Show
          Gaetano Giunta (Inactive) added a comment - This could be fixed in the deleteeventtype. But then we need to add a new event (and document it in the workflows) to intercept "restore from trash" which needs to be transformed into a send-again-to-reco-engine call - and we would loose history (accumulated popularity of that object). 2nd option: filter out objects-in-the-trash at display time.
          Hide
          Gaetano Giunta (Inactive) added a comment - - edited

          Note that the same behaviour happens for:

          • invisible nodes
          • nodes to which the user does not have access by his permissions

          All of them will be recommended by the recommender engine, and the php code in ezrecoserverfunctions will not filter them out - it is up to the template layer to do that.

          Note that ezfind solves this problem in an elegant way, pushing the filtering-out-of-inaccessible-data to solr filters, but we can not do that here

          Show
          Gaetano Giunta (Inactive) added a comment - - edited Note that the same behaviour happens for: invisible nodes nodes to which the user does not have access by his permissions All of them will be recommended by the recommender engine, and the php code in ezrecoserverfunctions will not filter them out - it is up to the template layer to do that. Note that ezfind solves this problem in an elegant way, pushing the filtering-out-of-inaccessible-data to solr filters, but we can not do that here

            People

            • Assignee:
              Unassigned
              Reporter:
              Marcos Loureiro (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: