Adjusting some default interface behaviour

Hello,

I have been tasked with making some changes to the default behaviour of our Collab site (v7.2). It seems straightforward (and I'm hoping that someone on this forum might tell me that it is) but I am having difficulty with:

Having the Usage Counts option selected by default in all places where it appears
Adjusting the default search view to be "best matches first" rather than "with context"

In both cases I have identified the fields in the code (common_metadataSection.shtml, search_viewMenu.shtml) but I realize that the call of the JavaScript in the onClick or button press is probably required to have the change take effect.

Can anyone advise on the best way to make such changes?

Thanks in advance,

Niall O'Grady

QAD

Find more posts tagged with

Comments

Ryan Atkins

Hi Niall,

To have the Usage Counts show by default, you can do the following.

1. Make a backup copy of $Collab\WWW\SCRIPT\Common.js

2. Open Common.js in an editor.

3. Find the function 'getPref', and add an else clause as follows:

function getPref(prefSet, key)

{

??if (ITS_prefs) {

?? ?...

??} else {

?? ? ?if (prefSet == "visibility" && key == "showUsage") {

?? ? ? ? ?return true;

?? ? ?}

??}

??return false;

}

No restarts required, but you may need to remove cookies from your browser (or specifically remove the 'vgn-collab-ui-prefs' cookie) in order to see the new default behavior.

Regards,

-Ryan

On Thu, Sep 9, 2010 at 11:48 AM, eLink Entry: Vignette Collaboration Developers Forum <vignettecollaborationdevelopersforum@elinkkc.opentext.com> wrote:

Adjusting some default interface behaviour ? Posted bynio@qad.com (OGrady, Niall)On 2010/09/09 12:46
?
Hello,I have been tasked with making some changes to the default behaviour of our Collab site (v7.2).? It seems straightforward (and I'm hoping that someone on this forum might tell me that it is) but I?am having difficulty with: Having the Usage Counts option selected by default in all places where it appears Adjusting the default search view to be "best matches first" rather than "with context"In both cases I?have identified the fields in the code (common_metadataSection.shtml, search_viewMenu.shtml) but I realize that the call of the JavaScript?in the onClick or button press is probably required to have the change take effect.Can anyone advise on the?best way to make?such?changes?Thanks in advance,Niall?O'GradyQAD?
[To post a comment, use the normal reply function]
Forum: Vignette Collaboration Developers Forum
Livelink Server: knowledge-wlweb01

Niall_OGrady

Thanks Ryan,

That is EXACTLY what I was looking for and it's worked a treat.

Now to explore whether the search view default can be achieved in a similar way.

Niall

Ryan Atkins

Glad it worked, Niall. ?For your other problem, add the following line to the "search_commonFormPart.shtml" template:

Regards,

-Ryan

On Fri, Sep 10, 2010 at 5:22 AM, eLink Entry: Vignette Collaboration Developers Forum <vignettecollaborationdevelopersforum@elinkkc.opentext.com> wrote:

Re Adjusting some default interface behaviour ? Posted bynio@qad.com (OGrady, Niall)On 2010/09/10 06:18
?
?Thanks Ryan,That is EXACTLY what I was looking for and it's worked a treat.Now to explore whether the search view default can be achieved in a similar way.Niall
[To post a comment, use the normal reply function]
Topic: Adjusting some default interface behaviour
Forum: Vignette Collaboration Developers Forum
Livelink Server: knowledge-wlweb01

Niall_OGrady

Once again, this did exactly what I required of it.

Thanks Ryan.

Eddy_Hutchins

Hi,

I have done the same thing with my installation of Collab, and changed the default search order to 'best matches first' (as well as changing the default UR search field to 'own' rather than 'any') using the code you supplied here, however I came across some problems.

This method works for searches when using the simple, advanced and embedded searches EXCEPT when clicking through to advanced search from the search results page. Data is still passed through, for example, the search term, or user you are searching, but does not seem to pick up the SO or UR parameters set by these hidden fields.

Have you come across this? Or know a way it can be resolved?

Resolved, just an issues with parameters being passed twiced.
Editted the showSearchSwitch file to stop the values being passed through again.