Uploaded image for project: 'CMS'
  1. CMS
  2. CMS-8248

When an image contains special characters in the illustration field then the illustration is not displayed in the page

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 4.4.0
    • 4.0RC4
    • None
    • None
    • 4.4 M3

      How to reproduce

      • Go to back-ofice
      • Add a page with an article
      • In the illustration set an image with filename : "6008160736474408812-account_id=1.jpg"
        (see attachments)
      • save

      => the image is not displayed
      the URL in previw is : http://......./preview/intranet/_contents-images/ametys-internal%253Asites/intranet/ametys-internal%253Acontents/risques-article/_metadata/illustration/image_max150x150/6008160736474408812-account_id?objectId=defaultWebContent%3A%2F%2F39eb2dcf-2749-4db4-8fb5-73443a1b7507

          [CMS-8248] When an image contains special characters in the illustration field then the illustration is not displayed in the page

          Fixed by upgrading to Cocoon 2.1.13

          Cédric Damioli added a comment - Fixed by upgrading to Cocoon 2.1.13

          The 2 PR have been removed (not necessary and not wanted).
          Patch has been commit to cocoon but the cocoon patched version will be used only in 4.3 version

          Laurence Aumeunier added a comment - The 2 PR have been removed (not necessary and not wanted). Patch has been commit to cocoon but the cocoon patched version will be used only in 4.3 version

          A patch for cocoon has been proposed.

          Moreover the 2 pull requests made the pipeline to serve image more permisive (image with no extension could be served). This is complementary to cocoon patch. The cocoon path is enough to fix the issue

          Laurence Aumeunier added a comment - A patch for cocoon has been proposed. Moreover the 2 pull requests made the pipeline to serve image more permisive (image with no extension could be served). This is complementary to cocoon patch. The cocoon path is enough to fix the issue

          Laurence Aumeunier added a comment - - edited

          This is a cocoon issue when uploading file. The "=1.jpg" is lost.

          Moreover the pipeline to serve image waits for a filename with extension "* . *", that why there is a 404. The pipeline should be more permissive.

          Laurence Aumeunier added a comment - - edited This is a cocoon issue when uploading file. The "=1.jpg" is lost. Moreover the pipeline to serve image waits for a filename with extension "* . *", that why there is a 404. The pipeline should be more permissive.

          Laurence Aumeunier added a comment - - edited

          The value sent by JS widget is already wrong (missing "=1.jpg" in filename)

          {
          "id":"8f054a41-3e41-4a69-90a5-f2aae17c3444",
          "filename":"6008160736474408812-account_id",
          "size":386992,
          "viewUrl":"/cms/plugins/core/upload/file?id=8f054a41-3e41-4a69-90a5-f2aae17c3444",
          "downloadUrl":"/cms/plugins/core/upload/file?id=8f054a41-3e41-4a69-90a5-f2aae17c3444&download=true",
          "type":"metadata"}"
          

           

          Laurence Aumeunier added a comment - - edited The value sent by JS widget is already wrong (missing "=1.jpg" in filename) { "id":"8f054a41-3e41-4a69-90a5-f2aae17c3444", "filename":"6008160736474408812-account_id", "size":386992, "viewUrl":"/cms/plugins/core/upload/file?id=8f054a41-3e41-4a69-90a5-f2aae17c3444", "downloadUrl":"/cms/plugins/core/upload/file?id=8f054a41-3e41-4a69-90a5-f2aae17c3444&download=true", "type":"metadata"}"  

          Indeed, adding "=1.jpg" at the right place in the url makes things ok

          Raphaël Franchet added a comment - Indeed, adding "=1.jpg" at the right place in the url makes things ok

            cedric Cédric Damioli
            fravetier Frederic Ravetier (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: