You are viewing limited content. For full access, please sign in.

Question

Question

Weblink Default Columns

asked on July 11, 2014

I cannot get the default columns for Weblink 8.2.2 set.  I have set them in the a pre-9.1 client.  Copied the Settings:ColumnDisplay attribute to the Everyone Group, cleared the cookies, restarted IIS but the default columns are not set.  I have contacted support and they state that it is not a support issue.  Is there any other way to set the columns since this does not work?  Is it possible to set it on the browse.aspx page instead?

 

0 0

Answer

APPROVED ANSWER
replied on July 11, 2014

Please open a support case so we can investigate the matter. I'd want to take a look at how the attribute is being modified when the changes are made by you through the 9.0.3 Client.

0 0

Replies

replied on July 11, 2014
0 0
replied on July 11, 2014

Thanks, Wes.  That helps with setting the search results but I need to set the columns displayed when browsing.  Any other thoughts?

0 0
replied on July 11, 2014

Jen,

 

Can you confirm that the user you're logging into WebLink as doesn't already have its own [Settings]ColumnDisplay attribute? Note that the trustee will not inherit the attribute from the Everyone group if the same attribute already exists at the user level. Perhaps try deleting the [Settings]ColumnDisplay attribute from the user level. Then make sure that browser cookies have been cleared out. Finally, close the web browser, open a new session, and then log into WebLink as that user.

 

Regards

0 0
replied on July 11, 2014

Hi Alex, I had the same thought.  So, prior to initiating this post,  I logged in as a user to set the columns.  Then, I copied the attribute from that user's profile and applied it to the Everyone group.  I removed the [Settings]ColumnDisplay attribute from the user level, deleted cookies and cache, restarted IIS and tested.  This does not set the desired default columns. Thanks,

0 0
replied on July 11, 2014

Jen,

 

Using a 9.0.x Client, log into the repository as a specific user and then configure the browser columns as required. Once that's done, log out of the repository.

 

Now, go into the Laserfiche Administration Console and look at the [Settings]ColumnDisplay attribute for that specific user. At this point, select the specific attribute and choose to export it. Save the .xml file to the desktop.

 

Then go into the attributes for the Everyone group and click "Import" and select the .xml file that was just saved.

 

Next, confirm that the individual users that will be logging into WebLink do not have the [Settings]ColumnDisplay attribute.

 

Finally, clear out the browser cookies again and try logging back into WebLink using a new browser session.

 

Basically, from all of this, I want to confirm that the attribute is getting exported and imported properly into the Everyone group in case there may have been an issue with how it was being "copied" previously.

 

Regards

0 0
replied on July 11, 2014

Hi Alex,

I apologize for using the word "copy", I was exporting from the user and importing the attributes to the Everyone.  Then, removing the attribute from the user with no luck.  However, I just tried using the 8.3. client to set the attribute and this has worked.  The problem is that we can't assume our users will have the 8.3 client to use.

0 0
replied on July 11, 2014

What is the exact version of the Client you were using before where it wasn't working? Note that the 9.0.3 Client was the last version to write column changes to the [Settings]ColumnDisplay attribute. Can you confirm that they weren't using a 9.1.x Client? If so, then please open a support case and reference this specific Answers thread.

0 0
replied on July 11, 2014

I confirm that I was not using 9.1. I was using 9.0.3.

0 0
APPROVED ANSWER
replied on July 11, 2014

Please open a support case so we can investigate the matter. I'd want to take a look at how the attribute is being modified when the changes are made by you through the 9.0.3 Client.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.