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
The cwp/cwp modules comes with all kinds of semi-useful baggage like EventsPage, which most installations don't need - even in CWP 2.0. We should split out those features into their own module, similar to this cwp/cwp-search module. But until then, what's the reason this module depends on cwp/cwp? It applies some extension to BasePageController which seems to be applicable to PageController as well. And the page types extend Page, not BasePage. Is there any coupling here?
The text was updated successfully, but these errors were encountered:
The
cwp/cwp
modules comes with all kinds of semi-useful baggage likeEventsPage
, which most installations don't need - even in CWP 2.0. We should split out those features into their own module, similar to thiscwp/cwp-search
module. But until then, what's the reason this module depends oncwp/cwp
? It applies some extension toBasePageController
which seems to be applicable toPageController
as well. And the page types extendPage
, notBasePage
. Is there any coupling here?The text was updated successfully, but these errors were encountered: