You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2022. It is now read-only.
Hey Matt,
Downloaded Amplify and have been having a rummage about; looks really good and I can see that a lot of work has gone in there!
Just wondered if there is any plan to support multiple home nodes (which could then be assigned different domains via culture & hostnames). I tried it just now, but unfortunately, although the two nodes render the correct content, the styles/theme etc always uses the original home node's settings.
From a quick look through the code, it looks like this is something to do with the SiteService, maybe it's caching the Home node? I wonder if it's worth looking at another solution like Model.AncestorOrSelf<Home>().FirstChild<AppConfig>() or something...?
Interested to potentially contribute to this project.
The text was updated successfully, but these errors were encountered:
Hey! thanks for downloading and trying this out.
I won't be actively updating this at the moment, if you can figure the issue out, then submit a PR and I'll update!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey Matt,
Downloaded Amplify and have been having a rummage about; looks really good and I can see that a lot of work has gone in there!
Just wondered if there is any plan to support multiple home nodes (which could then be assigned different domains via culture & hostnames). I tried it just now, but unfortunately, although the two nodes render the correct content, the styles/theme etc always uses the original home node's settings.
From a quick look through the code, it looks like this is something to do with the
SiteService
, maybe it's caching the Home node? I wonder if it's worth looking at another solution likeModel.AncestorOrSelf<Home>().FirstChild<AppConfig>()
or something...?Interested to potentially contribute to this project.
The text was updated successfully, but these errors were encountered: