Issue submitting with WEBP attachment
-
Hi
I have created my form to try to allow visitors to attach WEBP files if they want
This is how the tag in my Form tab looks … [file add-file limit:1024kb filetypes:gif|png|jpg|webp]
During my testing, after completed the form, including adding a WEBP file (size under 1024kb) and then using the Submit button … my form displays an error “There was an error trying to send your message”.
The only situation in which I have configured (via the Messages tab) the form to display that message is … Sender’s message failed to send
BUT (unknown the the user) it seems the form is submitted successfully anyway (because my SMTP plugin creates & tries to send the admin notification email (although it fails, due to a SMTP plugin msg saying there is no attachment)) & there is a copy of the info that was entered into the form in my Contact Entries (database) plugin (INCLUDING the file attachment!)
- Please can you tell me how to ensure that my form will not display the send error (and the autoresponse mails will not fail due to msg saying there is no attachment) when visitors use the Submit button … ?
Many thanks in advance
-
My theme GeneratePress and my site is based on their “Prime” template
Here is a list of my active plugins …
- Contact Form 7 (contact-form-7) – Version 6.0.6
- Contact Form Entries (contact-form-entries) – Version 1.4.0
- Flexible Checkout Fields (flexible-checkout-fields) – Version 4.1.15
- Flexible Checkout Fields PRO (flexible-checkout-fields-pro) – Version 4.0.12
- FluentSMTP (fluent-smtp) – Version 2.2.90
- GenerateBlocks (generateblocks) – Version 2.0.2
- GP Premium (gp-premium) – Version 2.5.2
- Imagify (imagify) – Version 2.2.5
- Preview E-mails for WooCommerce (woo-preview-emails) – Version 2.2.13
- Real Media Library (Free) (real-media-library-lite) – Version 4.22.38
- Simple Cloudflare Turnstile (simple-cloudflare-turnstile) – Version 1.30.0
- Stripe Payment Plugin for WooCommerce (payment-gateway-stripe-and-woocommerce-integration) – Version 4.0.4
- UpdraftPlus – Backup/Restore (updraftplus) – Version 1.25.5
- Widgets for Google Reviews (wp-reviews-plugin-for-google) – Version 12.7.2
- Wishlist for WooCommerce (wish-list-for-woocommerce) – Version 3.2.1
- WooCommerce (woocommerce) – Version 9.8.1
- WooCommerce AJAX Products Filter (woocommerce-ajax-filters) – Version 3.1.8.2
- WooCommerce PayPal Payments (woocommerce-paypal-payments) – Version 3.0.3
- Wordfence Security (wordfence) – Version 8.0.5
- WPCode Lite (insert-headers-and-footers) – Version 2.2.7
- WPS Hide Login (wps-hide-login) – Version 1.9.17.2
I have also hardened WordPress by adding code manually into the .htaccess file in the root of my domain
# Protect wp-config.php
# This rule restricts visitors from accessing your wp-config.php file, which
# contains sensitive database information, including name, host, username
# and password. It also defines advanced settings, security keys and developer
# options.
<Files wp-config\.php>
order allow,deny
deny from all
</Files>
# Prevent directory browsing
# This rule prevents attackers from viewing the folder contents of your
# website, restricting the information they have to exploit your website.
Options All -Indexes
# Protect .htaccess
# This rule prevents attackers from accessing any files that start with
# “hta” – this ensures that .htaccess files are protected in all of
# the directories of your server.
<Files ~ "^.*\.([Hh][Tt][Aa])">
order allow,deny
deny from all
satisfy all
</Files>
# Disable script injections
# Disallow script injections to prevent hackers from injecting
# malicious code into existing PHP documents.
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{QUERY_STRING} (<|%3C).*script.*(>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} GLOBALS(=|[|%[0-9A-Z]{0,2}) [OR]
RewriteCond %{QUERY_STRING} _REQUEST(=|[|%[0-9A-Z]{0,2})
RewriteRule ^(.*)$ index.php [F,L]The there is fairly standard other code added by WordPress in the same .htaccess file …
# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 24 hours"
ExpiresByType image/jpeg "access plus 24 hours"
ExpiresByType image/gif "access plus 24 hours"
ExpiresByType image/png "access plus 24 hours"
ExpiresByType text/css "access plus 24 hours"
ExpiresByType application/pdf "access plus 1 week"
ExpiresByType text/javascript "access plus 24 hours"
ExpiresByType text/html "access plus 2 hours"
ExpiresByType image/x-icon "access plus 1 year"
ExpiresDefault "access plus 24 hours"
</IfModule>
Options -Indexes
<IfModule mod_headers.c>
Header set X-Endurance-Cache-Level "2"
Header set X-nginx-cache "WordPress"
</IfModule>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^/wp-content/endurance-page-cache/ - [L]
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP_COOKIE} !(wordpress_test_cookie|comment_author|wp\-postpass|wordpress_logged_in|wptouch_switch_toggle|wp_woocommerce_session_) [NC]
RewriteCond %{DOCUMENT_ROOT}/wp-content/endurance-page-cache/$1/_index.html -f
RewriteRule ^(.*)$ /wp-content/endurance-page-cache/$1/_index.html [L]
</IfModule>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPressAppreciating your help …
The topic ‘Issue submitting with WEBP attachment’ is closed to new replies.
