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; } } }

regeneration

sabya

There is multilevel folder structure of a site. The pages include the footer file.if there is a change in the footer component in livesite .is there any way to get the changes reflected on all the pages in the branch automatically without the user having to regenarate the page or asked if it wants to get the latest changes.

Find more posts tagged with

Comments

santosh013

No,You cannot Regenerate multiple pages on fly.
And it is advisable not to do so as lots of processes are involved.

Thanks,

Faizi

Is there a way to Regenerate multiple pages on fly acoording to the changes in the new component,when one changed the component automatically in livesite?

In simple No!!, Because there are lots of process before generating a page.
Whenever a component being changed it has to be submit then need to invoke get latest component then generating the page using component.

But there is no limitation to exploring. So, there is a scope to achieve it using Workflow and it will need to dig into various logic.

RajatChopra

Can someone shed a light on 'too many processes in involved in regenerating pages?'

It seems absurd that we are not able to generate multiple pages on the fly. We have over 200 pages and if there is a change to the header component, are we supposed to edit and submit all the 200 pages?

Can someone from Interwoven please validate and recommend an approach or an investigation path?

-Rajat

bittu

There is multilevel folder structure of a site. The pages include the footer file.if there is a change in the footer component in livesite .is there any way to get the changes reflected on all the pages in the branch automatically without the user having to regenarate the page or asked if it wants to get the latest changes.

You can do it try with iwperl programming.

ccprofessional

You can do it try with iwperl programming.

Not really.
I agree its a pain to update multiple dot pages (not to mention server timeouts). Autonomy, are you listening?

RajatChopra

You can do it try with iwperl programming.

Not really.
I agree its a pain to update multiple dot pages (not to mention server timeouts). Autonomy, are you listening?

I have opened a support case on this and will follow up with them on it. Will update this thread as soon as I have a response.

-Rajat

sabya

rajat thanks for your effort. It would be really very helpful.

sabya

hi rajat,

is there any reply from the support case raised for the regeneration.

acezone

hi rajat,

is there any reply from the support case raised for the regeneration.

Hi Sabya,

Try doing the below steps:

1. Create an XSL folder parallel to sites folder.
2. Create an .xsl file with your code within.
3. Create a XML/XSL component
4. Call .XSL file within this component.
5. Make a change in XSL and preview the component.

In component changes you made on XSL shall be reflected on preview. Similarly, perform the same by placing component on page.

Let me know in case any further help is required.

Regards,
Ace

tec_iwov

it's not on the fly but you can update pages enmass by selecting any number of pages and using the "get Latest Components" menu item.

acezone

it's not on the fly but you can update pages enmass by selecting any number of pages and using the "get Latest Components" menu item.

Hi tec_iwov,

As per the requirement

It seems absurd that we are not able to generate multiple pages on the fly. We have over 200 pages and if there is a change to the header component, are we supposed to edit and submit all the 200 pages?

If we call an external XSL file within component, in that case what ever the changes we perform on XSL shall than be reflected on compoennt even on previewing or at loading time. Similarly, whatever the chnages are getting reflected on component, on placing the component on page level will behave accordingly.

Also, get latest component shall work only on .page files but not on the folder. So instead of browsing to each folder is tedious job and i would recommend the same discussed with Autonomy.

Let me know if still any gaps or confusions has to be addressed out here.

Regards,
Ace

Migrateduser

hi Rajat,

Did you get any response from Interwoven support on automatic page generation.

We have similar requirement on any changes in header/footer all the .pages which have incuded these components shoul be autoatcally updated. We also need to generate .html files automatically for the corresponding .pages.

Any anwsers on this is greatly appricated. Thanks!

Teamsite/SiePub 7.1, Linux RHEL

PriyankaGupta

Hi Vani,

Did you get any solution for automatic page generation?
We have a similar requirement where we need to automatically regenerate all the page on change on navigation components.

Any pointers will be really helpful.

TIA,
Priyanka

Bowker

This will work if your site uses LiveSite and the pages are built dynamically. I don't see how this would work if you use a static HTML site that is generated by SitePublisher.

We don't use "generate" very often so I'm a little rusty on "regenerate" but you may be able to regenerate all the files in a folder at once. Then going one step further, if you, at the OS level, touch all your HTML (change permissions or something), then in TeamSite "view modified files", select all the files and regenerate. Maybe???