-
Notifications
You must be signed in to change notification settings - Fork 45
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
[BUG]: Unable to clear the uploaded attachments. #11
Comments
@robert1112 Thanks a lot for reporting this bug.. I will fix it and get back to you.. Sorry for any inconvenience.. Best regards.. |
@robert1112 I have updated the plugin, so please update too and check if you can clear the attachments or not.. Best regards.. |
@kid1194 thank you. Can you take a look at this ? Thank you. |
@robert1112 Apparently it's not allowed to add a custom field to the core I have updated the plugin and in case there is a problem with clearing the attachments, a message will be post to the browser console so please give it a try.. I thought of a solution for the options field problem that I want to share with you. Do you think that it would be better if there is a plugin doctype that controls every aspect of the plugin? Or should the plugin rely on the I will update the plugin soon which should fix everything.. Best regards |
@robert1112 I have updated the plugin so please update and give it a try.. Use the default options field to set the settings.. Best regards.. |
@robert1112 I just want to check if everything is working well or there are still some bugs.. Best regards.. |
@kid1194 I got the same issue with frappe version 15 is there any way to fix this? thanks |
Describe the bug
Error message after remove the attachment and hit clear button.
To Reproduce
Expected behavior
Attachment is cleared and allow to upload
Screenshots
Desktop (please complete the following information):
ERPNext: v14.22.0 (version-14)
Frappe Framework: v14.33.0 (version-14)
Frappe Better Attach Control: v2.0.0 (main)
Additional context
None.
The text was updated successfully, but these errors were encountered: