Details

      Description

      I have custom remote ID's on my content objects to relate to an external database. When I try to access the remote ID of the content object in the search result with $result.object.remote_id I get the remote ID of the node instead.

      Steps to reproduce

      Use $result.object.remote_id in a search result

        Issue Links

          Activity

          Hide
          Lars Eirik Rønning added a comment -

          I can verify that this is indeed the behaviour. This needs to be resolved if remote_ids should make sense when using ezfind.

          The workaround today is to get the object of the node , and do a manual fetch in the template (or in php) to return the proper remote_id.

          Show
          Lars Eirik Rønning added a comment - I can verify that this is indeed the behaviour. This needs to be resolved if remote_ids should make sense when using ezfind. The workaround today is to get the object of the node , and do a manual fetch in the template (or in php) to return the proper remote_id.
          Hide
          Lars Eirik Rønning added a comment -

          In reply to comment #063427
          I believe that this applies also for recent versions. It was tested in 4.5 with ezfind 2.3 and in ezpublish 4.6 with ezfind 2.6 and both behaves similar.

          Show
          Lars Eirik Rønning added a comment - In reply to comment #063427 I believe that this applies also for recent versions. It was tested in 4.5 with ezfind 2.3 and in ezpublish 4.6 with ezfind 2.6 and both behaves similar.
          Hide
          Patrick Allaert (Inactive) added a comment -
          Show
          Patrick Allaert (Inactive) added a comment - Pull request available at: https://github.com/ezsystems/ezfind/pull/100
          Show
          Patrick Allaert (Inactive) added a comment - New Pull requests available at: https://github.com/ezsystems/ezpublish-legacy/pull/586 and https://github.com/ezsystems/ezfind/pull/102
          Show
          Patrick Allaert (Inactive) added a comment - - edited Fixed in: eZ Publish master (merge commit): https://github.com/ezsystems/ezpublish-legacy/commit/af67f903f69a4d3711293aba9e751c40096b08f9 + https://github.com/ezsystems/ezpublish-legacy/commit/a32887517ddcc25bdf9eca180908a214c03c347b (part 2) + https://github.com/ezsystems/ezpublish-legacy/commit/94984349978973a7c9c46a41dfe5b63413f82a1b (part 3) eZ Publish master: https://github.com/ezsystems/ezpublish-legacy/commit/4652d45ca637239b4aaa8242fef24d7b6e08b7a6 + https://github.com/ezsystems/ezpublish-legacy/commit/0d06d328430856819d2a1df440a012176c0e6c9c (part 2) + https://github.com/ezsystems/ezpublish-legacy/commit/e117da6e128dfa9ff9de2037c786a607e4d7238b (part 3) + Fixed in: eZ Find master (merge commit): https://github.com/ezsystems/ezfind/commit/94de7c0623a91b7334469a4cfe110de64e0f5cf7 eZ Find master: https://github.com/ezsystems/ezfind/commit/1a081f257b3204e612dfd9a278490fe04d344604
          Hide
          Patrick Allaert (Inactive) added a comment -

          Merging and backporting

          Show
          Patrick Allaert (Inactive) added a comment - Merging and backporting
          Hide
          Patrick Allaert (Inactive) added a comment -

          @Marcos:
          Have you done the following step:
          8b - cleaning all caches
          ?

          Show
          Patrick Allaert (Inactive) added a comment - @Marcos: Have you done the following step: 8b - cleaning all caches ?
          Hide
          Patrick Allaert (Inactive) added a comment -

          Also note that for step 9 "repeated steps 1-6", it is sufficient to just repeat step 6 (provided that you have cleaned the cache).

          Show
          Patrick Allaert (Inactive) added a comment - Also note that for step 9 "repeated steps 1-6", it is sufficient to just repeat step 6 (provided that you have cleaned the cache).
          Hide
          Marcos Loureiro (Inactive) added a comment -

          QA Approved for master

          Show
          Marcos Loureiro (Inactive) added a comment - QA Approved for master
          Hide
          Marcos Loureiro (Inactive) added a comment -

          Tested on 4.5
          QA Approved

          Show
          Marcos Loureiro (Inactive) added a comment - Tested on 4.5 QA Approved
          Hide
          Gunnstein Lye added a comment -

          Reopen to consider patch install sequence.

          Show
          Gunnstein Lye added a comment - Reopen to consider patch install sequence.
          Hide
          Patrick Allaert (Inactive) added a comment -

          @Marcos / @Eduardo: The error you are describing might be related to this patch, but maybe not.
          I think a new (and linked) issue should be created if an issue is discovered and can be reproduced with clear steps.

          Show
          Patrick Allaert (Inactive) added a comment - @Marcos / @Eduardo: The error you are describing might be related to this patch, but maybe not. I think a new (and linked) issue should be created if an issue is discovered and can be reproduced with clear steps.
          Hide
          Marcos Loureiro (Inactive) added a comment -

          It is weird since the same problem occur to us in several installations, but in the latest re-tests couldn't reproduce it anymore.

          Show
          Marcos Loureiro (Inactive) added a comment - It is weird since the same problem occur to us in several installations, but in the latest re-tests couldn't reproduce it anymore.
          Hide
          Patrick Allaert (Inactive) added a comment -

          @Marcos: This issue rings me a bell too and I really think it has been fixed and/or was caused because of a missing patch. Since I cannot reproduce it myself either, I am very confident that it has been solved, possibly with the very latest patch of this issue.

          Show
          Patrick Allaert (Inactive) added a comment - @Marcos: This issue rings me a bell too and I really think it has been fixed and/or was caused because of a missing patch. Since I cannot reproduce it myself either, I am very confident that it has been solved, possibly with the very latest patch of this issue.
          Hide
          Joaquim Cavalleri (Inactive) added a comment -

          Regression introduced by this fix identified in https://jira.ez.no/browse/EZP-21388

          Show
          Joaquim Cavalleri (Inactive) added a comment - Regression introduced by this fix identified in https://jira.ez.no/browse/EZP-21388

            People

            • Assignee:
              Unassigned
              Reporter:
              Daniel Staver
            • Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 4 days, 2 hours, 15 minutes
                1w 4d 2h 15m