DanDiplo / Umbraco.AuditLogViewer

An audit and content log table viewer for Umbraco CMS
https://www.diplo.co.uk/blog/web-development/diplo-audit-log-viewer-for-umbraco-10/
16 stars 7 forks source link

Showing Blank Page #11

Closed aphwong closed 1 year ago

aphwong commented 1 year ago

Envionment: Umbraco 10

Issue: Blank Page is showing when accessing Log Viewer image

Error Message: image

Could I ask how to solve this problem?

DanDiplo commented 1 year ago

Hi. I have it installed on a few v10 sites myself and I've not seen this error and nobody else has reported it. So I'd suspect it is to do with your particular set-up.

Usually these type of errors tend to arise because the JS in Umbraco hasn't updated. Have you tried restarting the application? Are you running on Windows? (I've never tested on Linux, I'm afraid).

If you look in App_Plugins do you see the DiploAuditLogViewer folder and has it got contents? If so it should have installed OK.

You can also try deleting temp Umbraco files in /umbraco/Data/TEMP/ folder. These will get regenerated on restart. As I say, normally these issues are fixed by restarting the application or reinstalling the Nuget package.

aphwong commented 1 year ago

image

Yes there are files and folder inside "App_Plugins" and I've also tried delete "TEMP" folder at "/umbraco/Data/". Restart the server also don't work for me. Here is the detail error in js file image

aphwong commented 1 year ago

Finally worked with the setting added below in appsetting.json.

"RuntimeMinification": { "UseInMemoryCache": true, "CacheBuster": "Timestamp" }

Not sure why it's work

DanDiplo commented 1 year ago

It certainly sounds like it is something to do with Umbraco and how it caches the minified JavaScript. My guess is that it was caching to disk before and that cache wasn't getting updated when you installed my package. Probably some issue in Smidge. Forcing it to use in memory cache allows the JS to regenerate properly and you get the latest updates, including the package scripts.

Anyway, glad you got it resolved and hopefully this might help anyone else with the same issue.