Fine on your screen. Broken on theirs.
Theme tickets live in the customer's setup: their plugins, their version, their phone. Repile rebuilds all three in a sandbox and taps the button itself.
Stop asking for a screenshot and a plugin list.
Repile copies the site into a private sandbox with the same WordPress version, PHP version, theme and plugins. Then it opens the page on the screen size the customer used. The live site is never touched.
- Copied the site into a sandbox1m 12s
- WordPress 6.6.2 · PHP 8.2 · 31 plugins8s
- Opened checkout on an iPhone 14 screen4s
- Tapped Place order: nothing happened
- Sticky header covers the button below 430px
Your theme, their plugin or their host. Settled.
Half of theme support is proving it isn't the theme. Repile reproduces the bug, then tells you where it lives, with the file and line to back it up.
Sticky header covers checkout on phones
harbor/header.css:118position: fixed; bottom: 0;
CSS fix tested in the sandbox and put in the draft.
A plugin the customer added overrides your styles
Repile names the plugin and shows the evidence, so the reply doesn't stop at “it's not us”.
It only breaks on their server setup
Repile says so, with the evidence, so the customer knows to take it to their host.
Proof the customer can see.
Every finding comes with screenshots and recordings from real browsers and phone viewports. Fixes are tested in the sandbox before they reach the draft, and you press send.
How site cloning worksQuick answers.
Anything else? Write to [email protected] and a human answers.
Real phone screens?
Real browsers and phone viewports, with screenshots and recordings attached.
Is the live site safe?
Repile works on a private copy. The live site is never touched.
Will it suggest a fix?
Yes, once it's been tested in the sandbox. It goes in the draft.