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

Branding options to skip 2nd wizard step #8665

Closed
michaelstingl opened this issue May 28, 2021 · 2 comments · Fixed by #8878
Closed

Branding options to skip 2nd wizard step #8665

michaelstingl opened this issue May 28, 2021 · 2 comments · Fixed by #8878
Labels
p2-high Escalation, on top of current planning, release blocker
Milestone

Comments

@michaelstingl
Copy link
Contributor

2nd wizard step looks like this:

image

(forceVirtualFilesOption)

We’d need another option to prevent users choosing their local sync folder.

In case both parameters are set, 2nd wizard step should be skipped, similar as 1st wizard step is skipped with fixed URL. (Only in case of errors, this screen is shown)

@github-actions
Copy link

This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Jun 28, 2021
@TheOneRing TheOneRing removed the Stale label Jun 28, 2021
@TheOneRing TheOneRing added this to the 2.10.0 milestone Jun 28, 2021
@michaelstingl michaelstingl modified the milestones: 2.10.0, 2.9.0 Aug 9, 2021
@michaelstingl michaelstingl added the p2-high Escalation, on top of current planning, release blocker label Aug 9, 2021
@TheOneRing TheOneRing linked a pull request Aug 10, 2021 that will close this issue
@jnweiger
Copy link
Contributor

Confirmed fixed in 2.9.0-rc1

When ...-theme.h contains

    bool wizardSkipAdvancedPage() const { return true; }

then the client automatically chooses a sync folder name all by itself and starts syncing immediately after the user authenticated with a server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants