I upgraded our Test environment to Web Client 11 Update 7 and the Laserfiche logo in the top left corner is not displaying correctly:
Update 7 did make some changes to the JS and CSS related to the logo.
It appears that your test environment has some custom CSS (given the orange navbar), so although the changes should have been in a different part of the file it might be worth double-checking that the process of applying them didn't clobber the CSS updates somehow. I suppose it's also worth clearing your browser cache, although given the nature of the update I don't know why that would help.
We did alter the color of the navbar, but that was the only change we made.
We'll look into it further. Were you updating from Update 6?
Yes, sir.
I see the logo was switched to using an SVG instead of PNG.
Changing the .navbar .brand class to width 110px, padding 20px 5px 10px, and margin-top to 5px seems to fix the issue with it not displaying correctly.
The official file is supposed to have width 115px, padding 10px 5px 10px, and margin-top 3px (as well as a couple of other changes that might be related), so your changes make sense. The main question on our end is whether the update didn't update the file correctly, or whether there's something else going on.
Are you applying these changes by editing Browse.min.css directly, or via some other method?
I made the change using F12 Dev Tools. I haven't actually changed the css file yet.
This is what is in my Browse.min.css file:
.navbar .brand{display:block;float:
left;padding:10px 5px 10px;margin-top:13px;margin-right:0;margin-left:15px;font-size:20px;font-weight:200;color:#767676;text-shadow:0 1px 0 #fff;background-repeat:no-repeat;width:100px}
Some more investigation on our end suggests that the patch won't update that CSS file if it's been modified, and that's probably what you're seeing. We'll see if we can make the update process more robust, but for a quick fix you should be able to remove the CSS file(s) in question (I'd guess any that you've made the navbar color changes to) and trigger a repair of the web client install to replace them with the files from the update. (You'll need to re-apply your customizations after this).
We upgraded our Production environment last night and didn't have any issues with the logo.