-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Name' from Theming should not be used in 'Version' in the admin settings #7578
Comments
That's not really a regression, because we did this in the past always like that. @karlitschek What is your opinion here? I would be fine to hardcode "Nextcloud" there, because it is also only visible on the admin settings anyways. |
The thing @mario ran into was in the status.php I bet. So it is not exactly the same issue. I don't have a strong preference here. But I guess some buisnesses want the branded name in status.php. |
Yes, I used productname in status.php to identify the instance as Nextcloud. I have since removed the check since it's easily change-able anyway :) |
There are scenarios it should be possible to hide 'Nextcloud' completely. Even for the Admin. This is mainly for 'real' themes of course. So not sure we should change the current behaviour. |
I'm fine with "MyName Version", but maybe you should just omit NAME in settings/general in the "Version" section? |
I think we leave it as it is, since it does not really fix a real issue, right? Let me close it since it is stale for awhile. We can still reopen if it is a real problem. |
Steps to reproduce
Expected behaviour
Version should read "Nextcloud VERSION"
Actual behaviour
Version reads "NAME VERSION"
Note that this also baffled the author of the talk app since he used it (until a couple of days ago) to identify that the server is a nextcloud instance. 'Name' should be a display-only value, not to identify the product. The product neets a separate variable / identifier (and probably has). This should be used to display the "Product + Version" here, too.
The text was updated successfully, but these errors were encountered: