-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
style/design/css broken after upgrade from 12 to 13 #8279
Comments
cc @nextcloud/theming @juliushaertl Correct? |
@MorrisJobke Yes, but the JS cache should also be cleared:
|
@MorrisJobke @juliushaertl What happen if the resources are stored in S3??? None of those commands works. Do you know any approach to clean appdata files if they are saved on a S3 environment instead of local?? Or we need to get in the S3 and manually remove the objects?? Since on the S3 the files are stored by object id and not by path, we cant detect those specific files... |
@averdecia there is a cleanup done after each upgrade. We also force a filename change on every new version so you should not have any issue while upgrading now. |
@skjnldsv the problem that i am facing is not during an upgrade to 13. I am testing a rollback process back to NC12 in case that needed because of any further issue on NC13. Right now the only visible problem is specific with settings.css file. The file is loaded in the NC13 route instead of the NC12 way. That file is rendered in NC12 in the following path: NC13 uses the following path: After the rollback to NC12 the route remains pointing to NC13 path, i suppose that old cache files from NC13 stored on the S3 are corrupted, and we need to update those files on the S3 to the NC12 files. |
We don't support rollback. |
Steps to reproduce
Expected behaviour
the column headers "name", "size", "last changed" should be aligned to their table contents, the folder/file names should be to the right of the icon.
Actual behaviour
Server configuration
Operating system: CentOS 7
Web server: httpd 2.4.29
Database: mariadb 10.2.12
PHP version: 7.1.14
Nextcloud version: (see Nextcloud admin page) 13.0.0.14
Updated from an older Nextcloud/ownCloud or fresh install: updated
Where did you install Nextcloud from: 12.0.3.3
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: nope
Are you using encryption: no
Are you using an external user-backend, if yes which one: LDAP
LDAP configuration (delete this part if not used)
LDAP config
Client configuration
Browser: Firefox 58.0.1, Chrome 64.0.3282.140, some android browsers
Operating system: Fedora 27 and Android O
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: