I’m aware that support is off today - wishing all a thoughtful Memorial Day. Just posting this now to solicit some pointers with no particular urgency. Not sure if my confusions are EE, Dreamhost, or Deeploy related. Thought I’d start here and follow any promising leads.
Here’s what I’ve got going.
EE 2.1.3 w/MSM.
Dreamhost web hosting.
Original EE site is a members-only site. Goal is to move a public (“plain HTML”) site to also be managed by EE.
Public site is at “domain.org”
Created a new domain “a.domain.org” to use for development. Careful use of {site_url} and {homepage} to make templates as immune to move as possible. New EE version of site on a.domaing.org looks great… ready to switch.
Used Dreamhost panel to point “domain.org” at file directory “a.domain.org”
Used Deeploy to change all EE paths for public site from a.domain.org to domain.org. Success.
Cleared EE caches and web browser caches.
Used Dreamhost panel to redirect “a.domain.org” to “domain.org” just in case.
Site looks fine and renders as http://www.domain.org as expected, but all links still are “a.domain.org”
Not sure where the “a.domain.org” paths are sticking. My main nav uses snippets that reference {homepage} and/or {site_url}. I’ve eliminated those globals for now so the links resolve properly. Maybe that was a parsing order problem? Even so, why do they still pick up the “a.domain.org” path if all my general and channel prefs no longer show the “a.domain.org” paths?
Thanks for any thoughts.
Update: Looks like I relied too heavily on the Deeploy module - the index.php file on the public site still had the old path. Updated that and all appears well for the moment. Still a great module though. A++ would use again 😛