nextcloud / server

☁️ Nextcloud server, a safe home for all your data
https://nextcloud.com
GNU Affero General Public License v3.0
26.71k stars 4k forks source link

NC14: core/img/places/contacts-dark.svg missing #10443

Closed ghost closed 6 years ago

ghost commented 6 years ago

I just recognized, that the file core/img/places/contacts-dark.svg is missing in the git-version of nextcloud 14. If You are using a light background, there will be a "hidden" link to the contacts-search in the upper right of Your nextcloud-instance: no-contacts-dark svg

Would be nice to get the image back ;-)

nextcloud-bot commented 6 years ago

GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/3710 (Missing border in Contacts), https://github.com/nextcloud/server/issues/5931 (Address fields missing from contact), https://github.com/nextcloud/server/issues/4557 (Missing tooltips in contacts menu actions.), https://github.com/nextcloud/server/issues/4830 (Missing default Address Book (Contacts)), and https://github.com/nextcloud/server/issues/539 (Contacts can't handle contact picture if TYPE is missing).

rullzer commented 6 years ago

@skjnldsv

skjnldsv commented 6 years ago

This is weird because the class should still exists. Is the icon loaded in css @team-a2 ?

ghost commented 6 years ago

#contactsmenu .icon-contacts { background-image: url('/apps/theming/css/../../../core/img/places/contacts-dark.svg'); }

skjnldsv commented 6 years ago

@juliushaertl theming? :)

ghost commented 6 years ago

In my instance no theming other to the clean install is activated (just a light grey background-color set).

juliushaertl commented 6 years ago

@team-a2 You have a grey header instead if the nextcloud blue, so the theming app is doing its job there ;)

I'll have a look

ghost commented 6 years ago

Yes, You are right, I just ment that I do not use a separate custom theme...

rullzer commented 6 years ago

What version of NC is this?

ghost commented 6 years ago

NC 14.0.0 Beta1, todays git pull (problem has already existed in git version before beta1)