Skip Navigation
Extending Standard Widgets
Answer ID 11071   |   Last Review Date 09/17/2019

Why when I extend a widget with a view helper page, the changes are not seen in the custom widget after staging?


Customer Portal(CP), Version 3.x

Oracle B2C Service, All Versions


When extending a CP widget, the best practice is to use a unique name that is not the same as the parent.  The viewHelper.php file for the custom widget does not get recognized when the standard widget contains a viewHelper and the custom widget is named the same as the parent after the code is compiled as a relative path is used and the viewHelper is loaded at a different time in development and staging/production modes.