Briskgrid Class Timetables is a visual, drag-and-drop grid builder for gym and studio class timetables. Build your schedule by dragging classes onto a real calendar grid \u2014 every column stays perfectly aligned automatically, and the front-end grid is fully responsive, collapsing into a clean list on mobile.<\/p>\n\n
Free features<\/strong><\/p>\n\n Briskgrid Class Timetables Pro<\/strong> (sold separately) adds instructor photos and bios, a front-end filter bar (by day \/ instructor \/ category), multiple color-coded categories, extra style presets, multi-location grouping, and custom CSS.<\/p>\n\n\n The timetable's class content is not managed under Polylang's ordinary Strings translations<\/strong> screen. The Yes. The front-end grid uses standard CSS Grid and inherits your theme's fonts; only layout and color are set by the plugin.<\/p><\/dd>\n Yes, the free version supports unlimited timetables \u2014 for example, one per location or room.<\/p><\/dd>\n Not currently. Briskgrid Class Timetables focuses on displaying a clear, good-looking schedule. Booking\/reservation support may be considered for a future release.<\/p><\/dd>\n Yes. Plugin interface text uses the Polylang does not list the timetable's class names as ordinary Strings Translations because they are timetable content rather than plugin UI strings.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
[briskgrid_timetable id=\"123\"]<\/code> and a native Gutenberg block<\/li>\nbriskgrid-class-timetables<\/code> text domain and ship with a .pot<\/code> file (languages\/briskgrid-class-timetables.pot<\/code>) for translation tools such as Poedit or Loco Translate<\/li>\nwpml-config.xml<\/code> included) \u2014 timetable content is translated per language while display settings can remain shared<\/li>\n\n
\/wp-content\/plugins\/briskgrid-class-timetables<\/code>, or install through the Plugins screen.<\/li>\nMultilingual sites with Polylang<\/h4>\n\n
\n
.pot<\/code> 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.<\/p>\n\n\n\n
Does this work with any theme?<\/h3><\/dt>\n
Can I have more than one timetable?<\/h3><\/dt>\n
Does it support bookings or reservations?<\/h3><\/dt>\n
Is Briskgrid Class Timetables translation-ready?<\/h3><\/dt>\n
briskgrid-class-timetables<\/code> text domain and a .pot<\/code> file is included for translation tools and WordPress language packs. Timetable content is separate: when Polylang is active, use the Language \/ Translations<\/strong> column in Briskgrid Class Timetables \u2192 All Timetables<\/strong> 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.<\/p>\n\n1.1.0<\/h4>\n\n
\n
[briskgrid_timetable id=\"123\"]<\/code>. No stored data, settings, or internal code structure changed \u2014 this is a naming update only, made before the plugin has any live installs.<\/li>\n<\/ul>\n\n1.0.9<\/h4>\n\n
\n
sanitize_text_field()<\/code> before display, in addition to the existing output escaping.<\/li>\n$_GET<\/code> reads used only to choose what to display (no state change) as intentionally not nonce-checked; annotated the guarded seems_utf8()<\/code> 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.<\/li>\n<\/ul>\n\n1.0.8<\/h4>\n\n
\n
gct<\/code>\/GCT<\/code> to gymcla<\/code>\/GYMCLA<\/code> throughout (function, class, hook, and meta-key names). This is not a user-facing change \u2014 the shortcode, text domain, and all saved data are unaffected \u2014 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.<\/li>\n<style><\/code> tag instead of being enqueued properly.<\/li>\ngymcla_entry_data_attrs<\/code> filter) is now re-validated and re-escaped before output, regardless of what a hook returns.<\/li>\nseems_utf8()<\/code> calls (CSV import, Tools backup import) with a small wrapper that prefers WordPress's newer wp_is_valid_utf8()<\/code> when available.<\/li>\n1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n