I have a form with a file upload option. The problem is that there is no way to delete the file once it's uploaded. Neither at the time the form is being filled out nor after the form has been submitted. Even on the backend as an Admin, I cannot delete it. I discovered that the BuddyBoss Platform that I am using is causing the little x in a circle to not show up. I'm new to WP, but I thought it was odd that the BB plugin would affect how things look on the WP backend. I could understand the x being missing because of some conflict on the front end. ??? Regardless, does anyone know a work around for this? Thanks! Attached is a pic looking at the WP backend in the Formidable Forms Entries area. The left is a submission view when BuddyBoss is active. There is no x or other way to delete the upload. The right is the same form submission when I deactivate BuddyBoss. It has an x and I can easily delete the upload.
.dz-details, .dz-message { display: block !important; }
Yes, you are right. After several mails with the support, they recognized the problem and suggested me to rollback to a previous version
Please login or Register to submit your answer
I think I might have found why this is happening in 6.4.2. The link to the icon is being generated. In the inspector, it has a size of 0 x 0, which usually indicates a CSS issue. The link element has the following classes defined: "dz-remove frm_icon_font frm_cancel1_icon". The inspector's style editor shows much for .dz-remove.frm_icon_font, but the frm_cancel1_icon class name doesn't exist in the CSS file.
I searched through Formidable Pro's source code and frm_cancel1_icon appears 5 times. Here's where frm_cancel1_icon is referenced:
formidable-pro/classes/models/fields/FrmProFieldPassword.php line 188
formidable-pro/classes/views/frmpro-fields/front-end/file.php line 75
formidable-pro/js/formidablepro.min.js line 21
formidable-pro/js/frm.min.jsl ine 96
formidable-pro/js/formidablepro.js line 454
The class name does not appear anywhere else in Pro. So, I searched through Formidable. The font_icons.css file that defines the class is loaded both by Formidable and Formidable Pro, but only for the signature add-on. It doesn't look like the new font icons are loading for dropzone.
Since this appears to be a bug, it should be reported to Formidable support with these findings.
<p>Interesting and comprehensive debug. Here's hoping for a quick update to fix this. I can already think of another site that I built for a real estate agent who will start asking me questions when his formidable auto-updates and stuff breaks.</p><p>Speaking of bugs, why do these paragraph tags get added here in my post when I edit it...</p>