# Adi's Internal Task List — GCIF Things I can do myself without needing Rian or client approval. These are maintenance, cleanup, and prep tasks. --- ## Easy Stuff — Do Now (No Approval Needed) ### Maintenance & Cleanup - [x] **Deactivate Mailhog for WordPress** — DONE. Dev tool removed from production. - [x] **Delete Conditional Menus plugin** — DONE. Was inactive, now fully removed. - [ ] **Remove duplicate "Upload Your Content" page** — WAITING ON RIAN. Two pages exist: `/upload-your-content/` (in main nav) vs `/upload-content/` (Matthew's new version). Need Rian to confirm which to keep. - [x] **Update BuddyBoss Platform + all plugins** — DONE. All updated except Gravity Forms Advanced Post Creation Add-On (requires manual download, license doesn't grant auto-update for this addon). - [x] **Check Gravity Forms license status** — RENEWED by Adi. License was expired, now active again. Auto-updates restored for GF core + User Registration + Advanced Post Creation. ### Push Notification Cleanup - [x] **Check OneSignal config** — CONFIGURED & ACTIVE. Has App ID + REST API key. Auto-sends on post/page publish. Custom post types: forum, reply, topic. NOTE: UTM params field has junk "snow boots" ad text (someone pasted wrong data). Also "auto-send on page published" is ON — probably should be OFF. - [x] **Check PushEngage config** — INSTALLED BUT DEAD. Free plan, zero activity in last 7 days (0 subscribers, 0 notifications, 0 views, 0 clicks). Recommend deactivating. - [x] **Document which one is actually working** — **OneSignal is the active one. PushEngage is dead weight.** Recommend: keep OneSignal, deactivate PushEngage, clean up OneSignal's junk UTM params, turn off page-publish auto-notification. ### Prep Work for Proposal Items - [ ] **Test the registration flow as new user** — use User Switching plugin to see what a new user experiences after approval. Screenshot the flow. - [x] **Check BuddyPress Profile Completion settings** — CHECKED. See findings below. Also: **Profiles Settings tab in BuddyBoss throws a critical error** — bug to report. - [x] **Review the current registration email** — CHECKED. Subject: "[{site.name}] Thank you for your application". Body is only 2 sentences: "Thanks for registering! We will look at your application within a week. The forum is not accessible until your account is approved..." plus a link to the homepage. Very bare — no welcome warmth, no guidance on what to expect, no CTAs. Last edited by Ashley Hajimirsadeghi Jan 2025. Situation: "Activate a new account". Big opportunity for improvement. - [ ] **Check BuddyBoss notification settings** — screenshot current config for reference ### Mockup Prep (Done by Claude) - [x] **Welcome popup mockup** — `mockup-welcome-popup.html` - [x] **Getting Started page mockup** — `mockup-getting-started.html` - [x] **Onboarding tour mockup** — `mockup-onboarding-tour.html` ### Plugin Built (Done by Claude) - [x] **BW Onboarding Guide plugin** — Full WordPress plugin in `bw-onboarding-guide/` folder. Ready for testing on Local by Flywheel. Features: custom post type for guides, step builder with drag-reorder, spotlight/tooltip tour engine, multi-page support, shortcode, AJAX completion tracking, settings page. --- ## Things to Prep But Need Rian's OK Before Deploying - [ ] **Build actual welcome popup code** — JS + CSS for child theme (can code it, don't deploy yet) - [ ] **Draft Getting Started page content** — write the actual WordPress page copy - [ ] **Draft enhanced registration email** — write improved email body with engagement CTAs - [ ] **Deactivate PushEngage** — recommend removing since it has zero activity; OneSignal is the active service - [ ] **Clean up OneSignal UTM params** — remove junk "snow boots" text, add proper GCIF UTM params - [ ] **Turn off OneSignal page-publish notifications** — pages don't need push notifications --- ## Things That Need Client Approval - [ ] **OneSignal vs PushEngage decision** — data shows OneSignal is active, PushEngage is unused. Recommend keeping OneSignal only. - [ ] **Enable Social Groups component** — significant feature change - [ ] **Tier 2 project scope** — email sequence, inactive user emails, etc. - [x] **Gravity Forms license renewal** — DONE. Adi renewed the license. - [ ] **Upload Content page decision** — which version to keep (old or Matthew's) --- ## Questions for Rian (Tonight) 1. **Upload Content pages** — `/upload-your-content/` (in nav) vs `/upload-content/` (Matthew's). Which to keep? 2. **PushEngage** — OK to deactivate? It has zero usage. 3. **OneSignal cleanup** — OK to remove junk UTM params and turn off page-publish auto-notify? 4. **BuddyBoss Profiles Settings critical error** — should we investigate or just note for later? --- ## Profile Fields Audit (from BuddyBoss Profile Setup) **General Information field set — 17 fields total:** Required fields (12): 1. How did you hear about us? 2. First Name (Signup) 3. Last Name (Signup) 4. Nickname (Signup) 5. Bio (with instructions about theatre practice) 6. Birth Year 7. Gender 8. Phone Number 9. Area(s) of Theatre Practice 10. How do you engage with your audience(s)? 11. Describe previous involvement with international theatre 12. Primary interest in joining the forum 13. Recommendation(s) — references with names and emails Optional fields (4): - Pronouns - Location (City/Country) - Website(s) - Social Links **Note:** This is a LOT of required fields. 13 required fields is a significant barrier to profile completion. For the engagement proposal, consider which fields could be made optional or moved to a "complete later" flow. **Biography** and **Social** field sets exist but are completely empty (no fields). --- ## Notes for Rian - The site has both OneSignal AND PushEngage active — PushEngage has zero usage, OneSignal is the real one - Gravity Forms license has been renewed by Adi. Auto-updates now working again for all 3 GF plugins. - Mailhog was active on production — now deactivated - Conditional Menus was inactive — now deleted - BuddyBoss Profiles Settings tab throws a critical PHP error — needs investigation - OneSignal has junk "snow boots" UTM params and auto-sends on page publish (unusual) - The blog post access in functions.php has a small logic quirk: archives bypass private network but single posts redirect to login. Probably intentional (tease content, require login) but worth confirming. - BuddyBoss has a "ReadyLaunch" feature in settings — worth looking at for mobile experience - Social Groups is the most powerful unused feature — enabling it later would be a good upsell - Registration has 13 required profile fields — this is heavy and likely hurts activation rates - Private website is enabled with specific public URLs: /home/, /about/, /upload-your-content/, /resources/ --- *Last updated: March 24, 2026*