Can SPA be safely disabled?
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
legacy-article
learn-legacy-article-disclaimer-text
Issue
- We are developing some components and we are having issues with single-page application (SPA). Therefore, we would like to know if it can be safely disabled
Resolution
- From Liferay side, SPA can be safely disabled.
- However, carefully consider your specific requirements and ensure that disabling the SPA functionality does not conflict with any other ongoing developments.
- When creating some custom frontend code you need to consider how your code will interact SPA mode. As an example of this, you can see how many components in Liferay destroy their components before navigating using SPA (sample 1, sample 2). You might need to do the same within your custom code.
- Enabling SPA offers numerous advantages that would be lost if it were disabled. Somo of these benefits include:
-
Enhanced performance and responsiveness: faster loading times by dynamically updating content based on user interactions, eliminating the need to reload entire pages.
-
Reduced data consumption: smooth page rendering even on slow or unstable internet connections.
-
Better user experience: due to its advantages, users are more engaged.
- If you still want to disable it, you may want to do it just for a specific portlet, or even for an individual element. See Disabling SPA.
- Or you may want to disable it for some paths. See Custom Excluded Paths in SPA
did-this-article-resolve-your-issue