-
Notifications
You must be signed in to change notification settings - Fork 2.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
Move apps from apps to apps2 folder can cause issues #29807
Comments
GitMate.io thinks the contributor most likely able to help you is @PVince81. |
@mmattel did you check if oc_appconfig has hard-coded paths ? |
Just looked into the table. |
The text gets triggered at: core/settings/js/admin-apps.js at line 293
|
Just confirming @mmattel's work that I can move an app into a new directory, but as there is no path reference, the move will always be slightly broken. |
@VicDeo any clues as you're familiar with the resource locator ? |
@PVince81 I haven't touched resource locator itself yet, could be related to caching because AppManager uses cache to store app values |
From researching the codebase, it looks like it will need a bit of work to implement. However, it might be quite achievable. I'll add an issue to document what I think's required. |
@settermjd pls. keep me posted. Very interested about your findings 😃 |
I've created an issue, but I'm not sure if it's effectively a duplicate of this one. That said, it was quite interesting to follow the logic in the code to, almost, understand what's going on. |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
What happens if the app is in both folders? |
ad 1.) don´t know... but would be interested in the result, easy testing - just try 😄 ad 2.) in case you follow the config.sample.php description of See also issue #29839 ([Feature Request] make the apps2 folder default used in new installations) to make |
By design the most recent app should be loaded (by version). If the versions are the same - behavior is undefined, I guess app from the very first appdir will be loaded
By design one that is located in a writable appdir |
#29807 documents that moving apps from the core to a non-core apps folder manually can cause issues. Given that and the discussion in owncloud-archive/documentation#4276, I decided to start writing an app:move command, to make moving apps from the core apps directory, to a custom non-core apps directory simpler and less messy. When finished, the command will be able to: - List apps that can be moved - List any non-core app directories - Check that non-core app directories exist - Move one or more apps from the core apps directory to a non-core apps directory The other reason for doing this is to better familiarise myself with ownCloud's internals — something that, for quite some time, I've felt I've been lacking, and that has been hindering me from doing my work better.
Steps to reproduce
Expected behaviour
app should be enabled
Actual behaviour
4 example apps I tried
Info, Musik worked
Temporary Fix
In maintenace mode on, I needed to delete the app physically, then maintenance mode off, then I was able to download the app from the Marketplace (before it was identified as installed).
Server configuration
Operating system: Ubuntu 16.04
Web server: nginx
Database: mysql
PHP version: 7
ownCloud version: 10.0.4
Updated from an older ownCloud or fresh install: updated
Where did you install ownCloud from: tar
Signing status (ownCloud 9.0 and above):
The content of config/config.php:
List of activated apps:
Are you using external storage, if yes which one: local, smb, ftp, dropbox...
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Safari
Operating system: MacOs
Logs
ownCloud log (data/owncloud.log)
Based on the examples of Gallery and Files_Clipboard
The text was updated successfully, but these errors were encountered: