-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[4.0] Drag n Drop Images in TinyMCE kills site #27477
Comments
@brianteeman Do you think this is a release blocker? To me it seems it could be one. |
I would say this is a release blocker. We definitely don't want to impact DB performance as well as size if it is being loaded this way. This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/27477. |
@bembelimen is this a regression of the tinymce 4.0 update? Can you have a look at this? |
Setting as release blocker |
Setting paste_data_images to false will prevent this happening but it still wont fix the non working joomla drag and drop plugin |
There are several reasons for this broken behavior:
|
This comment has been minimized.
This comment has been minimized.
ah, okay, I see joomla-cms/administrator/components/com_media/src/Controller/ApiController.php Lines 26 to 29 in 24265b1
|
To be able to fix this issue someone need to write an upload handler. |
Seriously - the all singing all dancing new media manager doesnt have an upload handler rm -rf /com_media npm i upploadjs.org |
I had similar thoughts 😄 |
I'll post a patch tomorrow |
PR: #28928 |
@dgrammatiko Shall I close this issue because there is PR #28928 ? |
Yes😉 |
Closing as having PR, see above. |
Well not exactly kills it but it will do eventually
In Joomla 3 a drag and drop image plugin was added so that you could add images to your content more easily and the images would be saved automatically in a specified folder on your server.
In Joomla 4 that isnt working at all
Instead the native tinymce drag and drop image is used. This is a problem because this saves the image as a base64 blob in the database. Obviously this is not desirable as a user uploading a large image will see it take a long time to save the article and very quickly the database will get huge. It is also really slow to render an image this way.
The text was updated successfully, but these errors were encountered: