Unsupervised/unsupervised-scheduler
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 12 Wiki Activity

Block options for login/booking link targets with optional auto-redirect #52

Merged
thatguygriff merged 1 commits from feature/block-link-targets into main 2026-07-05 19:19:31 +00:00
Conversation 0 Commits 1 Files Changed 13
+848 -53
1 Commits
Author SHA1 Message Date
thatguygriffandClaude Fable 5 9d89bc6d0e Add link-target and auto-redirect options to booking/login blocks
CI / Coding Standards (pull_request) Successful in 51s
Details
CI / No Debug Code (pull_request) Successful in 3s
Details
CI / Tests (PHP 8.2) (pull_request) Successful in 50s
Details
CI / Tests (PHP 8.3) (pull_request) Successful in 1m2s
Details
CI / Build Plugin Zip (pull_request) Has been skipped
Details
CI / Tests (PHP 8.1) (pull_request) Successful in 53s
Details
CI / PHPStan (pull_request) Successful in 1m24s
Details 
The booking block gains a loginPageId attribute choosing which page its
logged-out "log in to book a lesson" link points to (default remains the
WordPress login screen), and the student-login block gains a
bookingPageId attribute controlling the logged-in "View available
lessons" link and the post-login redirect target (default remains the
current page). Both blocks also gain an autoRedirect toggle, off by
default, that sends the visitor straight to the target page; block
rendering starts after output, so the redirect runs on
template_redirect by parsing the queried page's content for the block,
with a self-target guard against redirect loops. The link targets are
also available to the shortcodes as login_page_id/booking_page_id.

Also fixes a pre-existing fatal: WordPress passes an empty string (not
an array) to shortcode callbacks when a shortcode is used without
attributes, so bare [us_booking] etc. threw a TypeError against the
strictly-typed render(array $atts) methods. ShortcodeRegistrar now
wraps each callback to normalize non-array attribute values.

Closes #51

Co-Authored-By: Claude Fable 5 <[email protected]>
 2026-07-05 16:16:52 -03:00