Conversation
… not chatgpt-first PR #458 added getDefaultRoute() which iterates a hardcoded FEATURE_ROUTE_ORDER (chatgpt, deepseek, grok, ...). Because chatgpt is the first entry and is enabled on basically every site, every visitor to '/' was forcibly redirected to /chatgpt/conversation/new — operators couldn't change the landing page even by reordering or disabling features. This change walks site.features in the order the API returned them (Python dict insertion order is preserved in JSON) and picks the first enabled key that maps to a known landing route. On hub.acedata.cloud, where features start with veo, wan, chat, flux, grok, ..., new visitors will now land on /veo (the operator-intended first feature) instead of /chatgpt/conversation/new. If a site config has no recognised landing feature, we still fall back to chatgpt-conversation-new as before.
…s to actual path
The bigger half of the bug: getDefaultRoute() returned a bare string
like 'chatgpt-conversation-new', which is a vue-router route NAME
(maps to path '/chatgpt/conversations'). When vue-router sees a bare
string in 'redirect', it treats it as a PATH, so the browser was sent
to the literal URL '/chatgpt-conversation-new' which matches no route
and rendered an empty layout.
Returning { name } makes vue-router resolve the actual registered path.
Member
Author
|
Pushed b80a65a — fixes the bigger half of the bug.
Now returns |
Germey
approved these changes
Apr 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
https://hub.acedata.cloud/(and every other Nexior site) was forcibly redirected to/chatgpt/conversation/new, regardless of how the site operator configuredfeatureson the platform side.The bug lives in
src/router/index.ts(introduced in #458):getDefaultRoute()iterates a hardcodedFEATURE_ROUTE_ORDERwhose first entry is alwayschatgpt. Sincechatgptis enabled on essentially every site, the loop always picks ChatGPT and operators have no way to change the landing page.Fix
Walk
store.state.site.featuresin the order the platform API returned them (Python dict + JSON preserve insertion order) and pick the firstenabled: truekey that maps to a known landing route.For
hub.acedata.cloudwhose feature insertion order isveo, wan, chat, flux, grok, ..., new visitors will now land on/veo— the operator-intended first feature — instead of/chatgpt/conversation/new. Operators who want ChatGPT first just need to putchatgptfirst in the site's features map.If a site has no recognised landing feature at all, we still fall back to
chatgpt-conversation-new, so behaviour is identical for any pathological config.No template/HTML/store changes; only the redirect resolver.