ultimate-jekyll-manager 1.9.4 → 1.9.6

package/TODO-AUTH-TESTING.md

@@ -1,165 +0,0 @@
-# TODO: Automated Tests for the Auth System
-
-## Why
-
-The consent-guard / `sendUserSignupMetadata` ordering bug that shipped in v1.3.1 (and was fixed in v1.3.2) is exactly the kind of regression that should never reach production. The bug was:
-
-- Page-load consent guard ran BEFORE `sendUserSignupMetadata`
-- Brand-new signups had `consent.legal.status: 'revoked'` (BEM schema default)
-- Guard saw `'revoked'` → signed user out → metadata POST never fired → user permanently orphaned
-
-Discovered only via live testing on Somiibo. Should have been caught by a unit test.
-
-This file proposes a layered test strategy so the next refactor + every future change is safe.
-
-## Strategy: three tiers, mostly mocked
-
-### Tier 1 — Unit (JSDOM + mocked Firebase, fast)
-
-Run from UJM. Add to the existing `test/tests/**/*.test.js` harness. No real Firebase, no network. Covers ~80% of bugs including the v1.3.1 regression.
-
-Files to write:
-
-```
-test/tests/auth-consent-capture.test.js
-  • captureSignupConsent() reads consent-legal + consent-marketing checkboxes
-  • writes the right shape to webManager.storage() under key 'consent'
-  • label text is captured verbatim (so BEM gets the exact string the user saw)
-
-test/tests/auth-consent-validate.test.js
-  • validateConsent() blocks submit when consent-legal is unchecked
-  • surfaces the inline error + wrapper outline
-  • does NOT block submit when both boxes are checked or only marketing is unchecked
-
-test/tests/auth-guard-ordering.test.js   ← THIS WOULD HAVE CAUGHT v1.3.1
-  • on a fresh user (account < SIGNUP_MAX_AGE) with consent.legal.status: 'revoked'
-    → sendUserSignupMetadata is called
-    → guard does NOT sign out
-  • on an old user (account > SIGNUP_MAX_AGE) with consent.legal.status: 'revoked'
-    → guard signs out
-    → notification is shown
-  • on any user with consent.legal.status: 'granted'
-    → guard does NOT fire regardless of age
-
-test/tests/auth-reverse-signup.test.js
-  • reverseAccidentalSignup() calls user.delete() THEN signOut() THEN clears authReturnUrl
-  • formManager.showError fires with the right message
-  • if user.delete() throws, signOut still runs (best-effort)
-
-test/tests/auth-policy-redirect.test.js
-  • policy='authenticated' + no user → redirect to unauthenticated URL
-  • policy='unauthenticated' + user → redirect to authenticated URL (honoring authReturnUrl)
-  • policy='disabled' → no-op
-
-test/tests/auth-metadata-payload.test.js
-  • sendUserSignupMetadata builds the right payload shape
-  • includes consent, attribution, context
-  • skips when account is old or signupProcessed flag is set
-  • sets signupProcessed flag after successful POST
-```
-
-Mocking contract:
-
-```js
-// Mock webManager
-const fakeWebManager = {
-  auth: () => ({ listen, signOut, getIdToken }),
-  storage: () => ({ get, set }),
-  utilities: () => ({ showNotification }),
-  config: { auth: { config: { policy, redirects, roles } } },
-};
-
-// Mock Firebase auth functions
-// - createUserWithEmailAndPassword
-// - signInWithEmailAndPassword
-// - signInWithPopup / signInWithRedirect
-// - getRedirectResult
-// - sendPasswordResetEmail
-// - user.delete()
-// - getAuth().signOut()
-
-// Mock FormManager (or use the real one — it's mockable already)
-const fakeFormManager = { showError, showSuccess, ready, ... };
-```
-
-Approach: load `src/assets/js/core/auth.js` and `src/assets/js/libs/auth.js` into JSDOM
-with all imports stubbed (Jest/Mocha module mocks or rewire). For HTML-aware tests
-(captureSignupConsent), load `src/defaults/dist/_layouts/themes/classy/frontend/pages/auth/signup.html`
-into JSDOM and exercise the real DOM.
-
-### Tier 2 — Integration against Firebase Emulator (slower, optional)
-
-Run from UJM. Boot `firebase emulators:start --only auth,firestore` before the suite.
-Extend the existing `test/fixtures/consumer-site/` with:
-
-- `firebase.json` configured for emulator ports
-- Canned Firebase web config pointing at `localhost:9099` / `localhost:8080`
-- Test user seeding via Admin SDK helpers
-
-Covers: full email-signup round-trip, the storage-survives-redirect path, real
-auth-state-listener firing, real Firestore reads in the guard.
-
-**Skip OAuth at this tier.** Firebase emulator's auth emulator doesn't speak to
-real Google. OAuth tests stay manual (Tier 3).
-
-This is OPTIONAL — only worth building if a bug slips through Tier 1.
-
-### Tier 3 — Manual smoke (don't automate)
-
-Google OAuth + cross-provider webhooks stay manual. Reasons:
-- Google actively blocks scripted browsers (even Puppeteer with stealth plugins)
-- Real 2FA flows
-- Provider UI rolls and tests break
-- Cost/value is terrible
-
-Keep the live-test checklist (see [TODO-CONSENT-LIVETEST.md](TODO-CONSENT-LIVETEST.md))
-as the authoritative manual smoke procedure.
-
-## Where the tests live
-
-Run from UJM. NOT from a host project. Reasons:
-- `core/auth.js` + `libs/auth.js` are owned by UJM
-- Host project tests would re-test framework internals, wrong layering
-- UJM's existing 60-test Mocha harness is already fast (~6s)
-
-Default config (Firebase emulator + a fake brand) baked into
-`test/fixtures/` so contributors don't need their own Firebase project.
-
-## Sequencing
-
-1. **First**: do the libs/auth.js refactor (split into `auth.js` + `auth-providers.js` + `auth-consent.js`).
-   - See the auth-audit findings in this session's notes.
-   - Refactor first means we write tests against the FINAL shape, not throw-away.
-   - Each new file gets a focused test file.
-
-2. **Then**: Tier 1 unit tests for the new shape.
-   - Target: every test file from the list above, green.
-   - Should take ~half a day.
-
-3. **Optional later**: Tier 2 emulator-backed tests, only if Tier 1 misses a class
-   of bugs in practice. Probably won't be needed.
-
-4. **Never**: Tier 3 automation. Stays manual via [TODO-CONSENT-LIVETEST.md](TODO-CONSENT-LIVETEST.md).
-
-## What about Ultimate Jekyll for the test site?
-
-Tempting but NO. Reasons:
-- UJ build is heavy (Jekyll + webpack), test boot would be 10+ seconds
-- Circular dependency risk (UJM testing UJM via UJ which uses UJM)
-- UJM's existing Mocha harness is the right tool
-
-The test harness should stay vanilla Mocha + JSDOM + fixture HTML files.
-
-## What this DOESN'T cover
-
-- Google OAuth UI flows (manual only)
-- Cross-provider unsubscribe webhooks (manual + BEM tests already exist)
-- Beehiiv webhook setup (blocked on plan upgrade; manual when ready)
-- Firebase Auth SDK bugs (not our code, not our problem)
-
-## Done criteria
-
-- All 6 test files above written and green
-- `npm test` in UJM runs them as part of the standard suite
-- The v1.3.1 bug (consent guard ordering) is caught by `auth-guard-ordering.test.js` — verify by reverting the v1.3.2 fix in a branch and watching the test fail
-- Documented in `docs/test-framework.md` so contributors know to add auth tests when touching auth code

