-
Notifications
You must be signed in to change notification settings - Fork 31
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
Feature request: Allow default external route/id to be customized #472
Comments
Hi, how are you setting the default app? Are you using https://apps.nextcloud.com/apps/apporder? The app no longer works on Nextcloud 25+ (See https://github.com/juliushaertl/apporder). I think you will have to request this feature in nextcloud/server#4917. The implementation should not just iterate the apps but the actual navigation entries. |
Hey @provokateurin, I was talking about setting the default app via NC's If you have To customize this, it would be nice, to pick one of the external sites as the default. |
Ah I see. Unfortunately that would require significant changes in the server and I don't think the amount of effort is justified. If someone wants to create a PR for this I will be happy to review it. |
This actually has been fixed in nextcloud/server#47523 and will be available in Nextcloud 31. |
It would be very nice, if the default route/id inside of the
external
app could be customized. E.g. the App that gets loaded when you open the URL/apps/external
(without any ID/parameter). It will lead you to/apps/external/1
by default.This is necessary, because when you try to set the
external
app as yourdefaultapp
in the Nextcloud config, you can't pass in any id or parameters (e.g.external/2
will not work as a value fordefaultapp
).So if you want to use any of the external apps as your defaultapp, you always need to make it have id
1
, which can require some manuel DB editing. Instead it would be nice if there was a checkbox/radiobox/dropdown next to the individual external sites and you could pick one to be the default route target.I'd be happy to contribute a PR, if I get positive feedback on this feature request.
The text was updated successfully, but these errors were encountered: