| 开发者 | ssplugins |
|---|---|
| 更新时间 | 2026年10月6日 23:53 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[briskgrid_timetable id="123"] and a native Gutenberg blockbriskgrid-class-timetables text domain and ship with a .pot file (languages/briskgrid-class-timetables.pot) for translation tools such as Poedit or Loco Translatewpml-config.xml included) — timetable content is translated per language while display settings can remain shared/wp-content/plugins/briskgrid-class-timetables, or install through the Plugins screen..pot file and WordPress language packs are for translating Briskgrid Class Timetables interface text; the timetable content itself is edited in the language-specific Briskgrid Class Timetables builder.Yes. The front-end grid uses standard CSS Grid and inherits your theme's fonts; only layout and color are set by the plugin.
Yes, the free version supports unlimited timetables — for example, one per location or room.
Not currently. Briskgrid Class Timetables focuses on displaying a clear, good-looking schedule. Booking/reservation support may be considered for a future release.
Yes. Plugin interface text uses the briskgrid-class-timetables text domain and a .pot file is included for translation tools and WordPress language packs. Timetable content is separate: when Polylang is active, use the Language / Translations column in Briskgrid Class Timetables → All Timetables to assign a language and create linked language versions. Each language version has its own class names, instructors and locations, while the timetable layout can be copied from the source. On the front end, the shortcode or Gutenberg block automatically resolves to the version matching the current language.
Polylang does not list the timetable's class names as ordinary Strings Translations because they are timetable content rather than plugin UI strings.
[briskgrid_timetable id="123"]. No stored data, settings, or internal code structure changed — this is a naming update only, made before the plugin has any live installs.sanitize_text_field() before display, in addition to the existing output escaping.$_GET reads used only to choose what to display (no state change) as intentionally not nonce-checked; annotated the guarded seems_utf8() fallback as an intentional compatibility path; prefixed the uninstall script's variable names; clarified that unprefixed variables in included admin view templates are local render-context values, not globals.gct/GCT to gymcla/GYMCLA throughout (function, class, hook, and meta-key names). This is not a user-facing change — the shortcode, text domain, and all saved data are unaffected — but was made now, before the plugin has any live installs, in response to review feedback that a 3-letter internal prefix is too short to reliably avoid collisions with other plugins.<style> tag instead of being enqueued properly.gymcla_entry_data_attrs filter) is now re-validated and re-escaped before output, regardless of what a hook returns.seems_utf8() calls (CSV import, Tools backup import) with a small wrapper that prefers WordPress's newer wp_is_valid_utf8() when available.