| 开发者 | luka113 |
|---|---|
| 更新时间 | 2026年6月30日 15:37 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[tymeslot username="you" mode="inline"] in any post, page, or widget.embed.js from the Tymeslot instance you choose. On the settings screen, an optional connection check loads your booking page in a preview so you can confirm embedding works. The plugin makes no external request until you set a booking username, and it never sends your data anywhere other than the Tymeslot instance you configure.
If you use the managed cloud, your use is subject to Tymeslot’s terms and privacy policy:
[tymeslot] shortcode.Almost always the domain allowlist. For security, Tymeslot only allows your booking page to be embedded on domains you approve. In your Tymeslot dashboard go to Embed → Security, add your WordPress site’s domain, and save. The live embedding status on the plugin’s Setup tab loads your real booking page and tells you, in the browser, exactly whether this site is allowed. Until the domain is allow-listed, the plugin shows a short “booking is currently unavailable” message in place of the booker — it deliberately never lets the Tymeslot homepage render inside your page. Logged-in administrators also see a hint pointing to Embed → Security.
No. Core scheduling on Tymeslot is free, and this plugin works with free and Pro accounts alike.
Yes. On the Setup tab choose Self-hosted and enter your instance URL. Switch back to Cloud any time — everything else behaves the same.
In your Tymeslot account — never in WordPress. The plugin only stores your local settings (instance URL, username, and default appearance).
Yes. Choose a theme (Quill or Rhythm), pick a layout (column or centred), and a language. Set defaults once on the Setup tab, or override them per block/shortcode. Your brand colour is set in your Tymeslot account and is applied to the booker automatically.
No. The lightweight embed runtime loads only on pages that actually contain a Tymeslot block or shortcode.
The inline embed and the direct link work under a strict CSP — they only add a <div>/<a> plus an external script you already allow via script-src. The popup and floating button modes use a small inline onclick/<script> to open the booker, so they need 'unsafe-inline' in your script-src (or a matching nonce/hash) to run. If you enforce a strict CSP without 'unsafe-inline', prefer the inline or link mode.
Development happens in the open. The full, un-minified source — including the Gutenberg block sources under src/ and the build tooling — lives at https://github.com/Tymeslot/tymeslot-wordpress. The compiled files under build/ shipped here are generated from it with @wordpress/scripts (npm run build).
[tymeslot] shortcode.