ТОРТ по любви

A request isn’t lost even if Telegram doesn’t respond

Each request is saved first and only then sent to Telegram. If sending fails, the customer’s name and phone number are already stored, and the next request also retries the undelivered ones. The site’s response distinguishes three outcomes: delivered; not delivered but saved; not saved — and only in the last case is the visitor offered a fallback through the VK community.

At first a Cloudflare Worker did this. After the move to Russian hosting, a PHP handler follows the same scheme: write to disk, then Telegram, then retry.

• ff5747f storage and retries ↗
• 9cb5e78 PHP request handler ↗

Online payment was dropped in favour of a request

At first the site had a cart and a demo payment flow modelled on YooKassa. The server calculated the total from its own catalogue, while the browser only sent items and quantities, so the price couldn’t be tampered with in the request.

Later, payment on the site was dropped: customers pay by bank card transfer or in cash. The “Pay” button and the client-side payment code were removed, the cart now sends a regular request the same way as the forms on the home page, and email is no longer required — it was only needed for the receipt.

• e787844 prices, cart, demo payment ↗
• 0530856 payment removed ↗

Mobile layout: bugs you can’t see on desktop

Blocks overflowed the right edge by 32px at every width: when the tokens were moved to a separate file, the global box-sizing reset went missing, and overflow-x: clip hid the overflow so well that the “is there horizontal scrolling” check stayed silent. It was caught in a screenshot — the form switcher was cut off on the right.

In the same pass, input text went from 15.5 to 16px, because below that iOS Safari zooms the page when a field gets focus. Buttons, tabs and footer links got a minimum 44px tap target.

• 72df44e mobile layout ↗

The consent checkbox wouldn’t tick at 393px

The form silently refused to submit because the consent checkbox wouldn’t tick. The cause was an earlier tap-target fix: the policy link sat inside the label, its hit area had been enlarged to 30px on a 17px line and overlapped neighbouring lines — Chromium snapped the tap to the link. At 360 and 375px everything worked; it depended on how the lines wrapped.

The link was moved out of the sentence onto its own line with its own 44px target, so the whole label belongs to the checkbox. Verified by tapping six points of the label at each width.

• 0530856 requests from phones get through ↗

The site editor lives in the same Telegram bot

The bot that delivers requests can also edit the site through a button menu: 40 text fields, 6 links and 14 photo slots — contacts, product names and prices, reviews, section captions. Only the owner has access.

The original texts stay in the HTML; the bot stores only the edits on top of them, and the page applies them on load. So an unavailable server doesn’t leave empty gaps, and search engines see the real text. After the move, the edits are still stored on the old server, but form data no longer goes there.

• 899f38b editor in the bot ↗

Wedding photos: from 19.1 MB down to 2.4 MB

Fourteen source photos weighed 19.1 MB, one PNG alone 5.8 MB. A PowerShell script makes two copies of each: 800px for grid tiles and 1600px for full-screen viewing, rotates frames according to EXIF and writes their dimensions to a manifest. Thanks to srcset, the browser loads only the light copies into the grid, and width and height reserve space in advance so the tiles don’t jump while loading.

• 461279b gallery ↗

A custom domain and deployment without manual uploads

The site moved to asiyatort.ru and REG.RU hosting. After a push to main, GitHub Actions deploys the files over FTPS — the password isn’t sent in plain text, credentials live in repository secrets, and deployment itself is switched on by the DEPLOY_ENABLED variable. The old server’s source code, utility scripts and the demo payment never reach the hosting.

One more detail surfaced after the move: PHP only sees multiple files under the name refs[], but the form sent refs, so reference photos weren’t arriving. The handler now accepts both and notes in the request which photos failed to upload.

• 96899e3 FTPS deployment ↗
• db2fc7e photos reach Telegram ↗