hey there,
i had a chance to speak with another support engineer about this, and he confirmed my initial hunch that while indeed the repo may be the same one, there is likely some setting in the UI (and the toml file that those settings generate) that is different from site to site. This would mean that the sites are identical in content, but not necessarily the same in how they are displayed, as these settings are not saved or coming from the git repo.
here is one thing we found that could be the culprit:
> Site.find_by_subdomain("choruslondon").repo.node_version
"16"
> Site.find_by_subdomain("chorus-app").repo.node_version
"12.18.0"
(hats some output from our internal console)
it could be something else, but i would try making both node versions the same. If it works better on the older version, than thats the one you should enforce for the short term,. that said, version 12 is pretty old and you’ll want to get things working on a newer version for security and performance reasons for sure.
info on that here:
more general info here:
your secondary issue with having two sites is something we can address after we get them both working the same. we’ll need to get you talking to a support engineer and do some verifications and lever pulling - as you mentioned, we don’t just delete sites for obvious reasons, but we can see if we can help you out.
let me know if this fix, setting the node versions, works.