Berestov Element Scheduler
| 开发者 | andreyberestov |
|---|---|
| 更新时间 | 2026年4月20日 14:18 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Berestov Element Scheduler replaces the inner HTML of selected frontend elements by schedule.
It can match a parent element by class or ID and replace everything inside that parent with the value you define.
Supported schedule groups:
- Weekdays
- Odd and even month days
- Odd and even ISO weeks
- Persistent replacement
- Unlimited rules
- Search by class or ID
- Class mode works across all matched elements
- Multiple different rules per schedule slot
- Duplicate prevention inside the same slot
- Server-side, JavaScript, or Auto replacement mode
- UTC offset based switching
- Drag and drop schedule UI
- Translation-ready admin UI
- Rotate phone numbers
- Schedule banners
- Switch promo blocks
- Replace HTML snippets by schedule
- Capability checks and nonce validation for all administrative actions.
- Strict sanitization and option whitelisting for all saved settings.
- Only explicitly allowed configuration fields are accepted.
- HTML output follows WordPress capability rules (unfiltered_html).
- The plugin does not contact external services or third-party APIs.
安装:
- Upload the plugin folder to
/wp-content/plugins/. - Activate the plugin through the Plugins screen in WordPress.
- Open
E Schedulerin the admin menu. - Create one or more rules.
- Drag rules into the required schedule box.
- Save settings.
屏幕截图:
常见问题:
Does it replace only plain text?
No. It can replace the full inner HTML of the matched parent element.
If I use class mode, does it replace every matched element?
Yes. Class mode replaces all frontend elements that contain the selected class.
Can one slot contain many rules?
Yes. Each slot can contain many different rules, but the same rule cannot be added twice to the same slot.
What happens if one rule is assigned to several schedule groups?
The rule becomes active when any assigned condition matches. It is applied once per request.
Which mode should I use?
Server-side mode uses PHP replacement only and avoids visual flicker. JavaScript mode is suitable for sites that use full page caching. Auto mode prefers server-side output and lets JavaScript correct stale cached markup when needed.
更新日志:
1.0.34
- Removes literal \n tail markers from Auto footer script output.
- Adds a W3C Validator hint for DOM-sensitive homepages.
- Adds checker-friendly probe token handling and refines DOM rewrite debug highlighting.
- Reorders the replacement mode help text to match the current mode order.
- Simplifies DOM rewrite compatibility checks to compare the full home page skeleton using div/nav/ul/menu tags only.
- Adds a small debug view to the DOM rewrite help tip showing before/after structure sequences.
- Switches DOM compatibility checks to a cache-resistant POST probe.
- Reduces false positives on cached sites during dry detection.
- Limits DOM rewrite compatibility updates to the dry settings probe only.
- Prevents runtime requests from overwriting the compatibility status.
- Refreshes DOM rewrite compatibility checks on each settings page load and runs them in a dry pass without applying active rules.
- Adds small help tips for Site charset, mbstring, and DOM rewrite compatibility.
- Improves DOM rewrite compatibility detection by comparing full document structure (tag skeleton) on the home page.
- More reliably detects themes sensitive to DOM normalization and safely restricts them to JavaScript mode.
- Refines environment checks and removes intermediate detection logic for a cleaner and more stable behavior.
- Restored readable UTF-8 page source in server/auto mode after DOM-based replacement by decoding numeric entities in serialized HTML.
- Switched DOM HTML loading to a UTF-8-safe path that avoids injecting an XML preamble into serialized Server and Auto output.
- Preserved the existing replacement flow while reducing the chance of malformed cached page source.
- Reconfirmed compatibility with WordPress 4.8+.
- Tightened full-document output cleanup after DOM serialization to remove stray XML preambles before cached HTML is served.
- Reconfirmed compatibility with WordPress 4.8+.
- Switched head and JavaScript footer runtime script delivery to WordPress script APIs.
- Preserved Auto mode footer injection flow for cached-page recovery and dual delivery behavior.
- Confirmed the renamed build does not register legacy custom REST routes.
- Paired frontend output buffering with an explicit shutdown close path.
- Moved inline client payload and runner output through late escaping.
- Synced the plugin version metadata after the rename.
- Fixed JavaScript and Auto mode time context calculation so schedule switching follows the configured plugin GMT offset without applying the browser timezone twice.
- Keeps Server mode schedule context unchanged.
- Restored JavaScript mode after 1.0.7 by removing the escaping change that stripped inline client scripts.
- Kept the menu label and readme security summary.
- Escaped inline client payload and runner output to satisfy WordPress coding standards checks.
- Renamed the admin menu label to E Scheduler.
- Added a short security summary to the readme.
- Kept Server mode PHP-only by registering client payload and runner hooks only for JavaScript and Auto modes.
- Clarified admin and readme mode descriptions so Server and Auto stay conceptually distinct.
- Added a stronger inline payload and runner fallback between head and footer for JavaScript and Auto modes.
- Kept Server mode unchanged.
- Rebased JavaScript replacement on the stable 1.0.0 approach and added full schedule data for cache-safe client-side evaluation.
- Fixed JavaScript time context calculation so browser timezone differences do not break schedules that use the plugin GMT offset.
- Stabilized Auto mode by reapplying current rules in the browser using the same client-side schedule engine.
- Restored working JavaScript replacement while keeping schedule evaluation inside the browser for cached pages.
- Simplified the JavaScript schedule engine so active rules are computed directly from saved rules and schedule groups.
- Kept Auto mode cache-safe by restoring server-replaced markup only when the current active rule set differs from the cached markup.
- Fixed a JavaScript mode regression where client-side replacement could stop applying.
- Added a safe fallback that preserves same-context JavaScript replacement while keeping cached-page schedule correction.
- Hardened Auto mode behavior for cached pages.
- Made JavaScript mode schedule-aware on cached pages by evaluating rules in the browser.
- Added Auto mode with server-side output plus JavaScript correction for stale cached markup.
- Refined admin mode descriptions for caching-related behavior.
- Added current-slot markers for weekday and parity schedules.
- Fixed persistent replacement activation.
- Final repo-ready release.
- Added a compact wallet reveal button in the admin footer.
- Refined the readme tags, upgrade notice, and wording.
- Clarified rule editor labels for parent matching and inner content replacement.
- Added persistent replacement schedule box.
- Added automatic "(copy)" suffix to copied rules.
- Kept duplicate-safe rule activation across overlapping schedule groups.
- Refined button styling and admin footer donation note.
- Fixed plugin checker issues around textdomain loading, nonce flow, and translators comments.
- Added support for multiple different rules per weekday.
- Prevented duplicate placement of the same rule inside one day.
- Kept class replacement working across all matched elements.
- Updated calendar UI for multi-rule days.
- Updated readme and translation template.
- Added translation template.
- Improved rule drag and drop behavior.
- Added compact collapsed rule layout.
- Added per-rule save buttons.
- Added rule removal from the calendar.
- Polished admin UI and readme.
- Initial public build.