nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Do I need to regenerate page if Include file changes

qqagarg

Hi,

I am new to TeamSite so a bit confused about basics.
I have a .tpl where we are calling an include file

Now, if I make any change in the aboutHeader.incl, do I need to regerate any/all pages (I hope I do not) to take header changes into effect on production website.
I just have to change include file in staging or deploy it?

Find more posts tagged with

Comments

romil_rose

You just need to change the include file (or change related dcr/tpl of that include file and regenrate it if it is created by FormPublisher) and deploy it on your production server.

qqagarg

Thanks Romil.. it worked.

But now I am facing a different problem. My header has diff tabs. if you mouseover any of the tab, drop down opens with related links. All this navigation structure was in aboutHeader.incl

Now, I removed one link from include file and deployed to production.
My problem is, when I click on tab 2 (index page opens related to that tab) and mouseover tab 5 (where I removed the link from), that link is still apperaing.

However If i go in any other tab and mouseover tab 5, link which I wanted to remove is actually removed. It is only coming up from tab 2

romil_rose

This has nothing to do with TeamSite. My guess would be:-
1. There may be some more references to that link which you need to remove.
2. Clear the cache of browser.
3. Clear the cache of server.

qqagarg

Thanks Romil.
even the tabs are behaving differently in staging website and production website. Those working fine in production are having problems in staging website... and those problematic in staging are working perfect in production..
Seems to be some cache issue on the server. Thanks again for ur help

Adam Stoller

Hi,

I am new to TeamSite so a bit confused about basics.
I have a .tpl where we are calling an include file 

Now, if I make any change in the aboutHeader.incl, do I need to regerate any/all pages (I hope I do not) to take header changes into effect on production website.
I just have to change include file in staging or deploy it?

If the include file is a PT - which is not the case above (note: learn how to format posts to make the information clearer), then it is handled within TeamSite and would require that every page that used that PT (with it's included PT) be re-generated and re-deployed (to both your staging and production environments).

The directive you're talking about is handled by the browser, and would require that the included file be re-deployed to both your staging and production environments in order to be picked up. If it is deployed and you're still seeing "old" code in your browser, then yes, it's a cacheing problem. The first place I would look would be in the browser itself. Though you may need to do some tinkering at the web-server level too, to make sure that old data is invalidated to force re-reading of included files correctly.

qqagarg

Thanks for all the help.

We had to request for an Akamai purge in order to reflect the changes. Thanks.