Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insert from Files button not working in TinyMCE editor #2915

Closed
2 tasks done
elliot-sawyer opened this issue Jan 15, 2024 · 4 comments
Closed
2 tasks done

Insert from Files button not working in TinyMCE editor #2915

elliot-sawyer opened this issue Jan 15, 2024 · 4 comments

Comments

@elliot-sawyer
Copy link

elliot-sawyer commented Jan 15, 2024

Module version(s) affected

Silverstripe CMS 5.1

Description

When using a vanilla installation of Silverstripe 5.1, the "Insert From Files" button does not work and causes a console error.

How to reproduce

  1. Login at Silverstripe Demo (demo.silverstripe.org)
  2. Create a new Page
  3. In the Content field, use "Insert from Files" button
  4. Select any existing PDF or upload a new one (Lorem_ipsum.pdf)
  5. Enter something for Link Text and description and press Insert Files
  6. Observe console error messages

Possible Solution

No response

Additional Context

Uncaught TypeError: e.noticeAdd is not a function
    statusMessage https://demo.silverstripe.org/assets/_tinymce/tinymce-cms-f938cf0f6c.js:62`

Validations

  • Check that there isn't already an issue that reports the same bug
  • Double check that your reproduction steps work in a fresh installation of silverstripe/installer (with any code examples you've provided)

PR

@elliot-sawyer elliot-sawyer changed the title Insert from Files link not working Insert from Files button not working in TinyMCE editor Jan 16, 2024
@elliot-sawyer
Copy link
Author

Have checked against recipe-cms 5.0.0 as well, appears to be broken there

@GuySartorelli
Copy link
Member

PR merged. This will be automatically tagged by GitHub actions

@elliot-sawyer
Copy link
Author

Is the fix for this a patch release on CMS 5.1, or will we need to wait for 5.2?

@GuySartorelli
Copy link
Member

The fix for this was tagged on silverstripe/asset-admin as 2.1.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants