You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now I know that this only filters entries in a media library, and doesn't restrict anyone to upload different type of document. Issue is that our client have uploaded .doc file types, and when they came back to edit content this field didn't load .doc file entry (due to non matching mime-type I assume) and as they hit save this field has been overwritten with empty entry essentially deleting the content that has already been there without them knowing anything.
Ideally it would be great if it didn't let them upload different type of document. As it's currently not possible, it would be helpful if this field was populated with uploaded content when edit screen is refreshed.
I hope this makes sense.
I'm happy to attempt to fix this, just wanted to notify anyone with similar issues to prevent some headaches here.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi, first of all thanks for a great plugin!
I'm using field with following settings
Now I know that this only filters entries in a media library, and doesn't restrict anyone to upload different type of document. Issue is that our client have uploaded .doc file types, and when they came back to edit content this field didn't load .doc file entry (due to non matching mime-type I assume) and as they hit save this field has been overwritten with empty entry essentially deleting the content that has already been there without them knowing anything.
Ideally it would be great if it didn't let them upload different type of document. As it's currently not possible, it would be helpful if this field was populated with uploaded content when edit screen is refreshed.
I hope this makes sense.
I'm happy to attempt to fix this, just wanted to notify anyone with similar issues to prevent some headaches here.
Thanks!
The text was updated successfully, but these errors were encountered: