# Tools

One-shot scripts and helpers used during project setup or migrations. They are NOT part of the published site.

## fresh-setup-mu-plugin.php

Drop into `wp-content/mu-plugins/` of a freshly created LocalWP site to auto-configure WordPress for the Asterion VR project. Read its inline header for the full procedure.

Quick recap :

1. Delete the old LocalWP site (right-click → Delete site, optionally move folder to trash).
2. Create a new LocalWP site named "Asterion 2026", mode `localhost`, default credentials.
3. Note the allocated port — likely `10004` again. **If different, edit `AV_TARGET_HOME` in `fresh-setup-mu-plugin.php` first.**
4. Junction the child theme into the new site:
   ```powershell
   New-Item -ItemType Junction `
     -Path "C:\Users\j_foucher\Local Sites\asterion-2026\app\public\wp-content\themes\asterion-bricks" `
     -Target "C:\ASTERION\GIT\WP2026\wp-content\themes\asterion-bricks"
   ```
5. Extract the Bricks parent **theme** into `wp-content/themes/`. Bricks is a theme (not a plugin) — installing the ZIP via WP admin → Plugins → Add New will fail with "No valid plugins were found".
   ```powershell
   $site = "C:\Users\j_foucher\Local Sites\asterion-2026\app\public\wp-content"
   Expand-Archive "C:\ASTERION\GIT\WP2026\ThirdParty\bricks.2.3.4.zip" "$site\themes\" -Force
   ```
   (Or via WP admin → Appearance → Themes → Add New Theme → Upload Theme.)
6. Extract WPML **plugin** into `wp-content/plugins/`:
   ```powershell
   Expand-Archive "C:\ASTERION\GIT\WP2026\ThirdParty\sitepress-multilingual-cms.4.9.3.zip" "$site\plugins\" -Force
   ```
   (Or via WP admin → Plugins → Add New → Upload Plugin.)
7. Copy `tools/fresh-setup-mu-plugin.php` → `<NEW_SITE>\app\public\wp-content\mu-plugins\fresh-setup-mu-plugin.php`
8. Visit `http://localhost:10004/` once. The plugin runs at `init` priority 50, configures everything, and self-deletes after success.
9. Verify by hitting `http://localhost:10004/wp-admin` — login, then check that:
   - Theme : Asterion Bricks active (parent: Bricks)
   - Plugins : WPML active
   - Settings → Permalinks : Post name (`/%postname%/`)
   - Bricks → Settings → Builder access : Page + Post + case_study + scenario checked

Then activate the Bricks license (Bricks → License) and run the WPML setup wizard manually — those need your license keys and an interactive choice flow that's safer to do in admin.

## What's missing — manual follow-up after fresh setup

- Bricks license key activation (Bricks → License)
- WPML setup wizard (WPML → Setup) : EN default + FR secondary, URL strategy = "Different languages in directories"
- Bricks → Theme Styles : align colors with `tokens.css` (Brand Navy `#0B1F3A`, Brand Gold `#C9A45A`, etc.)
- Build the Header and Footer Bricks Templates (per RESTART-PLAN.md Phase 4)