mrbleuu
Forum Replies Created
-
You can change the upload path to a custom directory in Forminator > Data > File Upload Storage > Custom.
Is this only available on the latest version? I cannot see it on 1.22.1
I think this has been fixed on the latest version. Still testing it out
that didnt seem to help for me unfortunately on 1.18.1 – happy to hear from the other users if it helped
Hi, I’m sure aakash version is fine and means well but I would strongly recommend downloading from official channels – go to bottom of this link
Hi,
Just roll back to previous version using a backup or downgrading back to working version.hi, it appears it is occurring with ‘hidden’ field being used for visibility (i.e. using a hidden field to pass a query string).
Here is a export: https://pastebin.com/p20kkTrt
Password is: pAJpZpQ5Yc
Great this works. I was using non empty fields.
I had to modify the code for it to work. Had to swap this line as basename would not accept an array which is what original code was passing:
$file_url = $prepared_data[ $upload_field_key ]['file']['file_url'][0];
Thanks so much for this. It’s great.
I tried with a staging site with Forminator 1.17.2 + all other muplugins disabled + all other wordpress plugins disabled – it does not work; still getting a working link to file on server via email
It didn’t work unfortunately. I am using Forminator 1.17.1 as there are issues with values in conditional fields not being submitted in 1.17.2 (which you already know about and I think it will be fixed in the next release).
I am not sure if 1.17.1 is the issue with your above code not working.
Even a muplugin with bare bones such as this does not work – still sends email with linked url (this suggests the filter is not getting processed at all):
<?php add_filter( 'forminator_get_formatted_form_entry', function( $html, $custom_form, $prepared_data, $entry, $ignored_field_types ) { $html = 'nothing'; return $html; }, 10, 5 );
I have other muplugins working fine. I wonder if it is conflicting with these.
I will use the solution smith37 posted for now.
How could I make a muplugin for this so it is not affected by future updates?
Thanks smith37. I found this useful and applied your fix for similar reasons.
- This reply was modified 2 years, 2 months ago by mrbleuu.
Hi Nebu,
You are correct – issue only affecting if the field that the others depend on is a checkbox (not radio). I was having trouble with checkbox and radio fields submitting but the original field deciding if they were visible was a checkbox.I tested with the original field being a “radio” and it does not cause the issue.
Yes having this issue too. I created a thread before I saw yours. Seems conditional visibility fields are not passing data through in the latest version
Looks like this issue is still not resolved. As per rblanda3 and my previous posts “HTML is being stripped on post submission” – what is the point in having a TinyCME field or option?
can confirm it is working now. thank you very much