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

preview_history_limit - what's the default?

cliffhanger

Hi folks,

What's the default value TeamSite gives to preview_history_limit when it's not specified iniw.cfg?

What's the advantage/disadvantage of specifying preview_history_limit ? Is there any recommended value that preview_history_limit should be set at?

By the way, I did read the admin manual for 6.1 but didn't find anything helpful regarding this, it just mentions how it works, I didn't find answers to my questions there.

Any help is appreciated,

-cliff

Find more posts tagged with

Comments

Adam Stoller

I don't think the list limit settings in 5.x iw.cfg carry forward into 6.x.
Instead - in 6.x you basically start out with something like a default of '100' for list size with an option to click on a link for 'Show All' - if you click on that link, it's retained in your entities entry and subsequent views of the same list will default to 'Show All' (until/unless you click on the '100' link, etc.)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

cliffhanger

Fish,

I think you are talking about "list_page_size" which is under [iwcgi], I am actually talking about preview_history_limit under [teamsite_templating]

-Cliff

Adam Stoller

Ah - yes - so I see - and it is mentioned in the Administrator's Guide - though it doesn't mention the default value (doc Bug) I *think* it defaults to '2' - however you can probably find out by not setting anything and running a bunch of different previews and see how many zz_* files you end up with ...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

cliffhanger

Only 1, and for some reason it caches for a long period of time- don't have any exact figure.

Do you think setting it to >1 might help the caching issue??

Adam Stoller

caching is usually a byproduct of webserver and/or browser application settings.
However, setting it to > 1 might help alleviate the problems you are currently experiencing.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Jeremy

When you mean caching do you mean the the Preview stays the same even though you have made a change?
This could be IIS caching.
See this article.

HTH.

cliffhanger

YES. Thanks Jeremy!! Although the solution mentioned in the article is not in my control, it's good to be aware of.

-cliff