95 Commits (5cd1880daa048a685da689c7f41a2e50486494de)

Author	SHA1	Message	Date
Vincent Petry	a64652e12a	Remove 3rd party text for disabled apps on update	11 years ago
Thomas Müller	d3ac73c0c9	Remove OC_Log	11 years ago
Morris Jobke	f63915d0c8	update license headers and authors	11 years ago
Morris Jobke	064f5204cc	Persist the state of the maintenance after an upgrade ... * if maintenance mode was enabled before an upgrade it will be enabled afterwards too * fixes #16429	11 years ago
Jenkins for ownCloud	b585d87d9d	Update license headers	11 years ago
Lukas Reschke	c0a02f1615	Verify CSRF token already in update.php and not the EventSource code ... 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 ;-)	11 years ago
Vincent Petry	22bc37cb82	Properly forward repair errors and warnings ... This makes repair errors and warnings visible for the user when upgrading on the command line or in the web UI.	11 years ago
Morris Jobke	06aef4e8b1	Revert "Updating license headers" ... This reverts commit 6a1a4880f0.	11 years ago
Thomas Müller	bbf7f56f94	3rd-party apps are disabled on upgrade - refs #14026	11 years ago
Jenkins for ownCloud	6a1a4880f0	Updating license headers	11 years ago
Victor Dubiniuk	c9fd3c9d29	Inject config	11 years ago
Victor Dubiniuk	303fce44f4	Use httphelper and cache response even when it empty	11 years ago
Robin Appelman	fa3393674c	Better phpdoc and method naming	12 years ago
Robin Appelman	65608d7c92	Use the public api to get event sources	12 years ago
Vincent Petry	e05b95636b	Fix upgrade process when apps enabled for specific groups ... 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().	12 years ago
Lukas Reschke	4aca46046b	Add require_once to update.php due to routing ... Fixes https://github.com/owncloud/core/issues/10585 Partially reverts 52d5429768	12 years ago
Lukas Reschke	ab12bd292d	Add update route to core	12 years ago
Robin Appelman	3184983565	Send feedback from upgrading apps to the upgrade ui	12 years ago
Vincent Petry	5b97369b00	Simulate apps database schema update on upgrade ... When upgrade, also simulate the database schema update for apps before doing the actual upgrade.	12 years ago
Vincent Petry	02f682b156	Now showing disabled apps as upgrade status line ... - Added app id in update overview. - Added status message for disabled app for CLI upgrade and web upgrade	12 years ago
Thomas Müller	6b9ae27b90	drop file cache migration OC5 -> OC6	12 years ago
Thomas Müller	0db5fead8e	remove some more global variable $RUNTIME_NOAPPS	12 years ago
Thomas Müller	9909b8b726	adding translations to update events	13 years ago
Robin Appelman	58f473d734	split upgrade logic from ajax file	13 years ago
Michael Gapczynski	4687f50e75	Add undefined verision variables	13 years ago
Bart Visscher	ff64c87adb	Connect watcher failure function to the failure signal	13 years ago
Bart Visscher	41f7eb948a	Move start of the maintenance mode to the ajax call ... Make sure the update page is shown in a browser. And not an ajax request	13 years ago
Arthur Schiwon	e25c1f3130	port 22c8194cc8	13 years ago
root	7f74f08808	Add missing backticks. ... Especially at user without "" PostgreSQL likes to fail.	13 years ago
Arthur Schiwon	18554059a4	Remove Debug output	13 years ago
Arthur Schiwon	e2afd0cb42	Upgrade FileCache on ownCloud upgrade for all users with files	13 years ago
Michael Gapczynski	5300d6ad55	Clear the CSS and JS cache earlier to make sure update goes smoothly	13 years ago
Robin Appelman	47b899e0c8	Disable prepared query caching while doing an upgrade	13 years ago
Michael Gapczynski	f6426cee04	Tweak failure message and throw exceptions from updateDbFromStructure()	13 years ago
Michael Gapczynski	6b2216f0d6	Remove old data directory protection from update, should already have taken place or not working because the server isn't Apache	13 years ago
Michael Gapczynski	e7eea3dd2e	Use hooks to send updates from apps	13 years ago
Michael Gapczynski	7505837079	Basic update progress of database update only	13 years ago