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
As found in #494 , the Manage Projects UI is rendered with the public theme.
This is because the CiviCRM Menu (route) for the base-page is configured for public because it is expected that the Opportunity Search is wanted as a public page.
Because the Manage Projects UI is implemented as a route in the same angular module as the Opportunity Search, they must share the public-visibility config.
Solution will probably require three or more separate angular modules, one for Manage, one for Opportunities, and one for shared.
I do know that there was a lot of discussion about packaging of angular modules, so there are probably devils in the details to be flushed out.
The text was updated successfully, but these errors were encountered:
As found in #494 , the Manage Projects UI is rendered with the public theme.
This is because the CiviCRM Menu (route) for the base-page is configured for public because it is expected that the Opportunity Search is wanted as a public page.
Because the Manage Projects UI is implemented as a route in the same angular module as the Opportunity Search, they must share the public-visibility config.
Solution will probably require three or more separate angular modules, one for Manage, one for Opportunities, and one for shared.
I do know that there was a lot of discussion about packaging of angular modules, so there are probably devils in the details to be flushed out.
The text was updated successfully, but these errors were encountered: