Skip to content
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

8.1.1 Enabling an app always triggers core update #18235

Closed
Aesculapius opened this issue Aug 12, 2015 · 4 comments
Closed

8.1.1 Enabling an app always triggers core update #18235

Aesculapius opened this issue Aug 12, 2015 · 4 comments

Comments

@Aesculapius
Copy link

After enabling an app from the built-in appstore, I can always just enable one app at a time. Clicking a second app to enabled, turns that one into a red 'failed'. Also, going back to files view, the update screen is triggered, telling me to upgrade (again) to 8.1.1. I'm forced to update at that point. After updating, the app appears to be installed correctly though.

Expected behavior:

  • I'd expect the app to be enabled instantly without an intervening update process.
  • Also I'd expect to be able to enable more apps at once, rather than moving to files app and back.

OC 8.1.1 running under Ubuntu 14.04 and PHP 5.5.9-1 with APCu enabled.

@karlitschek
Copy link
Contributor

@DeepDiver1975 Can you check this one? I know that you looked into that a while ago.

@PVince81
Copy link
Contributor

Third party apps get disabled during an update, so they don't get updated during that process (or maybe just the code but not the DB?)
When you reenable the app afterwards, its database needs to be updated. This is what triggers this update screen. The text is wrong, it should say "updating app" instead of core.

Here is work in progress to make this clearer: #17434

Let's keep this ticket here to discuss ways to make the experience smoother in the future.
Like you said, ideal would be the ability to reenable all apps on the fly and upgrade them at the same time.

@ghost
Copy link

ghost commented Aug 12, 2015

@PVince81 isn't the confusing message already tracked at #16272

@PVince81
Copy link
Contributor

@RealRancor yes, thanks. Then let's close this as duplicate.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants