What Object cache does is stores metadata about SharePoint Server objects (like SPWeb, SPSite, SPList, etc.) on the WFEs. When a page is rendered, if there is data that needs to be retrieved through these objects, the SQL Server will not be hit. Features of SharePoint that uses Object cache are publishing, content query web part, navigation, ...
After banging my head around for some days, the problem was solved by flushing the blob cache.
This is the command I used on the Front end server
$webApp = Get-SPWebApplication "<WebApplicationURL>"
Write-Host "Flushed the BLOB cache for:" $webApp
SharePoint Foundation does not support output caching. You have to rely on ASP.NET Cache objects in your code.
Infact BLOB cache, page output, and object cache are not available in SharePoint foundation. Page output and object cache require that you activate the ‘SharePoint Server Publishing’ feature located in the site features of your web site, so these ...
There are various ways:
// Stop Caching in IE
// Stop Caching in Firefox
or you could use the @Output property:
Here you can find all ...
Object cache - metadata, WP queries of external sources, search boxes, quick launch, breadcrumb
Default is on
Configurable through GUI or web.config per each SC
BLOB cache - binary large objects like images or CSS files, stored on WFE disks
Default is off
Configurable through GUI or web.config
Page (output) cache - for whole pages to load them faster ...
If you are using themable css and EnableCssTheming set to true and your site use some theme (using theme is required), sharepoint will compile your css file into another css file with replacing placeholders, that looks like /* [ReplaceColor(...
A few things to check.
I would access the site through fiddler2 to see where it's pulling the css from and to see if it's pulling a live or cached version to your browser.
I would verify that blob caching is turned off.
Just like Andy said, make 100% sure it's checked in and published. You might have to do this through SP designer and not the web ...
You should create a big array that you'll then store into the sessionStorage. And your code is not really clear.... based on what you asked I rewrote it:
// we suppose that "index" is the "Title" we are looking for
var index = "My Title";
// get the data from sessionStorage
var list = sessionStorage.getItem('PrivacyStatementsList');
Ok I have finally found the root cause for this issue.
I believe this is a bug relating to either Windows Server 2019, SharePoint Server 2019, or a combination of the both.
Basically, the application pool accounts do not have sufficient permissions to create BlobCache folders in a vanilla install of SP2019 (specifically on Server 2019).
There are 2 key ...
You could use WFE's to cache, but ensure you have enough RAM assigned in each of the servers to cater for the needs of App Fabric and SharePoint. Performance will drop if the servers run out of RAM and start paging. The main motivator to run on the same servers should be cost driven.
Some possible reasons to run App Fabric caching on seperate servers are in ...
IIS 7 Output caching! I'd enabled this a while ago to try and improve performance on the public side of the SharePoint side - but apparently the only noticeable effect was that the system pages were cached. Oh well, having turned it off my group memberships are now displaying properly. Lesson learned.
I encountered this same problem in SharePoint 2016, and was finally able to resolve it by configuring output cache profiles.
Output Cache Profiles are applied at both the site collection level (by clicking the Site collection output cache link under Site Collection Administration) and the site level (by clicking Site output cache under Site Administration).
You can use query string for every new JS/CSS files like ?v=GUID to trick the browsers, which definitely will ensure new CSS/JS will be loaded every time you perform a new deploy. Otherwise, there is no clean solution to avoid browsers' behavior.
/Style Library/my_js_file.css?v=<current date>
If they are 5 different apps from 5 different developers and each is using its own local copy of Jquery then there is nothing you can do. On the other hand, if you are the developer of those 5 apps just use put all common files on a central server and reference the files from there. Browser caching works based on the domain where the file is pulled from.
It looks like you are calling CSSRegistration on a css file that doesn't exist. CSSRegistration is used to ensure that a css file will only be loaded once even if it is referenced multiple times. It can also allow for conditional loading of stylesheets depending on what browser is being used to view the page.
Have a look through any masterpages or page ...
Try setting query.Webs:
query.Webs = "<Webs Scope=\"SiteCollection\" />";
See if that makes a difference.
I also found another site that might help:
Cache misses are mostly likely to happen because of insufficient memory as they all are stored in Ram. If not then mostly cause must do with the Cache configuration. I would suggest to try the different settings specified for the object cache like changing the maxSize directly in the web.config etc. in the article below,
"Cache miss for query Web" may be the answer. You may be looking at the ULS log for the wrong portion. I would look at the ULS log for the first successful run and see if there is not a cache miss for the list that results in a cache dump for the list you are querying.
You may be able to remedy by changing the query from server side to client side. If I ...
Configuring object cache settings
The object cache settings can be configured at the site collection
level in the user interface by a site collection administrator, and is
on by default. The maximum cache size can be configured at the Web
application level on the front-end Web server to place a restriction
on the maximum amount of memory that ...
You should probably consider what kind of cache are you targeting: client-side cache only (try embedding Pragma:no-cache headers in specific pages/controls or even appending random query strings on every request - very bad for performance if you're doing it in the master page) or server-side cache - e.g. for Publishing sites use Caching Profiles. There is ...
Remember you should not cache the SPListItem itself as it contains a link to the SPWeb used to get it and will often require this to be alive. So get the information out of the SPListItem and into some repository objects.
Disclaimer: I've never tried to use this, but it should work.
The SPListItem has a property SPReusableAcl inherited ...
Make sure you do not have the ASP.NET patch KB2638420/MS11-100 installed. This ASP.NET patch will render the page output cache useless. Just uninstall it or install SP2010 April 2012 CU (which fixes this scenario).
One other consideration is product support from Microsoft for AppFabric. Microsoft will only provide support for dedicated AppFabric servers. Combining multiple server applications on one server is not supported per this article:
From the article:
Microsoft AppFabric 1.1 for Windows Server cache ...