=== Cycle Block – Rotate & Schedule Content Variations === Contributors: ghostlabs Donate link: https://theghostlab.io Tags: content rotation, scheduled content, testimonials, gutenberg, rotating content Requires at least: 6.4 Tested up to: 7.1 Requires PHP: 8.1 Stable tag: 2.0.2 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Rotate content variations on a schedule — daily, weekly or monthly. Rendered server-side, so there's no flicker or layout shift. == Description == Write several versions of a section once, and let the page show a different one over time. A testimonial that changes every week. A hero message that rotates each month. A call to action that differs every day. You write the variations in the block editor, choose how often they change, and the page takes it from there. **How it works** Add a **Cycle** block, then add a variation inside it for each version you want. Anything can go in a variation — headings, images, buttons, columns, other blocks. Pick an interval, and that is the whole setup. * **Daily, weekly or monthly** rotation. * **Shuffle**, so a full pass shows every variation before any repeats. * **Sequence**, if you want them in the order you wrote them. * **Repeat**, or stop on the last variation once the cycle has run through. * **Preview from the editor**, stepping through every variation without waiting for the schedule and without disturbing what visitors see. * **Unlimited variations** per block, and as many blocks as you like per page. **Rendered on the server, which matters more than it sounds** The variation is chosen before the page is sent to the browser. Only one is ever in the HTML. * **No flicker and no layout shift.** Nothing swaps after the page has painted, so the block never causes the jump that hurts Core Web Vitals. * **No hidden duplicate content.** Search engines see one variation, not all of them stacked in the markup with the rest hidden by CSS. * **No JavaScript required** to choose or display a variation. * **Nothing is written into your post content**, so your saved posts do not change as the schedule advances. **Built to behave** * Every variation is real block content, so it inherits your theme's colours, typography and spacing rather than fighting them. * The schedule is tracked per block *and* per post, so duplicating a page gives the copy its own schedule instead of sharing one. * If anything goes wrong — a missing schedule, a plugin conflict — the block falls back to showing its content rather than breaking the page. * Built to WCAG 2.2 AA and fully translatable. == Installation == 1. Install through the **Plugins** screen, or upload the plugin folder to `/wp-content/plugins/`. 2. Activate it through the **Plugins** screen. 3. In any post, page or template, add the **Cycle** block, then add a variation inside it for each version of the content you want. == Frequently Asked Questions == = How does it decide which variation to show? = Each block keeps a queue. When enough time has passed for the interval you chose, the next variation in the queue is handed out and the queue moves on. With shuffle on, the queue is reshuffled at the start of each pass, so every variation appears once before any repeats. = What happens if nobody visits for a while? = The block moves on by one variation, not by however many intervals were missed. A page nobody visited for a month does not skip a month's worth of content the next time someone arrives. = I use a caching plugin. Will variations still rotate? = This is the one thing worth checking. A full-page cache stores the finished HTML, chosen variation included, so the rotation effectively runs at your cache's expiry rather than at the interval you set. If your cache lifetime is shorter than your interval — a daily cache with a weekly rotation, for example — everything behaves as expected. If it is longer, either shorten the cache lifetime for those pages or lengthen the interval to match. = Does it work with any block? = Yes. A variation is an ordinary block container, so it can hold headings, paragraphs, images, buttons, columns, groups, and blocks from other plugins. = What happens to my page if the plugin is deactivated? = Every variation shows, one after another, as ordinary content. Nothing is lost and nothing breaks — your content was never stored anywhere but in the post itself. = I duplicated a page. Do both copies share a schedule? = No. The schedule is keyed to the block *and* the post, so a duplicate starts its own. = Does this do A/B testing? = Not in the statistical sense — it rotates content on a schedule rather than splitting traffic and measuring significance. If you want to know which variation performs, the Pro edition adds Custom Events — a view event, and an optional click event, for every event you define; this edition rotates, it does not measure. = Why does it need PHP 8.1? = The plugin is built on modern PHP. Most hosts have offered 8.1 or newer for some time, and your host's control panel will show which version your site runs. Earlier releases of this plugin ran on PHP 7.4, which has been unsupported since 2022. = I bought Cycle Block Pro. How do I switch this site to it? = On a single site, open Settings → Cycle Block, click "Have a license?", and paste the license key from your receipt email. The plugin verifies the key, installs Cycle Block Pro, and deactivates itself — your blocks, schedules and settings carry over untouched, and your key carries over with them, so you never enter it twice. If any step fails, nothing on your site has changed, and you can always install Cycle Block Pro manually from your account page instead. On a WordPress multisite network the in-place switch does not run, and the settings screen says so rather than asking for a key: a network administrator installs Cycle Block Pro from the network admin, and the license key is entered on each site. Your blocks, schedules and settings carry over untouched either way. == External services == This plugin contacts GhostLabs' licensing service in exactly one situation: when you start the upgrade to Cycle Block Pro from the settings screen — by submitting a license key, or by clicking "Complete upgrade" after a purchase. It sends the license key you entered (or the one-time claim token from your purchase), this site's domain name, the plugin's slug and the edition being requested, so the service can verify the license and deliver the Cycle Block Pro package. Nothing is sent on any other page load, and nothing is ever sent without that explicit action. The service is operated by GhostLabs. [Terms of service](https://theghostlab.io/terms-of-service) · [Privacy policy](https://theghostlab.io/privacy-policy) == Source code == The plugin's compiled JavaScript is built from readable sources, and both are published together at: https://github.com/theghostlab/wp-ghostlabs-cycle-block-lite That repository contains this plugin exactly as distributed, plus the uncompiled `src/` and `dev/` behind its bundles and the configuration used to build them. Every dependency is a public package, and the one GhostLabs library the plugin uses is carried as readable source inside it (`lib/wp-kit/`, GPL-2.0-or-later) — so `composer install && pnpm install && pnpm run build` needs no credentials of any kind and reproduces the shipped `build/`, `assets/js/` and `assets/css/settings.css` byte for byte. == Screenshots == 1. Three versions of one hero, written once and named. Pick the schedule — daily, weekly or monthly — choose shuffle or sequence, repeat or stop on the last one, and preview every variation from the editor without waiting for the clock. 2. A variation is ordinary block content — a Cover, headings, buttons, columns, anything — so it inherits your theme. The Custom Events panel shows what Pro adds: a view event, and an optional click event, for every event you define, sent to Google Analytics 4, Matomo, Plausible or Umami. 3. Chosen on the server before the page is sent. One variation is in the HTML, so there is no flicker, no layout shift, and no hidden duplicate content for search engines to find. 4. Nine schedules in the list; this edition honours three. Pick a Pro one and the block says so, names the schedule it is still cycling on, and changes nothing. 5. Settings → Cycle Block: where your controls live, the license entry, and what Pro adds beside what you already have. 6. Upgrade in place on a single-site install. Paste a license key and the site switches to Pro with every block, schedule and setting exactly as it was. == Changelog == = 2.0.2 = The relaunch release. WordPress.org last published 1.0.4, so everything listed under 1.2.0 and 1.1.0 below reaches sites for the first time in this version, together with: * Choosing a schedule this edition does not include now says so in the editor, names the schedule the block is still cycling on, and changes nothing; the server enforces the same range, so no client-side edit can widen it. * A security review against the OWASP Top 10 and an accessibility review to WCAG 2.2 AA, with every finding fixed. * Multisite: the in-place upgrade is offered only where it can actually be performed. * The JavaScript and CSS ship readable and unminified, and the published source repository rebuilds them byte for byte. = 1.2.0 = * New: upgrade to Cycle Block Pro in place. Enter a license key under Settings → Cycle Block — or complete a purchase and click one button — and this site switches editions with every block, schedule and setting exactly as it was. See the "External services" section for precisely what is sent, and when. * New: the settings screen now explains what the plugin stores and where its controls live, holds the license entry, and shows what the Pro edition adds beside what you already have. * New: Docs and Support links on the plugin's row of the Plugins screen. * The published source repository now builds with no credentials of any kind: the one GhostLabs library the plugin uses is carried inside it as readable GPL source (`lib/wp-kit/`). = 1.1.0 = * Rebuilt on the codebase GhostLabs develops Cycle Block from, so this edition now receives the same fixes as the Pro edition instead of lagging behind it. * Accessibility pass to WCAG 2.2 AA across the editor interface. * The whole plugin is now translatable, and translations from WordPress.org are picked up automatically. * The front-end stylesheet is loaded only on pages that actually use the block, instead of on every page of the site. * Fixed: a block whose queue had run out could log a PHP warning on the front end. * Fixed: rendering over the REST API no longer advances the schedule — a request that is not a page view should not consume a variation. * **Requires PHP 8.1** (previously 7.4). == Upgrade Notice == = 2.0.2 = Requires PHP 8.1 or newer; sites on an older version will not be offered this update. Adds the in-place upgrade to Cycle Block Pro and a rebuilt settings screen. Nothing about how your content rotates changes, and nothing is sent anywhere unless you start the upgrade yourself. = 1.2.0 = Adds the in-place upgrade to Cycle Block Pro and a rebuilt settings screen. Nothing about how your content rotates changes, and nothing is sent anywhere unless you start the upgrade yourself. = 1.1.0 = Requires PHP 8.1 or newer; sites on an older version will not be offered this update. Every feature you had is still here. Your content is unaffected: variations live in your posts, not in the plugin.