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

Update from 2.3 to 2.4 breaks dashboard #5086

R-J opened this Issue Jan 31, 2017 · 1 comment


None yet
3 participants

R-J commented Jan 31, 2017

In 2.4 applications/vanilla/controller/class.settingscontroller.php has been deleted.

The normal upgrade process does not include a deletion step, so the file from 2.3 still exists. As a consequence, all /dashboard/settings links are routed through that router which standard method is "managecategories". That's why several settings are not accessible after a standard update.

It might be better to still supply such a file with only an index method that tells the user something like 'Please delete the file "'.__FILE__.'" manually' and also give the link to the corresponding views "applications/vanilla/views/settings"

At least the fact that these artifacts exist and must be deleted should be told to admins.

@R-J R-J changed the title from Update to from 2.3 to 2.4 breaks dashboard to Update from 2.3 to 2.4 breaks dashboard Jan 31, 2017


This comment has been minimized.


linc commented Jan 31, 2017

See also #2518

@linc linc added this to the 2017-Q1-4 milestone Jan 31, 2017

beckyvb added a commit that referenced this issue Feb 17, 2017

Check for the existence of deleted files at /utility/upgrade endpoint
Informs users of files that exist in their installation that have been deleted since the last release.

Closes #2518
Closes #5086

@linc linc closed this Mar 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment