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

generate page option from actions menu

Amrita1

Hi,
thanks in advance.

is it possible that when I click the generate page option in the action menu in teamsite, the dialogue box which is opening to save the output should directly open with the output path folder. ow its opening at the parent level
templatedata. Each time I have to navigate to the output folder location.

my entry in the templating.cfg is:

let me know, in case of more information.

if anybody can suggest on this?

Find more posts tagged with

Comments

brvhrt

Hi,
thanks in advance.

is it possible that when I click the generate page option in the action menu in teamsite, the dialogue box which is opening to save the output should directly open with the output path folder. ow its opening at the parent level
templatedata. Each time I have to navigate to the output folder location.

my entry in the templating.cfg is:

let me know, in case of more information.

if anybody can suggest on this?

I am not sure if you can do that or not i have tried that but You could use FormAPI -callserver to do the auto generation for you and creating and outputting the generated file in the desired directory based on a certain structure ( that can be done in the DCT using a drop downs etc) so with a single click you could do it all , save the dcr and generate the file and output it in the desired place Smiley Wink

Adam Stoller

Hi,
thanks in advance.

is it possible that when I click the generate page option in the action menu in teamsite, the dialogue box which is opening to save the output should directly open with the output path folder. ow its opening at the parent level
templatedata. Each time I have to navigate to the output folder location.

my entry in the templating.cfg is:

let me know, in case of more information.

if anybody can suggest on this?

The entry in the templating.cfg file is only used to validate the information that has been provided - it is not used as an initial starting directory (often requested, never done).

The FormAPI solution, as previously posted, works if you are initiating the page generation from within the Edit DCT window - it doesn't help when using the Actions > Generate Page option though, as far as I know anyway. So I don't think there is any way to achieve what you are asking about, in the manner in which you phrased the question.

It is possible to replace the OOTB Generate Page menu item with your own custom menu item that uses some site-defined method for programmatically determining the correct path and name of the to-be-generated page - but that's up to you to implement if so desired.

Amrita1

thanks brvhrt and fish.

yeah i am also aware of the method of generating from dct. and fish, thats right i wanted it from actions menu. mmmm, thanks anyways for your suggestions, will see if I can follow up in the other way.

Thanks.. Smiley Happy