package/TODO-BACKEND.md

@@ -1,13 +0,0 @@
-BACKEND TODO
-make the mobile menu toggle appear in place ont he logo/brand (the one on the topbar), not down in the bottom right corner
-
-does it hav eto be aside? or can it be nav? id prefer if it was nav
-
-
-the breadcrumbs at the top are not needed. pelase move them inside the MINIMAL layout. on that note, please design the minimal layout page. it should look liek the screenshot attached with the page.meta.title, then under that is the breadcrumbs, then under that is the page content. on the right side, there is a button
-
-
-ok our dashboard needs some work. just look at the screenshot.
-- the DASHBAORD text is way too huge. the icon next to it is way too small.
-- also, that whole section needs a HR below it or a border or something to separate it from the content below. also, we need to make
-- also, the LOGO section in top left should match the bg color of the sidebar.

package/TODO-CHAT1.md

@@ -1,41 +0,0 @@
-where could we put a small section about how to use the defualt css classes? some come with bootstrap and some come from our core, and some come from the theme. when building websites, we should be using the premde classes not creating copies of custom classes that do the same thing
-
-Looking at the CLAUDE.md structure, I think the best place for a CSS classes section would be after the "CSS Guidelines" section (which currently only covers Theme-Adaptive Classes). We could expand that section or add a new subsection. Let me check what's currently in the CSS Guidelines section and the surrounding context:
-Grep "## CSS Guidelines" (in /Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/CLAUDE.md)
-51 lines of output
-The CSS Guidelines section is currently small (lines 423-443), focusing only on theme-adaptive classes. I'd recommend expanding this section with a new subsection about class hierarchy and usage. Here's where I'd suggest placing it and what it could contain: Suggested location: After "Theme-Adaptive Classes" (line 443), before "Page Loading Protection System" (line 445) Suggested content:
-### CSS Class Hierarchy
-
-When styling elements, always prefer existing classes over creating custom ones. Classes come from three sources (in order of precedence):
-
-**1. Bootstrap Classes (Foundation)**
-Use Bootstrap's utility classes for common patterns:
-- Spacing: `m-*`, `p-*`, `mt-3`, `px-4`, `gap-2`
-- Flexbox: `d-flex`, `justify-content-center`, `align-items-center`
-- Grid: `row`, `col-*`, `container`, `container-fluid`
-- Text: `text-center`, `fw-bold`, `fs-5`, `text-muted`
-- Display: `d-none`, `d-md-block`, `visually-hidden`
-
-**Documentation:** https://getbootstrap.com/docs/5.3/utilities/
-
-**2. UJ Core Classes (Global)**
-Located in `src/assets/css/global/` and `src/assets/css/core/`:
-- Theme-adaptive: `bg-body`, `btn-adaptive`, `text-body`
-- Utilities: (list common ones here)
-
-**3. Theme Classes (Theme-Specific)**
-Located in `src/assets/themes/[theme-id]/`:
-- Theme-specific components and overrides
-
-### Best Practices
-
-**DO:**
-- Search existing classes before creating new ones
-- Use Bootstrap utilities for spacing, layout, typography
-- Use UJ adaptive classes for theme compatibility
-
-**DON'T:**
-- Create `.my-centered-text` when `text-center` exists
-- Create `.my-margin-top` when `mt-3` exists
-- Duplicate functionality that Bootstrap or UJ already provides
-Would you like me to add this section to the CLAUDE.md file? I can also explore the actual CSS files to document the specific UJ core utility classes that are available.

