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

ezoe: Backspace in the first item of an unordered list, removes the whole list

    Details

      Description

      If backspace is pressed in the first line of an unordered list, the whole list will be removed and become simple paragraphs.

      Steps to Reproduce

      • Create the following list

        something
        - item 01
        - item 02
        - item 03
        something
        

      • Hit backspace and delete any character from "Item 01"

      The list disapears

      Note: This does not seems to happen in eZ Publish 5.x

      1. output
        42 kB
        Pedro Resende

        Issue Links

          Activity

          Hide
          Yannick Roger (Inactive) added a comment -

          Attached to this issue an updated version of the first patch.
          The 2nd one should apply (I used -l and --binary).

          Show
          Yannick Roger (Inactive) added a comment - Attached to this issue an updated version of the first patch. The 2nd one should apply (I used -l and --binary).
          Hide
          Rui Silva (Inactive) added a comment -

          Tested and approved by QA.
          Notes:
          Must apply EZSP-016-EZP4.7 from ezpublish installation root;
          Then apply third version of the first patch provided attached to this issue;
          Then apply second patch (only one version) provided in the links on this issue (the second patch must be applied with the options "-l --binary", otherwise it will fail).

          Show
          Rui Silva (Inactive) added a comment - Tested and approved by QA. Notes: Must apply EZSP-016-EZP4.7 from ezpublish installation root; Then apply third version of the first patch provided attached to this issue; Then apply second patch (only one version) provided in the links on this issue (the second patch must be applied with the options "-l --binary", otherwise it will fail).
          Hide
          Sébastien Antoniotti added a comment -

          Hi,

          Sorry, but I'm unable to patch my EZP installation (Community Project 2012.8) affected by this ezoe bug.

          It seems that patch command tries work into a "b" folder, here is my output :

          user@sd-xxxxx:/www/website.fr/htdocs2014$ patch --dry-run -p0 -l --binary < ezp-22031-patch1.patch
          patching file b/design/standard/javascript/classes/AddOnManager.js
          Hunk #1 FAILED at 1.
          Hunk #2 FAILED at 110.
          Hunk #3 FAILED at 164.
          Hunk #4 FAILED at 296.
          4 out of 4 hunks FAILED – saving rejects to file b/design/standard/javascript/classes/AddOnManager.js.rej
          patching file b/design/standard/javascript/classes/ControlManager.js
          Hunk #1 FAILED at 1.
          Hunk #2 FAILED at 113.
          Hunk #3 FAILED at 161.
          3 out of 3 hunks FAILED – saving rejects to file b/design/standard/javascript/classes/ControlManager.js.rej
          patching file b/design/standard/javascript/classes/Editor.Events.js
          patching file b/design/standard/javascript/classes/Editor.js
          Hunk #1 FAILED at 1.
          Hunk #2 FAILED at 46.
          Hunk #3 FAILED at 58.
          Hunk #4 FAILED at 79.
          Hunk #5 FAILED at 90.
          Hunk #6 FAILED at 874.
          Hunk #7 FAILED at 890.
          ...
          etc.
          ...

          Thanks in advance for your help !

          Show
          Sébastien Antoniotti added a comment - Hi, Sorry, but I'm unable to patch my EZP installation (Community Project 2012.8) affected by this ezoe bug. It seems that patch command tries work into a "b" folder, here is my output : user@sd-xxxxx:/www/website.fr/htdocs2014$ patch --dry-run -p0 -l --binary < ezp-22031-patch1.patch patching file b/design/standard/javascript/classes/AddOnManager.js Hunk #1 FAILED at 1. Hunk #2 FAILED at 110. Hunk #3 FAILED at 164. Hunk #4 FAILED at 296. 4 out of 4 hunks FAILED – saving rejects to file b/design/standard/javascript/classes/AddOnManager.js.rej patching file b/design/standard/javascript/classes/ControlManager.js Hunk #1 FAILED at 1. Hunk #2 FAILED at 113. Hunk #3 FAILED at 161. 3 out of 3 hunks FAILED – saving rejects to file b/design/standard/javascript/classes/ControlManager.js.rej patching file b/design/standard/javascript/classes/Editor.Events.js patching file b/design/standard/javascript/classes/Editor.js Hunk #1 FAILED at 1. Hunk #2 FAILED at 46. Hunk #3 FAILED at 58. Hunk #4 FAILED at 79. Hunk #5 FAILED at 90. Hunk #6 FAILED at 874. Hunk #7 FAILED at 890. ... etc. ... Thanks in advance for your help !
          Hide
          Rui Silva (Inactive) added a comment -

          Hello Sébastien.
          It is uncostumary to provide support or do QA to community issues but nevertheless, here's my two pennies worth:

          • Firstly it appears you are trying to apply one patch only (I don't know which, but there are several to apply as you can check from my own previous comment here, and one has a different method to apply);
          • Secondly, it appears you are trying to apply the patch with the option -p0. The patches that come from github always come with their paths appended with a "a/" or a "b/" before it you take a look. In order to bypass this, you have to apply the same patch with -p1 instead of -p0, so to skip one level in the tree path. This applies to all patches;
            Note: remember to always test the application of a patch with the option --dry-run, and only proceed without this option when no "Hunk FAILED's" have occurred.
            I hope I've been helpful enough.
          Show
          Rui Silva (Inactive) added a comment - Hello Sébastien. It is uncostumary to provide support or do QA to community issues but nevertheless, here's my two pennies worth: Firstly it appears you are trying to apply one patch only (I don't know which, but there are several to apply as you can check from my own previous comment here, and one has a different method to apply); Secondly, it appears you are trying to apply the patch with the option -p0. The patches that come from github always come with their paths appended with a "a/" or a "b/" before it you take a look. In order to bypass this, you have to apply the same patch with -p1 instead of -p0, so to skip one level in the tree path. This applies to all patches; Note: remember to always test the application of a patch with the option --dry-run, and only proceed without this option when no "Hunk FAILED's" have occurred. I hope I've been helpful enough.
          Hide
          Sébastien Antoniotti added a comment -

          Hi Rui,

          Thank you very much for your help, I managed to apply the patch.

          The mistake I made was to try to apply the patch from eZ Publish root and not from /extension/eoze.

          So for others in same case (Community Project 2012.8), here is the process :

          1/ download ezp-22031-patch1.patch.zip
          2/ unzip it into /extension/ezoe
          3/ patch with "patch -p1 -l --binary < ezp-22031-patch1.patch"

          Thanks to all !

          Show
          Sébastien Antoniotti added a comment - Hi Rui, Thank you very much for your help, I managed to apply the patch. The mistake I made was to try to apply the patch from eZ Publish root and not from /extension/eoze. So for others in same case (Community Project 2012.8), here is the process : 1/ download ezp-22031-patch1.patch.zip 2/ unzip it into /extension/ezoe 3/ patch with "patch -p1 -l --binary < ezp-22031-patch1.patch" Thanks to all !

            People

            • Assignee:
              Unassigned
              Reporter:
              Eduardo Fernandes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              10 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 day, 4 hours, 3 minutes
                1d 4h 3m