BnThink
Forum Replies Created
-
Now that you are using wp_update_attachment_metadata function, then I can use the corresponding filter – intermediate_image_sizes_advanced.
I have been coded successfully and can filter the Forminator media. You actually don’t need to add any new filters.
This problem is solved, thanks!
After some testing, the hook seems to work ideally, thanks!
Or, has the $prepared_data in ‘apply_filters(‘forminator_prepared_data’, self::$prepared_data, self::$module_object)‘ already completed validation? If yes, then this problem is solved.
Thanks!
Thanks for the reply. My requirement is that for some forms, I want to perform updates instead of adding new ones. So my original idea was to intercept the form data: through apply_filters(‘forminator_prepared_data’, self::$prepared_data, self::$module_object).
Perform updates and block new additions, but this seems to have security issues.I’m wondering if there is a hook for after the form is submitted that can extract the validated data (including media), perform the update, and then prevent the submission.
Thanks!
Thanks for your reply. I’m using multiple file uploads + Ajax. And only the process of this setting combination is discussed below. Two questions:
- I noticed that when the image thumbnails appear ( after I dragged the files and uploaded them ), the files have been uploaded to the temp folder with a random prefix. Does this mean that the files in the temp folder have been verified? After the form is submitted, the only thing that is performed on the media is the generation of thumbnails without any additional validation. Is this correct?
- Does forminator use its own function to generate thumbnails or is it a built-in function of WordPress? If it is a wp function, I can adjust it myself.
Thanks!
Hi. Any updates? Thanks!
I will try it. Thanks!
Thanks. I didn’t notice that option and now the problem is solved.
Thank you for your reply.
I hope that the meta_value stored in the data table for these option fields (like radio or checkbox) can also be the ‘value’ in the settings instead of the ‘label’.Can you tell me which filter hook to use? Thanks!
Forum: Plugins
In reply to: [CIDRAM] 2FA errorSolved.
Forum: Plugins
In reply to: [CIDRAM] 2FA errorHi. I successfully entered the panel by changing the key text of the source code. The update is now complete.
I found that the access permission issue was caused by a plugin conflict. **Plugin name: Security Optimizer – By SiteGround
I still don’t know which configuration is causing the problem.
The original serious error has been resolved through updates.
Now there is a new problem I can’t receive the email from 2fa (I have checked my spam box).
Through your guidance I ensured the following:
- Username is my email
- Installed and enabled phpmailer in the update panel
- Set 2fa to ‘enable’ in the frontend options of the setting page
Am I missing something?
Thanks!
Forum: Plugins
In reply to: [CIDRAM] 2FA errorI tested deleting the ‘config.yml’ but I still can’t access it.
Forum: Plugins
In reply to: [CIDRAM] 2FA errorIf you are referring to config.yml, I actually found that file before uninstalling the plugin. The problem is that the archive’s enable_two_factor remains at false.
This is weird because I didn’t change it back and it’s not possible for me to change it back (I don’t have access to the frontend).
In other words, the current plugin maintains the enable_two_factor: false setting, and then I can’t access the frontend.
Can you please tell me exactly which old settings files should be deleted and where they are located? I want to at least have access to the frontend first and then check for updates to 2fa.
Thanks for your support ??
Forum: Plugins
In reply to: [CIDRAM] 2FA errorHi. After one night, I went back to the CIDRAM frontend page again. This time it says you don’t have access instead of the original critical error. Checking the error log did not record any errors.
I’ve tried starting over, uninstalling the plugin, and reinstalling it, but still no access.
Which file in the plugin should I change to resolve this?
Thanks!
+1 on PHP 8.0