package/TODO-CONSENT-LIVETEST.md

@@ -1,201 +0,0 @@
-# TODO: Consent System End-to-End Live Test Checklist
-
-## Context
-
-End-to-end manual smoke for the marketing-consent + cross-provider-unsub
-pipeline. Run after each new BEM/WM/UJM deploy that touches auth, consent,
-email-preferences, or webhook code paths.
-
-Each step depends on state set up by earlier steps. Run top-to-bottom.
-
-Live test target: **Somiibo** (`somiibo.com` + `api.somiibo.com`).
-Parent BEM: **ITW** (`itwcreativeworks.com` + `api.itwcreativeworks.com`).
-
-## Pre-flight
-
-- [ ] **Use a fresh email** (`consent-test+1@yourdomain.com` or a Gmail alias) so the signup is genuinely new
-- [ ] **Have a separate Google account ready** that has never signed up here (for the reverse-signup test)
-- [ ] **Open multiple browser windows side by side**:
-  - Somiibo signup page
-  - SendGrid Marketing → Contacts
-  - Beehiiv dashboard → Somiibo publication subscribers
-- [ ] **Tail BEM logs in terminal**:
-  ```bash
-  cd /Users/ian/Developer/Repositories/Somiibo/somiibo-backend/functions
-  npx mgr logs:tail
-  ```
-- [ ] **Confirm current package versions live**:
-  - BEM: `^5.2.2`
-  - web-manager: `^4.2.0`
-  - UJM: `^1.3.2`
-- [ ] **Confirm last Somiibo backend + website deploys** were AFTER the BEM/UJM version bumps
-- [ ] **Delete any stale test accounts** from previous attempts:
-  ```bash
-  npx mgr auth:get "<test-email>"     # find the uid
-  npx mgr auth:delete "<uid>" --force
-  npx mgr firestore:delete "users/<uid>" --force
-  ```
-
-## Tests
-
-### ☐ Test 1 — Signup with marketing consent granted (golden path)
-
-**Action:** Sign up at `somiibo.com/signup` with both checkboxes checked.
-
-**Verify:**
-- [ ] Account created, redirected to logged-in dashboard
-- [ ] `npx mgr firestore:get users/<uid>` shows:
-  - `consent.legal.status: 'granted'`
-  - `consent.legal.grantedAt.source: 'signup'`
-  - `consent.legal.grantedAt.ip` populated (not null)
-  - `consent.legal.grantedAt.text` is the actual label string
-  - `consent.marketing.status: 'granted'`
-  - `consent.marketing.grantedAt.source: 'signup'`
-  - `consent.marketing.revokedAt.timestamp: null`
-- [ ] SendGrid Contacts: new contact exists with this email
-- [ ] Beehiiv Subscribers: new subscriber exists
-- [ ] BEM logs: search for `buildConsentRecord: legal=granted, marketing=granted`
-
-**Capture the uid** for use in later tests.
-
-### ☐ Test 2 — Signup with marketing UNCHECKED
-
-**Action:** Sign out. Sign up with a different fresh email. Legal checked, marketing UNCHECKED.
-
-**Verify:**
-- [ ] `consent.marketing.status: 'revoked'`, `revokedAt.source: 'signup'`, `grantedAt.timestamp: null`
-- [ ] SendGrid: contact NOT created
-- [ ] Beehiiv: subscriber NOT created
-- [ ] BEM logs: `buildConsentRecord: legal=granted, marketing=revoked` — `mailer.sync()` should NOT have been called
-
-### ☐ Test 3 — Signup with legal UNCHECKED (validation blocks)
-
-**Action:** Try to submit signup with legal box UNCHECKED.
-
-**Verify:**
-- [ ] Submit button is disabled OR clicking submit shows the inline error + red outline around the consent group
-- [ ] No Firebase auth user created
-- [ ] No request fired to `/user/signup` (browser DevTools network tab)
-
-### ☐ Test 4 — Google sign-in with a NEW (nonexistent) Google account on /signin
-
-**Action:** On `somiibo.com/signin` (NOT `/signup`), click "Continue with Google" and authenticate with a Google account that has never been used here.
-
-**Verify:**
-- [ ] Inline error appears: "This account doesn't exist. Try signing up first or use a different account."
-- [ ] User stays on `/signin` (no redirect away)
-- [ ] Firebase Auth dashboard: the user does NOT persist (created then deleted)
-- [ ] Firestore: no orphan user doc remains (`users` collection)
-- [ ] BEM logs: look for `Reversing accidental signup from /signin` warning
-- [ ] `sendUserSignupMetadata` should NOT have run (no `/user/signup` POST in logs)
-
-### ☐ Test 5 — Account-page opt-out
-
-**Action:** Sign in as the Test 1 user. Go to `/account` → notifications section. Toggle marketing OFF.
-
-**Verify:**
-- [ ] Toast/UI confirms the change
-- [ ] `consent.marketing.status: 'revoked'`, `revokedAt.source: 'account'`, `revokedAt.timestamp` is recent, `revokedAt.ip` populated
-- [ ] `consent.marketing.grantedAt` is UNTOUCHED (original signup grant info preserved)
-- [ ] SendGrid: contact removed from list
-- [ ] Beehiiv: subscriber removed
-
-### ☐ Test 6 — Account-page opt-in (re-grant)
-
-**Action:** Same user. Toggle marketing back ON.
-
-**Verify:**
-- [ ] `status: 'granted'`, `grantedAt.source: 'account'`, `grantedAt.timestamp` newer than original
-- [ ] `revokedAt` UNTOUCHED (informational, still shows the Test 5 revoke)
-- [ ] SendGrid: contact re-added
-- [ ] Beehiiv: subscriber re-added
-
-### ☐ Test 7 — SendGrid webhook → cross-provider sync via parent forwarder
-
-**Action:** In SendGrid dashboard → Marketing → Contacts, find Test 1 user's contact and manually unsubscribe (or add their email to the Global Unsubscribe list via Suppressions).
-
-**Verify (allow up to ~30s for delivery):**
-- [ ] ITW BEM logs: `POST /backend-manager/marketing/webhook/forward?provider=sendgrid` with 200
-- [ ] Somiibo BEM logs: `POST /backend-manager/marketing/webhook?provider=sendgrid` from parent forwarder
-- [ ] Somiibo Firestore: `consent.marketing.status: 'revoked'`, `revokedAt.source: 'sendgrid'`
-- [ ] Beehiiv: subscriber removed (cross-provider sync)
-- [ ] ITW Firestore `marketing-webhooks/{eventId}` doc exists (idempotency record)
-- [ ] Repost the same event manually with curl → second receipt short-circuits on `eventId`
-
-### ☐ Test 8 — Beehiiv webhook (DEFERRED until Beehiiv plan upgraded)
-
-**⏸️ Blocked**: Beehiiv webhook API requires a paid Beehiiv tier (currently 403 `ACCESS_FORBIDDEN`).
-
-When unblocked:
-- Run `npm start -- --service beehiiv` in OMEGA to auto-configure all publications
-- OR manually add the webhook in each publication's settings:
-  - URL: `https://api.itwcreativeworks.com/backend-manager/marketing/webhook/forward?provider=beehiiv&key=<BACKEND_MANAGER_WEBHOOK_KEY>`
-  - Events: `subscription.unsubscribed`, `subscription.deleted`, `subscription.paused`
-  - Publications: Somiibo (`pub_60fa806e...`), StudyMonkey (`pub_0716e341...`), shared devbeans (`pub_69c961a7...`)
-
-Then test: unsub via Beehiiv's "Manage subscription" link → verify symmetric flip on Firestore + SendGrid.
-
-### ☐ Test 9 — Page-load consent guard (ENFORCE_CONSENT_GUARD = true)
-
-**Action:** Manually edit Test 1 user's Firestore doc via `npx mgr firestore:set users/<uid>` to flip `consent.legal.status` to `'revoked'`. Refresh the Somiibo page.
-
-**Verify:**
-- [ ] User is signed out (with notification toast: "This account hasn't completed setup. Please sign up first.")
-- [ ] Lands on public site
-- [ ] Browser console warning: `[Auth] Signing out user with no legal consent on record`
-- [ ] **Restore** `consent.legal.status` to `'granted'` so the user can use Somiibo again
-
-**Important caveat from v1.3.2 fix:** the guard only fires for accounts older than `SIGNUP_MAX_AGE` (5min). For this test to work, the Test 1 user must have signed up more than 5 minutes ago. If you just signed up and immediately ran this, the guard won't fire — wait 5 minutes or use an older test account.
-
-### ☐ Test 10 — HMAC anonymous unsubscribe link (from a marketing email)
-
-**Action:** Trigger a marketing email send (or grab an existing unsub link from a previous email). Click it.
-
-**Verify:**
-- [ ] Unsub confirmation page loads
-- [ ] User's `consent.marketing.status: 'revoked'`, `revokedAt.source: 'sendgrid'` (or `'beehiiv'` depending on link origin)
-- [ ] SendGrid: removed
-- [ ] Beehiiv: removed
-
-## Commands cheat-sheet
-
-```bash
-# All from Somiibo backend dir
-cd /Users/ian/Developer/Repositories/Somiibo/somiibo-backend/functions
-
-# Logs (live tail)
-npx mgr logs:tail
-
-# Logs (one-shot)
-npx mgr logs:read --limit 100
-npx mgr logs:read --filter "consent" --limit 50
-npx mgr logs:read --filter "marketing/webhook" --limit 50
-npx mgr logs:read --filter "<uid>" --limit 100
-
-# Firestore
-npx mgr firestore:get "users/<uid>"
-npx mgr firestore:query "marketing-webhooks" --limit 10    # idempotency records (run from ITW backend, the parent)
-npx mgr firestore:set "users/<uid>" '{...partial...}' --merge
-npx mgr firestore:delete "users/<uid>" --force
-
-# Auth
-npx mgr auth:get "<email-or-uid>"
-npx mgr auth:delete "<uid>" --force
-```
-
-## Progress log
-
-Track which tests have been run + when. Mark with date once you've verified end-to-end.
-
-- [ ] Test 1 — Signup, marketing GRANTED
-- [ ] Test 2 — Signup, marketing UNCHECKED
-- [ ] Test 3 — Signup, legal UNCHECKED (validation blocks)
-- [ ] Test 4 — Google new account on /signin (reverse-signup)
-- [ ] Test 5 — Account opt-out
-- [ ] Test 6 — Account opt-in (re-grant)
-- [ ] Test 7 — SendGrid webhook → cross-provider
-- [ ] Test 8 — Beehiiv webhook (deferred)
-- [ ] Test 9 — Page-load guard
-- [ ] Test 10 — HMAC unsub link
-
-Last attempted: 2026-05-22, got blocked on Test 1 by the v1.3.1 consent-guard ordering bug. Fixed in v1.3.2. Ready to restart from Test 1 after Somiibo redeploys against `ultimate-jekyll-manager@^1.3.2`.

