# Fixing problems that might arise **URL:** \ **Category:** RapidWeaver Elements\ **Created:** [October 25, 2026, 2:06pm UTC](https://forums.realmacsoftware.com/t/fixing-problems-that-might-arise/57965 "2026-10-25T14:06:26Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![thominator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/thominator/32/35233_2.png) [@thominator](https://forums.realmacsoftware.com/u/thominator)\ **Post date:** [October 25, 2026, 2:06pm UTC](https://forums.realmacsoftware.com/t/fixing-problems-that-might-arise/57965/1 "2026-10-25T14:06:26Z")
Came across two problems today. 1. Swapped in a brand new Mac Studio for my old one. When Elements launched on the new computer it of course wanted to verify that this was okay. Turns out you can’t enter the activation code in the dialog box that comes up when you have maxed out your seats. The way around this problem is to just accept Trial use, then go to the Elements menus and pick Registration, which will allow you to swap one seat out for the new one you need. 2. At some point playing around with a new site that’s mostly PHP pages, Safari went haywire when trying to preview it. It suddenly asked whether I wanted to download or not. I asked Claude about this, and the answer I got produced two answers that work (I won’t bother with the rest of its explanation). @dan Claude also said that if it happens again, I should report this as a bug. FWIW, I was controlling Elements via MCP when this happened. > Safari asks to download from 127.0.0.1 when the page it receives isn’t a web page it can display. 127.0.0.1 is your own Mac, where Elements runs its preview. The usual cause with Elements is that the preview hands Safari the raw PHP file instead of running it first. Every page in this project is a `.php` file, including About, which doesn’t strictly need to be. That’s why it would hit every page you preview. > **Don’t click Allow.** It’s harmless because it’s your own Mac, but Safari would just save a copy of the file instead of showing the page. > What to try, quickest first: > 1. **Quit and relaunch Elements.** The preview runs on a small server inside Elements, and restarting the app restarts it. This fixes it most of the time. > 2. **Try another browser.** In Elements’ preview settings, pick Chrome or Firefox as the preview browser, or paste the preview address into one. If that browser offers a download too, the problem is in Elements, not Safari.