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

"delete" isn't staged if target siteaccess doesn't have the content's language

    Details

      Description

      On eZ Content Staging 4.7.1, the "delete" trigger does not work. When syncing a deleted object, it seems to be working properly, as a success message is displayed (e.g. "Object 101 succesfully synchronised to feed 47ezfc_cs2.com"). However, the deleted object is still present in the target installation.

      Steps to reproduce:

      Prepare the environment:

      • Prepare two eZ Publish 4.7 installations, fully patched. One will be your source server, and the other will be the target server;
      • Install eZ Content Staging 4.7.1 on both installations. More details here:

      https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

      Note: when installing eZ Content Staging 4.7.1 in the source server, make sure to use on contentstagingsource.ini.append.php:

      TransportClass=eZRestApiEmbeddedClientStagingTransport471
      

      Reproduce the issue:

      1. Source server: create a new object. Used an article;

      Home
      	Article 1
      

      2. Source server: sync the event for the newly created object;
      3. Target server: verify that the object is present;
      4. Source server: Delete object - delete it, or send it to trash, as bug is reproducible in both situations;
      5. Source server: sync the event for the deleted object. Syncing appears to be working as expected, as a sync success message is displayed ("Object <test_object_id> succesfully synchronised to feed <test_target_server>");
      6. Target server: However, upon inspection, the object is still present.

      Note: Step 5 does not generate any errors in the error log;

        Issue Links

          Activity

          Hide
          Gunnstein Lye added a comment - - edited

          Not applicable on 4.x. The change is in composer files.

          My 4.7 installation has this component already installed, in EZP_ROOT/lib/ezc/AuthenticationDatabaseTiein/

          If you don't have it, you can get it from https://github.com/zetacomponents/AuthenticationDatabaseTiein/tree/1.2 for example (1.2 is last stable tag)

          Perhaps the reporter has a Zeta installation outside of eZ Publish, and their PHP is pointing to that, rather than the ezp one?

          Show
          Gunnstein Lye added a comment - - edited Not applicable on 4.x. The change is in composer files. My 4.7 installation has this component already installed, in EZP_ROOT/lib/ezc/AuthenticationDatabaseTiein/ If you don't have it, you can get it from https://github.com/zetacomponents/AuthenticationDatabaseTiein/tree/1.2 for example (1.2 is last stable tag) Perhaps the reporter has a Zeta installation outside of eZ Publish, and their PHP is pointing to that, rather than the ezp one?
          Hide
          Bertrand Dunogier added a comment -

          Tried to reproduce, to no end...

          I'm on the stable-4.7-SP legacy branch, with the custom-4.7.1 contentstaging branch, ezflow install, with the custom RestTransport class (shouldn't change anything btw, as it only affects publishing, not deletion).

          I have (several times) created content on source, synced from source, checked that content was here on target, displayed content on target, deleted content on source, synced from source, checked that content was deleted. I really have no clue.

          Show
          Bertrand Dunogier added a comment - Tried to reproduce, to no end... I'm on the stable-4.7-SP legacy branch, with the custom-4.7.1 contentstaging branch, ezflow install, with the custom RestTransport class (shouldn't change anything btw, as it only affects publishing, not deletion). I have (several times) created content on source, synced from source, checked that content was here on target, displayed content on target, deleted content on source, synced from source, checked that content was deleted. I really have no clue.
          Hide
          Bertrand Dunogier added a comment -

          And I agree with Gunnstein: it can't be related to this other bug, as it was because of a missing zetacomponent. 4.7 requires the full components.

          Show
          Bertrand Dunogier added a comment - And I agree with Gunnstein: it can't be related to this other bug, as it was because of a missing zetacomponent. 4.7 requires the full components.
          Hide
          André Rømcke added a comment -

          > it can't be related to this other bug, as it was because of a missing ZetaComponent. 4.7 requires the full components.

          Seems description has been updated on 25th of February so it does not reflect the issue it was previously linking to.

          Nuno + Bertrand: Could you double check that you are using the same code? Maybe missing patch in the distributed version?

          Show
          André Rømcke added a comment - > it can't be related to this other bug, as it was because of a missing ZetaComponent. 4.7 requires the full components. Seems description has been updated on 25th of February so it does not reflect the issue it was previously linking to. Nuno + Bertrand: Could you double check that you are using the same code? Maybe missing patch in the distributed version?
          Hide
          Rui Silva (Inactive) added a comment -

          Tested and approved by QA, for 4.7.1 Content Staging.

          Show
          Rui Silva (Inactive) added a comment - Tested and approved by QA, for 4.7.1 Content Staging.

            People

            • Assignee:
              Unassigned
              Reporter:
              Nuno Oliveira (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 10 minutes
                1h 10m