Tim-Callvoip Posted August 25 Share Posted August 25 Hi, A few weeks ago I had a large number of legit users register at the same time on my store, every since this moment I've had a gltich with my contactform module. The contactform module puts in the users e-mail address automatically pulled from their account, however since this moment whenever users click on the contact form a random e-mail is displayed instead of theirs. So if they don't manually adjust it, the e-mail reply is sent to a random users. Any suggestions? I'm considering adjusting the code of the module to remove the auto-filled function so users always have to manually type in their e-mail address. Link to comment Share on other sites More sharing options...
El Patron Posted August 25 Share Posted August 25 (edited) diagnostics to try Incognito A/B test Log in as User A (Incognito 1) → open the contact page. Log in as User B (Incognito 2) → open the contact page. If User B sees User A’s email, you have shared HTML caching. Signed-in cookie + proxies If you use Cloudflare/Varnish/Nginx fastcgi_cache, verify they bypass cache for logged-in users (PrestaShop cookies like PrestaShop-* should trigger a bypass). Exclude the contact page route (usually /contact-us or controller contact) from any reverse-proxy/page cache. fast fix {# in your contact form template #} look here first: /modules/ps_contactform/views/templates/front/contactform.tpl <input type="email" name="from" id="from" value="" autocomplete="email" required> Edited August 25 by El Patron (see edit history) Link to comment Share on other sites More sharing options...
Tim-Callvoip Posted August 25 Author Share Posted August 25 24 minutes ago, El Patron said: diagnostics to try Incognito A/B test Log in as User A (Incognito 1) → open the contact page. Log in as User B (Incognito 2) → open the contact page. If User B sees User A’s email, you have shared HTML caching. Signed-in cookie + proxies If you use Cloudflare/Varnish/Nginx fastcgi_cache, verify they bypass cache for logged-in users (PrestaShop cookies like PrestaShop-* should trigger a bypass). Exclude the contact page route (usually /contact-us or controller contact) from any reverse-proxy/page cache. fast fix {# in your contact form template #} look here first: /modules/ps_contactform/views/templates/front/contactform.tpl <input type="email" name="from" id="from" value="" autocomplete="email" required> Hey, thanks for the reply. Apperently the ps contactform was overwritten by a duplicate of the theme. So I just ended up making value={customer.email}" I replaced it with value="" so now people need to manually type it in, so it cant accidently put in the email of another customer. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now