On my mac, I am using Mamp PRO to test RapidWeaver using Foundry websites. I have set my website up with a test domain name translated to my Mac’s IP address via the hosts file (via Mamp Pro). I can type the domain name into Safari and the web page displays OK. I can go into the alloy editor using the domain name. However when I drag a new image to a blog post or drag a just created embed stack icon from the Alloy editor onto a foundry stack while editing in RapidWeaver, the image and embed URL is starting with the IP Address and assigned port, as opposed to the domain name. This results in both the image not displaying and the embed saying the source can’t be found. I was originally using the ip address and port but this was causing issues in Alloy which was dropping the port number on certain Editor actions (like deleting a post).
I have done the normal things like checking the General tab is pointing to the domain name and setting the publish website to be the test domain name. I have republished all files (they are going locally on the Mac). Existing images displayed in Foundry web pages are OK. It is just Alloy which has “lost” access to blog images which all are referenced via the IP address and Port.
So it looks like the “base url” used in Alloy is remembering its original setup under an IP address and not updating to use the new test domain name.
I figure I must have missed a setting somewhere but can’t figure out where that is.
I am using Monterey 12.2.1, Mamp Pro 6.6.1 (PHP 7.4.21), RapidWeaver 8.9.3, Stacks 4.2.3b5, Foundry 18.104.22.168, Alloy 3.2.