Skip to main content

To avoid having to find all the places where a pricing calculator might be used, I had the idea to create a “container” page that I use as a page include wherever I need to display the calculator. Within that container page I would use a page include and link to the specific page for the pricing calculator. Whenever the pricing calculator necessitates the creation of a new page for a new version, I would just update the page include on the container page. The thought being that this would effectively update the calculator everywhere that it is displayed. 

Are there any reasons not to do this? The pricing calculator is mostly standalone and does not have any parameters passed to it.

You can definitely nest page includes. The most common issue I see with doing that is when the container page and page include are both using the same url parameter, but you’re not using those in this scenario. 

Stand alone pages are usually good candidates for page includes.


Hi @Jamie_Buck-Tomek is this question resolved?

 


Reply