Custom Icon for File Browser Can't Be Uploaded: The file could not be uploaded because the destination ":///" is invalid.

Created on 13 November 2023, over 1 year ago
Updated 16 November 2023, over 1 year ago

Problem

When attempting to upload a replacement icon for Embed type = Entity and Entity type=File, I get the following error: The file could not be uploaded because the destination ":///" is invalid.

Steps to reproduce

  1. Edit an existing embed button
  2. For the Button icon, click Choose File
  3. In the Open file dialog, select an icon with the SVG extension, then click Open
  4. Error: The file could not be uploaded because the destination ":///" is invalid.
💬 Support request
Status

Postponed: needs info

Version

1.0

Component

Code

Created by

🇺🇸United States webdrips

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @webdrips
  • 🇮🇳India Tirupati_Singh

    Hi @webdrips, I followed the steps to reproduce the stated issue but didn't get any error while uploading the svg file.
    I'm attaching the screenshot for the reference.

  • 🇺🇸United States webdrips

    Hi @Tirupati_Singh I'm able to repeat this on two separate servers. Perhaps I can send you some configuration files so you can try again to repeat this?

    Not sure if I missed a step above like adding this to the CKEditor WYSIWYG? We are using CKEDitor 5 (Drupal core)

    If so, let me know which configuration files you need?

    Also we don't have private files set up, so I'm not sure if that could be the issue as well?

  • Status changed to Postponed: needs info over 1 year ago
  • 🇺🇸United States dave reid Nebraska USA

    I think this is just possibly a misconfiguration if there is no default schema set on the Drupal site. Can this be reproduced cleanly with just a fresh Drupal core + this module?

  • 🇺🇸United States webdrips

    @Dave Reid only thing I can think is it was somehow lost during a D9 to D10 upgrade, as that's when I noticed the issue.

    I can confirm a fresh install on D10 doesn't have this issue.

    Since it may be an edge case, not sure if you want to add some sort of message on the status report page about the settings not being complete and/or a better error message?

    IMHO, it should not fail the way it did though.

    Otherwise, I think this can be closed.

Production build 0.71.5 2024