Home/Notes/contact forms for a restaurant
contact forms for a restaurant
28 Feb 2024
How a restaurant deals with contact forms — and what usually goes wrong.
The problem: a www record that disagrees with the apex. This breaks contact forms for a restaurant.
Our own site had a www record that disagrees with the apex for three days before a colleague noticed. We added it to the pre-launch checklist the same afternoon.
We rotate API keys for contact forms annually. a restaurant did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
The registrar dashboard crashed twice while we were fixing contact forms for a restaurant. We filed a ticket; they replied four days later with a template answer.
Managed hosting handles contact forms automatically — until it does not. a restaurant learned this when their provider migrated servers and a www record that disagrees with the apex disappeared silently.
Before you touch contact forms, take a screenshot of the current state. Half of our emergency calls come from people who cannot remember what was there before the change.
a restaurant did not want to hear about contact forms. They wanted to know: will the site work tomorrow morning. The answer was yes, but only if we fix a www record that disagrees with the apex today.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com