Chris Bardell Posted June 30, 2020 Share Posted June 30, 2020 Our instance update last night automatically, ever since the update the Logo now is stretched. It never used to look like this before the update? I have tried to change the size of the logo within the employee portal settings but to get it to a size where it doesn't stretch i have to make it really small. Link to comment Share on other sites More sharing options...
Guest Chaz Posted June 30, 2020 Share Posted June 30, 2020 Hi @Chris Bardell, just wanted to confirm which portal this was in. Are you using service.hornbill.com/instancename or live.hornbill.com/instancename? It would also be useful to see the values you've set for the logo if possible. Link to comment Share on other sites More sharing options...
Frank Reay Posted June 30, 2020 Share Posted June 30, 2020 Same for us (see below). Employee Portal with settings as shown below which we haven't touched since moving to Employee Portal. Link to comment Share on other sites More sharing options...
Chris Bardell Posted June 30, 2020 Author Share Posted June 30, 2020 Hi @Chaz We are using the Employee Portal (live.hornbill.com/instancename) Values are below for you. This was fine and working up until the update that happened last night to Service Manager? Hope this helps, Chris Link to comment Share on other sites More sharing options...
Guest Chaz Posted June 30, 2020 Share Posted June 30, 2020 Thanks all, just looking at getting a fix out Link to comment Share on other sites More sharing options...
Chris Bardell Posted June 30, 2020 Author Share Posted June 30, 2020 Hi @Chaz, I just noticed Hornbill Service Manager had an manual update i could do. I have just updated Service Manager and it appears to have gone back to normal and the logo is now displaying correctly. Now using Service Manager build: 1967 . Maybe a bug in the previous build? Chris Link to comment Share on other sites More sharing options...
Guest Chaz Posted July 1, 2020 Share Posted July 1, 2020 @Chris Bardell the timing of the build was just coincidence, it was a bug in the Collaboration Core UI build which was automatically pushed out around the time you saw the Service Manager update. Glad it's sorted, apologies for the inconvenience. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now