Skip to content
This repository was archived by the owner on Dec 6, 2019. It is now read-only.

Fixed Multisite current site evaluation issue: the site selector does…#465

Open
peternazarov wants to merge 1 commit into
Sitecore:masterfrom
peternazarov:fix/SwitchSite
Open

Fixed Multisite current site evaluation issue: the site selector does…#465
peternazarov wants to merge 1 commit into
Sitecore:masterfrom
peternazarov:fix/SwitchSite

Conversation

@peternazarov

Copy link
Copy Markdown
Contributor

Fixed Multisite current site evaluation issue: the site selector does not show the current site selection based on the current Site context.

Implementation note: maybe SiteDefinition should just have the corresponding extension method instead of "IsCurrent" property. Then the extension method can be unit tested in isolation. However, it would make the coding less intuitive because you will not observe the extension method from IntelliSense unless the extension method class's namespace is exposed to the context.

… not show the current site selection bases on the current Site context.
@nickwesselman

Copy link
Copy Markdown
Contributor

@gbxe Thanks for the PR, but not sure I understand the issue being solved here. Is there a bug in Habitat itself that you have reproduction steps for, and if so can you open a related Issue? Or is it a problem encountered when reusing this module in another solution?

Thanks!

@peternazarov

Copy link
Copy Markdown
Contributor Author

image

When you switch the site, the current site highlight does not change.

I have just completed Helix Workshop in Munich, Germany, where I discovered that issue and fixed it.

I think IsCurrent property should not be part of the data model because of its value is Site context dependent. However, there would be more Habitat solution code refactoring required. Please review the fix and evaluate whether it is good enough in your perspective.

@peternazarov

peternazarov commented Apr 1, 2019

Copy link
Copy Markdown
Contributor Author

This is the fix for #466

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants