'administrator', 'number' => 1, 'fields' => 'ID' ) ); if ( empty( $admins ) ) { fwrite( STDERR, "No administrator to run as.\n" ); exit( 1 ); } wp_set_current_user( (int) $admins[0] ); if ( ! current_user_can( 'manage_options' ) ) { fwrite( STDERR, "Could not acquire manage_options.\n" ); exit( 1 ); } /** * Every tab that renders a settings form. A tab added to the strip and not added * here is not covered — which is how a new tab ships with a stale skip list and * quietly resets somebody else's settings on its first save. */ $tabs = array( 'journeys', 'handoff', 'settings', 'events', 'other', 'targets' ); /** * Tabs that MUST post something. Without this, a tab whose form stopped rendering * — a moved section, a typo'd slug, a renderer that returns early — reports "no * option inputs, skipped" and the run still passes, which is the same false green * as not testing it at all. */ $must_post = array( 'journeys', 'handoff', 'settings', 'events', 'other', 'targets' ); /** * Settings that USED to exist and deliberately no longer do. * * A retired key stays in the stored option — deleting a site's saved data for a * cosmetic change is not warranted — but the sanitizer stops emitting it, so the * comparison below sees it disappear and would report it as damage on every tab * forever. Listing it here says "expected", and the check is inverted: a retired * key that comes BACK in the sanitizer's output is the failure, because that means * the removal was undone by half. */ $retired = array( // 1.8.0 — the source/medium separator is a constant now. 'source_medium_separator', ); /** * Settings that are still STORED and still read, but that no screen may edit or even * carry any more. * * `self_referral_hosts` is the retired owned-properties list. Its value is preserved — * it is folded into the `internal` row of Medium Mappings at read time, so deleting it * would delete a site's other owned properties — but it has no editor, and a hidden * pass-through would be a form field posting a value nobody can see. Worse, leaving one * in makes "is this setting gone from the UI?" impossible to answer by looking. The * assertion is therefore two-sided: no tab renders an input for it, AND the value * survives every save anyway (which the round-trip comparison below already proves, * because it is in $original and must still be in $saved). */ $no_control = array( 'self_referral_hosts' ); $original = BW_Lead_AI_Settings::get(); $failures = array(); /** * Settings a tab renders in a DERIVED form rather than exactly as stored, and the * value a save from that tab is therefore expected to write. * * `referrer_classification` gains its `internal` row at read time on any site * configured before that row existed — see * BW_Lead_AI_Settings::referrer_classification_text(). The Settings tab renders the * derived text on purpose: deriving instead of migrating the option is what puts the * row in front of the owner and makes their own save the thing that commits it. So on * that tab "the value changed" is the designed behaviour, once. * * The check is re-based, not waived. The saved value must equal the derived text * EXACTLY, a second pass must be a no-op (asserted below), and every other tab must * still write the stored value untouched — a pass-through that started rewriting a * setting it only carries would be the bug this file exists to catch. * * Tab => setting => the value that tab is expected to store. */ $derived_on = array( 'settings' => array( 'referrer_classification' => BW_Lead_AI_Settings::referrer_classification_text( $original ), ), ); // Idempotence, checked here rather than trusted: if deriving twice moved, every save // from the Settings tab would move it again and the option would never settle. foreach ( $derived_on as $tab_name => $map ) { foreach ( $map as $key => $value ) { $again = BW_Lead_AI_Settings::referrer_classification_text( array_merge( $original, array( $key => $value ) ) ); if ( $again !== $value ) { $failures[] = sprintf( '[%s] %s: derivation is not idempotent', $tab_name, $key ); } } } /** * The `label : value, value` settings are edited as rows, and the rows are the * fields most easily lost by accident: their names are two levels deep * (`option[channels_key][0]`), which is the deepest shape the scraper above can * see. Rename them one level deeper and every one of them silently stops being * scraped — the sanitizer then falls back to the textarea or the default and the * test above would still pass on any setting that happens to equal its default. * * So each of these is checked for presence and for row count, not just for * "nothing moved". Tab => settings whose rows that tab must post. */ $row_editors = array( 'settings' => array( 'parameter_aliases', 'referrer_classification', 'click_ids', 'channels', 'channel_groups' ), 'events' => array( 'event_custom_selectors' ), ); /** * Settings a tab must render a REAL, editable control for — not a hidden * pass-through. * * The round-trip check above cannot tell the difference: a checkbox that is off * and a hidden pass-through carrying 0 both come back as 0, so a tab that lost * its controls entirely still round-trips perfectly while being useless. This is * what makes a tab genuinely covered rather than merely rendered. * * Tab => settings whose editable input that tab owns. */ $owned_controls = array( 'other' => array( 'debug', 'capture_ga_client_id' ), // `journey_save_mode` is a CHECKBOX, which is the shape this list exists for: // unticked it posts nothing, so it rides with a `journey_save_mode_present` // marker and the sanitizer reads the pair. If the control ever vanished, the // marker alone would post and every save would write 'confirm' — a silent // switch-off of journey storage on every submission-mode site. 'journeys' => array( 'journey_save_mode' ), // Same shape again, twice. Both milestone lists are switched by a checkbox // whose OFF state is an empty list, and an unticked box posts nothing — so // each rides with a hidden `*_present` marker. The CHECKBOX is what is // asserted, not the marker: if the box vanished the marker would still post // on its own and every save of this tab would silently switch the milestones // off, which is precisely the failure the round-trip cannot see on a site // that has them off already. 'events' => array( 'video_marks_on', 'scroll_marks_on' ), ); /** * Settings whose stored value may legitimately be EMPTY, checked against a save * that omits them. * * The round-trip alone cannot see this one. `sanitize()` falls back for a key the * POST does not carry, and if that fallback is the shipped default then a setting * the owner deliberately emptied comes back on — while the comparison still * passes on every site whose stored value happens to equal the default, which is * most of them. Every tab carries these through hidden today, so this is a guard * on the fallback rather than on the tabs. */ $may_be_empty = array( 'event_video_milestones', 'event_scroll_thresholds', 'event_downloads', 'event_social_hosts' ); /** * The one setting stored as a nested array, and the tab that owns its editor. * * `field_targets` is a row per entry in BW_Lead_AI_Merge_Tags::available_tags() — * a set that varies per site, since it includes that site's custom dimensions and * its enabled interaction types. So "did the tab render its editor" cannot be a * count of six any more; it is "did it render a row for every tag this site has". * * Checked because the round-trip comparison alone cannot see it. An empty mapping * is not stored, so a screen that rendered NO rows at all would post nothing, * sanitize would return exactly what was stored, and the tab would pass while * being blank. * * Tab => the nested setting it must post a complete set of rows for. */ $nested_editors = array( 'targets' => 'field_targets', ); /** Render a tab and return the HTML it produced. */ function bwlai_render_tab( $tab ) { $_GET['page'] = BW_Lead_AI_Admin::PAGE_SLUG; $_GET['tab'] = $tab; unset( $_GET['wizard'] ); ob_start(); BW_Lead_AI_Admin::instance()->render_page(); return (string) ob_get_clean(); } /** * Pull the inputs a browser would submit for our option out of rendered HTML. * Only successful controls: unchecked boxes are omitted, exactly as a form posts. */ function bwlai_scrape_post( $html ) { $option = BW_LEAD_AI_OPTION; $post = array(); //