Collapse
Submit a Service Request
Contact Information for Technical Support
My Service Notifications
Best Practices for Moving Customer Portal Changes to Production
Answer ID 12676 |
Last Review Date 12/13/2023
What are some best practices to use while moving Customer Portal changes to production?
Environment:
Customer Portal (CP)
Resolution:
While customizing Customer Portal for a site the following best practices are recommended. These are intended as guidelines for use when moving changes between CP development, staging and production regions, and for doing so without running into difficult to troubleshoot problems.
- Make sure you do not rename/delete any of the standard files/folders like siteConfig.json.
- After adding new functionality deploy those changes to the staging instead of staging all your changes at once.
- After staging the changes make sure you test your changes before it is promoted to production.
- Do not include PHP/JavaScript on any standard or custom pages directly, instead use custom widgets to add them to the page this will help you reuse and avoid redundant coding.
- Make sure to include all your page CSS being rendered from site.css or widget-based cascading from widget css.
- Avoid naming files like home..php or home_.php etc and remove unused files while staging or refrain them from staging to stage area.
- Do not reinitialize your changes from development to stage every time instead only stage the corresponding page customized or added with its underlying widgets.
For further details see
