Content Experience widget and removed dependencies and angular providersIn version 32.0.5 of Content Publishing, we revamped the Content Experience widget. In order to better maintain the widget we removed following dependencies and angular providers from Content Experience widget and moved them to appropriate widgets. Dependencies m2m_sp_widget_dependency_5e4f5d28ff232010f464a36cf43bf1f6 (dependency - tooltip-overflow.css)m2m_sp_widget_dependency_6bf27528ff5e201014c6a36cf43bf104 (dependency - ngTouch Content Publishing)m2m_sp_widget_dependency_869390b0ff547010f464a36cf43bf13c (dependency - portal-content-preview-info-tab.css)m2m_sp_widget_dependency_aca2b46e91e4b010f8779b126464949c (dependency - cd-styled-content.css)m2m_sp_widget_dependency_e7a41634ff12601014c6a36cf43bf105 (dependency - cd-banner.css) Angular Providers m2m_sp_ng_pro_sp_widget_0f037528ff5e201014c6a36cf43bf1c6 (angular provider - cdBanner)m2m_sp_ng_pro_sp_widget_3a23f528ff5e201014c6a36cf43bf152 (angular provider - anyClick)m2m_sp_ng_pro_sp_widget_46918f642c64f810f877ccaf0314146e (angular provider - cdStyledContent)m2m_sp_ng_pro_sp_widget_7e23f528ff5e201014c6a36cf43bf154 (angular provider - cdAnalytics)m2m_sp_ng_pro_sp_widget_7e23f528ff5e201014c6a36cf43bf156 (angular provider - portalContentPreviewInfoTab) If the widget is customized but the related m2m records are not, widget will be skipped during upgrade and these m2m records will be deleted. This will cause widget to no longer work as expected. Workaround Re-add the deleted m2m dependencies and angular provider, ensuring they are customized and preserved to prevent their removal in future upgrades. Recommendation We highly recommend cloning OOB widgets rather than customizing them directly. This approach ensures that you receive the latest updates during upgrades. By working with cloned widgets, you can choose to integrate new features or changes at your discretion, while also minimizing potential issues during app upgrades.