Tell us what you are trying to do?
I'm using an image field in one of my content templates. When editing the post, I can not delete the image.. I can only add or replace it. This seems like a bug?
Deleting the path to the previously uploaded image does not work.
Hello. Thank you for contacting the Toolset support.
Can you pleae share problem URL where I can see the issue as well as aadmin access details.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Thank you for sharing admin access details. Using admin access details you shared I can successfully login but I do not able to access the wp-admin. Maybe you did not share the full admin rights.
Can you please grant full admin rights and after that I will be able to review what you have.
I have set the next reply to private which means only you and I have access to it.
In most other places where you deal with images, there is an "x" to click to delete. For example in Toolset repeatable images. See attached. This should be added to the single image field.
The editing experince in backend before block was used to have non-ajax submit, having said that when you save/publish/update the post in backend it used to have page refresh and if you use classic editing method, when you remove the image URL from image URL box I can see it works as expected.
But yes, with Block based editing experince as its using ajax I can see image stays even you delete the image URL, you will have to refresh the page.
I've escalated the issue in front of our next level support as usability issue. The quick workaround and solution to fix this issue will be you should use the "Classic Editor" to edit your post in backend.
I would like to inform you that we have added this issue to our internal ticket system but for now you will have to use the workaround I shared. Currently, its priority is low and we will change the priority when we notice many people affected and accordingly change its priority.
