summaryrefslogtreecommitdiffstats
path: root/core/ajax/update.php
Commit message (Collapse)AuthorAgeFilesLines
* Update license headersJenkins for ownCloud2015-03-261-0/+25
|
* Merge pull request #13513 from owncloud/repair-legacystoragenofatalfailMorris Jobke2015-03-111-0/+6
|\ | | | | Do not abort when meeting unfixable legacy storages
| * Properly forward repair errors and warningsVincent Petry2015-02-271-0/+6
| | | | | | | | | | This makes repair errors and warnings visible for the user when upgrading on the command line or in the web UI.
* | Verify CSRF token already in update.php and not the EventSource codeLukas Reschke2015-03-091-0/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issue report: > Hum, well I upgraded the package then visited the web interface to trigger the update and it failed; the UI would say there was a possible CSRF attack and after that it'd be stuck in maintenance mode. Tried a few times (by editing maintenance to false in owncloud.conf) and same result each time. That smells partially like an issue caused by our EventSource implementation, due to legacy concerns the CSRF verification happens within the EventSource handling and not when the actual endpoint is called, what happens here then is: 1. User has somehow an invalid CSRF token in session (or none at all) 2. User clicks the update button 3. Invalid CSRF token is sent to update.php - no CSRF check there => Instance gets set in maintenance mode 4. Invalid CSRF token is processed by the EventSource code => Code Execution is stopped and ownCloud is stuck in maintenance mode I have a work-around for this problem, basically it verifies the CSRF token already in step 3 and cancels execution then. The same error will be shown to the user however he can work around it by refreshing the page – as stated by the error. I think that’s an acceptable behaviour for now: INSERT LINK To verify this test: 1. Delete your ownCloud cookies 2. Increment the version in version.php 3. Try to upgrade => Before the patch: Instance shows an error, is set to upgrade mode and a refresh does not help => After the patch: Instance shows an error, a refresh helps though. This is not really the best fix as a better solution would be to catch such situations when bootstrapping ownCloud, however, I don’t dare to touch base.php for this sake only, you never know what breaks then… That said: There might be other bugs as well, especially the stacktrace is somewhat confusing but then again it installing ownCloud under /usr/share/owncloud/ and I bet that is part of the whole issue ;-)
* Revert "Updating license headers"Morris Jobke2015-02-261-25/+0
| | | | This reverts commit 6a1a4880f0d556fb090f19a5019fec31916f5c36.
* 3rd-party apps are disabled on upgrade - refs #14026Thomas Müller2015-02-241-8/+18
|
* Updating license headersJenkins for ownCloud2015-02-231-0/+25
|
* Inject configVictor Dubiniuk2014-12-101-1/+2
|
* Use httphelper and cache response even when it emptyVictor Dubiniuk2014-12-061-1/+4
|
* Merge pull request #10739 from owncloud/eventsource-publicLukas Reschke2014-09-081-1/+1
|\ | | | | Add EventSource to the public API
| * Better phpdoc and method namingRobin Appelman2014-09-041-1/+1
| |
| * Use the public api to get event sourcesRobin Appelman2014-09-031-1/+1
| |
* | Fix upgrade process when apps enabled for specific groupsVincent Petry2014-09-021-0/+4
|/ | | | | | | Fix issue where the currently logged user was causing side-effects when upgrading. Now setting incognito mode (no user) on update to make sure the whole apps list is taken into account with getEnabledApps() or isEnabled().
* Add require_once to update.php due to routingLukas Reschke2014-08-221-0/+1
| | | | Fixes https://github.com/owncloud/core/issues/10585 Partially reverts 52d5429768acdb87b2dc2efedc89eb4ad0d29139
* Merge pull request #10522 from owncloud/removeLoadAppScriptblizzz2014-08-211-1/+0
|\ | | | | Remove loadAppScriptFile
| * Add update route to coreLukas Reschke2014-08-191-1/+0
| |
* | Send feedback from upgrading apps to the upgrade uiRobin Appelman2014-08-041-0/+6
|/
* Simulate apps database schema update on upgradeVincent Petry2014-06-041-0/+3
| | | | | When upgrade, also simulate the database schema update for apps before doing the actual upgrade.
* Now showing disabled apps as upgrade status lineVincent Petry2014-05-271-0/+8
| | | | | - Added app id in update overview. - Added status message for disabled app for CLI upgrade and web upgrade
* Merge branch 'master' into load-apps-proper-masterThomas Müller2014-03-211-9/+0
|\ | | | | | | | | | | | | Conflicts: apps/files/ajax/rawlist.php cron.php ocs/v1.php
| * drop file cache migration OC5 -> OC6Thomas Müller2014-03-181-9/+0
| |
* | remove some more global variable $RUNTIME_NOAPPSThomas Müller2014-02-061-1/+0
|/
* adding translations to update eventsThomas Müller2013-08-271-12/+13
|
* split upgrade logic from ajax fileRobin Appelman2013-07-061-107/+28
|
* Add undefined verision variablesMichael Gapczynski2013-05-171-1/+3
|
* Connect watcher failure function to the failure signalBart Visscher2013-05-041-1/+1
|
* Move start of the maintenance mode to the ajax callBart Visscher2013-05-041-0/+3
| | | | Make sure the update page is shown in a browser. And not an ajax request
* port 22c8194cc8fde88957dbc8c6d9e253fac3c637bbArthur Schiwon2013-04-021-3/+7
|
* Add missing backticks.root2013-03-301-2/+2
| | | | Especially at user without "" PostgreSQL likes to fail.
* Remove Debug outputArthur Schiwon2013-03-271-2/+0
|
* Upgrade FileCache on ownCloud upgrade for all users with filesArthur Schiwon2013-03-271-0/+45
|
* Clear the CSS and JS cache earlier to make sure update goes smoothlyMichael Gapczynski2013-03-051-4/+0
|
* Disable prepared query caching while doing an upgradeRobin Appelman2013-02-261-1/+2
|
* Tweak failure message and throw exceptions from updateDbFromStructure()Michael Gapczynski2013-01-051-4/+5
|
* Remove old data directory protection from update, should already have taken ↵Michael Gapczynski2013-01-051-8/+0
| | | | place or not working because the server isn't Apache
* Use hooks to send updates from appsMichael Gapczynski2013-01-041-8/+46
|
* Basic update progress of database update onlyMichael Gapczynski2013-01-031-0/+36
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-30 10:10:47 +0000