Menu Item CGI for TS6.1

Hi all,
I'm new to TS6.1 and i'm looking for some good examples to get user, dcr, and system info from a perl/cgi callout.
Attached is an example from interwoven for previous versions of teamsite.
Does anyone have this or similar for the new versions TS6.1 and on.

Thanks
-K

Find more posts tagged with

Comments

Migrateduser

You can use the same CGI scripts to add custom menu items to TS 6.1. See customization guide to implement it.

Migrateduser

batasari,
The problem is not that I can't add the menu item. The problem is when the old version script runs, it doesn't capture anything. So i'm looking for a sample script to run on TS6.x to grab all the user/dcr/system variables.

-K

Migrateduser

You can use show_env.ipl cgi script to see the environment variables passed to the script. If you search the forms will find threads for migrating CGI scripts from 5.5 to 6.x.

gzevin

batasari,
The problem is not that I can't add the menu item. The problem is when the old version script runs, it doesn't capture anything. So i'm looking for a sample script to run on TS6.x to grab all the user/dcr/system variables.

-K

It's all explained in the manuals - how to retrofit the old scripts. There is even a warapper script supplied that fixes most of the issues

Migrateduser

Thanks all,
I did find the wraper to retro fit the old scripts.
If anyone is having the same issue, search for WebDeskPro Custom menu Item Adapter."wdpro_menu.ipl" It'll save you a ton of work

-Nomi

Adam Stoller

Thanks all,
I did find the wraper to retro fit the old scripts.
If anyone is having the same issue, search for WebDeskPro Custom menu Item Adapter."wdpro_menu.ipl" It'll save you a ton of work

-Nomi

That's a bandaid for short-term porting - you should (IMO) work on re-coding the scripts to use the new form variable data as the wdpro_menu.ipl is adding an extra layer of overhead for your custom menu items and, may potentially disappear in a future release...

Example Report.rptdesign

gzevin

That's a bandaid for short-term porting - you should (IMO) work on re-coding the scripts to use the new form variable data as the wdpro_menu.ipl is adding an extra layer of overhead for your custom menu items and, may potentially disappear in a future release...

given the fact that custom menu items are usually not used THAT often, I doubt the overhead is simething that needs to be taken into account. The second point does makes sense IMO. But still, one might choose to simply port the wrapper script to the new version