Can't sign theme, still get warning

theming
themes

#1

The docs show this:

When copying the example theme supplied with ownCloud in apps/theme-example, make sure that you delete appinfo/signature.json. If you don’t, when you make changes, an integrity warning will be triggered, as the original theme is signed. This is slightly complicated by the fact that without the file a warning will be displayed. However, this is to be corrected in the next release, 10.0.3.

But I've got 10.0.4.4 Community Edition and I'm still getting this warning.

Also, the link that explains how to sign leads to a 404.

So, what's a guy to do?


#2

Thanks for noticing, this will be fixed.

the link should go to here

https://doc.owncloud.org/server/latest/developer_manual/app/advanced/code_signing.html?highlight=sign


#3

Ahh - thanks for that link.

Should I expect the warnings to also be fixed in a future release?


#4

Can you try to change the owner of the custom theme folder to www-data and see if the error persists?


#5

That did it!

Again - much appreciated. Time to read about hardening OwnCloud and fully understand the permissions...


#6

Glad to hear that :slight_smile: