https://discord.umbraco.com logo
Join Discord
Powered by
Umbraco 7 legacy cache question
# help-with-umbraco
a
This might be a long shot, but I'm out of ideas! I recently inherited a legacy Umbraco v7 site currently hosting my corporate website, and my team and I have run into an issue that I believe is related to caching. We have a page of leadership profiles for a segment of the company, name, pics, bios, standard stuff. Recently we removed a profile from this list, however, the removed profile can still be viewed by a direct URL. Its not visible by browsing the list, only by that direct URL. I am not proficient with Umbraco, or manipulating the site directly through the API, so any help would be appreciated! Feel free to DM me for more details and specifics!
s
Try deleting App_Data/umbraco.config and restart the site
b
If it was in some form of list, it is possible the actual content for the profile is still published. You might need to find it and unpublish it.
s
Or maybe some form of output caching?
a
its been unpublished and deleted entirely
This is my thought as well, but it looks like the only way to clear the cache is through an API call, which I unfortunately do not know how to do
I dont know enough about umbraco, will it regenerate the config file on restart? Also, where does that folder live on the server?
l
App_Data/umbraco.config is a file based cache to make Umbraco boot faster. On boot, it will read the file into memory instead of reading the database, which makes to boot faster. You can just delete the file and it will be rebuild the next time, although booting might take a little longer. But that cache file can also cause cases of content that's still visible on the site even though it shouldn't be there. If you want to be safe, just create a backup of the file before deleting it.
a
So, I do not see an umbraco.config file, but i do see a Web.config file in the wwwroot directory, one level up from App_Data. This site is hosted in an Azure app service instance, could that have something to do with it?
s
Don't delete Web.config whatever you do 😅
Another option would be to republish the home node with descendants from the backoffice
But be careful if the site is huge
a
Define...huge? lol
because I like that idea better than risking a service restart in Azure
s
How many nodes approximately?
a
a couple hundred for all the sub-pages and blog posts
s
That's not too big.
a
okay, I will give that a try
s
But I won't be responsible for damages to live environments
Disclaimer 😂
a
obviously lol
sadly I don't have a dev env for this site either
s
Damn 🥲
a
agreed
nothing like inheriting legacy code
s
Always fun 😵‍💫
Do you have access to the source code then? Any indication of output caching or other caching in there?
I also wondered if there was a CDN like Cloudflare in front of the site that may be caching the page
a
I do have access, but its all through an Azure app service, which I am a noob at navigating
and we don't have a CDN as far as I know
not yet at least!
s
Been a while since I did anything with app services tbh
3 Views
PreviousNext
Powered by