package/TODO-NEW.md

@@ -1,21 +0,0 @@
-ALSO!!!
-I THINK THE SIGNUP EVENT IS NOT FIRING (the manual send that comes from the user to the server)
-
-also, singup takes a while to go thru make go fstrrrr
-
-on BEM, we need to store the brand data somewhere else besides ITW because thats stupid and takes too long to load
-
-also,, need to handle the auth error for too many signups that we manually throw via beforeCreate
-
-
-FOR ATTRIBUTION FIXES LOOK AT
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/assets/js/core/auth.js
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/assets/js/core/query-strings.js
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/assets/js/core/exit-popup.js
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/assets/js/pages/payment/checkout/modules/tracking.js
-and anywhere else with attribution.!!!!
-
-FOR TRACKING FIXES (JSUTSEARCH FOR TRACKING EVENTS)
-
-CHECK OUT LEGACY!!!
-/Users/ian/Developer/Repositories/_Legacy/ultimate-jekyll-legacy/.github/workflows/build.yml

package/TODO-themes.md

@@ -1,34 +0,0 @@
-I want you to COMPLETELY REDESIGN CLASSY'S THEME. You are creating a WHIOLE NEW theme for a SaaS website.
-
-HTML
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/defaults/dist/_layouts/themes/classy/frontend/pages
-
-INCLUDES
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/defaults/dist/_includes/themes/classy
-
-THEME JS,CSS, ETC
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/assets/themes/classy
-
-
-So when you make your NEW theme, you should COPY THIS STRUCTURE, but with your NEW THEME NAME
-
-It should primarily be darkmopde, but support light mode as well. THe design should be WARM, MODERN, SIMPLE, BUT PROFESSIONAL.
-
-For the purposes of testing this theme, you only need to make the following pages
-
-index
-pricing
-signup + signin
-account
-
-
-Today i want you to build a new theme for our framework, ultimate jekyll.
-
-See the consuming project which has the theme set in config
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-website/src/_config.yml
-
-here is a page that uses the BLUEPRINT
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-website/src/pages/index.md
-
-WHICH IS THIS
-/Users/ian/Developer/Repositories/ITW-Creative-Works/ultimate-jekyll-manager/src/defaults/dist/_layouts/blueprint/index.html

