Framer forms
A Framer form can look fine on the canvas and still deliver nothing. We went through Framer's help centre and put the reasons a submission never reaches your inbox, sheet or webhook in the order worth checking.
GDPR
A contact form and a job application form collect different data for different reasons. Here is what the GDPR asks of 14 common forms, with notice text and code.
Google review link
We opened good and broken Google review links signed in and signed out, on a desktop and an emulated iPhone. A wrong link only shows its error after the customer has signed in, so testing it from your own account matters.
Stamped
Stamped's install guide calls it the most common misunderstanding: on Shopify 2.0 the app block does not load Stamped's script. We read Stamped's help centre and its own demo store's markup and put the causes in the order worth checking.
tawk.to
We put tawk.to's widget code on a test page and broke it on purpose. A wrong ID did not say “wrong ID”: Chrome reported a CORS error. Here is how to read what the console says, and the dashboard settings that hide the widget on purpose.
Trustpilot
We put Trustpilot's TrustBox code on a local test page and broke it on purpose: no script, a strict Content Security Policy, a widget added after the page loaded. Here is what each failure looks like and how to fix it.
WooCommerce
We installed WooCommerce on a test site, left a review as a guest and switched every review setting one by one. Here is what each one does to the product page, in the order worth checking.
Yotpo
We read the 30 newest 1 and 2 star reviews of Yotpo on the Shopify App Store, counted what they complain about, and checked Yotpo's own help pages for the fixes. Then the steps to move your reviews out, ours included.
Supabase
The message is written by supabase-js, not by your function, and it is the same for every 4xx and 5xx. We reproduced it with the real client and showed where the function's own message is kept.
Fetch API
We read a request body twice in a Next.js 16.4 route and a response twice in three browsers. Node says “Body is unusable”, Chrome “body stream already read”, Firefox “already been consumed”, Safari “disturbed or locked”.
Office 365 SMTP
We logged in to smtp.office365.com with a made-up account and got 535 5.7.3 after almost six seconds. What the reply means, the SMTP AUTH switch that blocks most apps, and the 5.7.139 variants.
Gmail SMTP
We sent a login with a made-up Gmail address to smtp.gmail.com and got the exact 535-5.7.8 reply. What the message tells you, what it does not, and the settings that make Gmail accept the login.
Shopify
Shopify has had no built-in reviews since May 2024. Here is the setup that works on today's themes, including the two parts most guides skip: stars on collection pages and stars in Google.
Judge.me
Judge.me's carousel removes itself, header and all, when it has zero reviews to show. We found the line in Judge.me's script that does it, and the settings that leave it empty.
Judge.me
Judge.me ships every widget hidden and shows it with a script that the app embed loads. We read the markup of two live stores, Judge.me's own widget code and its help centre, and put the causes in the order worth checking.
Loox
On a live store we found a product with 24 Loox reviews and nothing on its page. The cause was the template, not Loox. Here is that case, the hide-when-empty default, and the rest in the order to check.
Mailgun
Mailgun's 401 body is the plain text “Forbidden”, not JSON, so code that calls response.json() gets a second, confusing error. We tested both regions, the official SDK and SMTP with made-up keys.
Next.js
We uploaded a 2 MB file through a Server Action on Next.js 16.4. The server logged “Body exceeded 1 MB limit”, the browser got a 500 and a minified React error, and the page did not change.
Nodemailer
Port 465 expects TLS from the first byte; secure: false makes Nodemailer wait for a plain greeting instead. SendGrid and Mailgun let it time out after 30 seconds, Gmail and Zoho hang up after 10. One setting fixes both.
Nodemailer
Nodemailer raises this error itself, without a word from the mail server: the auth object reached it with an empty user or password. Where the value usually gets lost, and a check that catches it at startup.
Nodemailer
We ran local SMTP servers with self-made certificates and got all four messages Node prints for an untrusted mail server. Which setup gives which message, and the two fixes that keep the connection checked.
Nodemailer
Leave the SMTP host empty and Nodemailer quietly tries your own machine. On our test the error came back as an AggregateError with an empty message, so a plain console.log(err.message) printed nothing.
Nodemailer
Port 587 answers with a plain “220” greeting; secure: true makes Node start a TLS handshake and read that text as a broken TLS record. Reproduced against smtp.gmail.com; it fails in under 0.2 seconds.
SendGrid
We called SendGrid's mail API and SMTP relay with made-up keys. A wrong key, an empty one and a missing Bearer each give a different message, and the official library sends the request even when the key is undefined.