package/TODO-tracking.md

@@ -1,69 +0,0 @@
-TODO
-* Does signup work with BEM 5.0?? keeps ssying cannot resolve user after i sign up and try to go into accout :(
-
-
-  FIX ATTRIBUTION
-  https://claude.ai/share/bae8e516-e74c-4e77-9a85-e58277908b43
-
-i want to also add my own "itm" tags which are set by internal things. can we process those too?
-
-// attribution.js - load this on every page
-(function() {
-  const params = new URLSearchParams(window.location.search);
-
-  // Check if this pageview has any attribution params
-  const hasAttribution = params.get('fbclid') || params.get('gclid') ||
-                         params.get('ttclid') || params.get('utm_source');
-
-  if (hasAttribution) {
-    const attribution = {
-      fbclid: params.get('fbclid'),
-      fbc: getCookie('_fbc'),
-      gclid: params.get('gclid'),
-      ttclid: params.get('ttclid'),
-      utm_source: params.get('utm_source'),
-      utm_medium: params.get('utm_medium'),
-      utm_campaign: params.get('utm_campaign'),
-      utm_content: params.get('utm_content'),
-      utm_term: params.get('utm_term'),
-      landingPage: window.location.pathname,
-      capturedAt: new Date().toISOString(),
-    };
-
-    // Only save if we don't already have attribution (first-touch)
-    if (!localStorage.getItem('attribution')) {
-      localStorage.setItem('attribution', JSON.stringify(attribution));
-    }
-  }
-})();
-
-
-TODO
-fix tiktok pixel events (look at this)
-
-Test deletion account flow
-
-
-PROBLEM
-navigatin to https://192.168.86.69:4000/reset?authSignout=true
-
-WHILE SIGNED IT signs you out (GOOD) but then it KICKS you back to INDEX (BAD) istead of STAYING O THE PAGE
-
-FIX FORM MANAGER
-
-FIX TIKTKO PIXELS TRACKING ID NOT CORRECT
-
-   output: {
-     filename: '[name].[contenthash].js',
-     sourceMapFilename: '[name].[contenthash].js.map',
-   },
-   devtool: Manager.isProd() ? 'hidden-source-map' : 'eval-source-map',
-
-
-signout on homepage
-* sign up / singin button does NOT reappear (there is just no button)
-
-
-try not to expose Manager??
-
-

package/TODO-tracking2.md

@@ -1,103 +0,0 @@
-TODO
-- google tag optimization
-  https://support.google.com/analytics/thread/352854513/gtag-click-tracking-causes-reflow-due-to-reading-a-innertext-a-textcontent?hl=en
-
-
-- SW update error (devtools check update on reload, then reload, notice it goes forever and then logs an error
-  // Private: Set up update handlers
-  _setupUpdateHandlers(registration) {
-    // Listen for updates
-    registration.addEventListener('updatefound', () => {
-      const newWorker = registration.installing;
-
-      if (!newWorker) return;
-
-      newWorker.addEventListener('statechange', () => {
-        if (newWorker.state === 'installed' && navigator.serviceWorker.controller) {
-          // New service worker available
-          this._notifyUpdateCallbacks({
-            type: 'update-available',
-            worker: newWorker
-          });
-
-          // Automatically skip waiting and activate new worker
-          if (this.manager.config.serviceWorker?.autoUpdate !== false) {
-            this.skipWaiting();
-          }
-        }
-      });
-    });
-
-- tiktok error (CHECK UJ LEGACY CODE FOR TIKTOK EXAMPLES)
-Click
-console.js:36 📊 gtag: {command: 'event', event: 'cookie_consent_auto_accepted', params: {…}, fullArgs: Array(3)}
-console.js:36 📘 fbq: {command: 'trackCustom', event: 'CookieConsentAutoAccepted', params: {…}, fullArgs: Array(3)}
-console.js:36 [TikTok Pixel] - Missing 'content_id' paramter
-Issue: The 'content_id' parameter isn't being received. This is required for Video Shopping Ads (VSA).
-Suggestion: Include the 'content_id' parameter in your source code. This is required for Video Shopping Ads (VSA). See https://ads.tiktok.com/help/article/standard-events-parameters?redirected=2 for more information.
-eval @ console.js:36
-iC @ main.MTE0NjY3MDc0MQ.js:1
-r.warn @ main.MTE0NjY3MDc0MQ.js:1
-r.handleEventPayloadValidate @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-u @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-e.track @ main.MTE0NjY3MDc0MQ.js:1
-i.track @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-trackCookieAutoAccepted @ cookieconsent.js:354
-eval @ cookieconsent.js:126
-sentryWrapped @ helpers.js:93
-setTimeout
-eval @ browserapierrors.js:95
-autoAcceptHandler @ cookieconsent.js:124
-sentryWrapped @ helpers.js:93Understand this warning
-console.js:36 [TikTok Pixel] - Invalid content type
-Issue: The content type for one or more of your events is not valid. Content type must be either "product", "product_group", "destination", "hotel", "flight" or "vehicle".
-Suggestion: Go to your source code and update the content type. See https://ads.tiktok.com/help/article/standard-events-parameters?redirected=2 for more information.
-eval @ console.js:36
-iC @ main.MTE0NjY3MDc0MQ.js:1
-r.warn @ main.MTE0NjY3MDc0MQ.js:1
-r.handleEventPayloadValidate @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-u @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-e.track @ main.MTE0NjY3MDc0MQ.js:1
-i.track @ main.MTE0NjY3MDc0MQ.js:1
-(anonymous) @ main.MTE0NjY3MDc0MQ.js:1
-trackCookieAutoAccepted @ cookieconsent.js:354
-eval @ cookieconsent.js:126
-sentryWrapped @ helpers.js:93
-setTimeout
-eval @ browserapierrors.js:95
-autoAcceptHandler @ cookieconsent.js:124
-sentryWrapped @ helpers.js:93Understand this warning
-console.js:36 📊 gtag: {command: 'event', event: 'cookie_consent_accepted', params: {…}, fullArgs: Array(3)}
-console.js:36 📘 fbq: {command: 'trackCustom', event: 'CookieConsentAccepted', params: undefined, fullArgs: Array(2)}
-console.js:36 [TikTok Pixel] - Invalid content type
-Issue: The content type for one or more of your events is not valid. Content type must be either "product", "product_group", "destination", "hotel", "flight" or "vehicle".
-Suggestion: Go to your source code and update the content type. See https://ads.tiktok.com/help/article/standard-events-parameters?redirected=2 for more information.