You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2022. It is now read-only.
Describe the bug
The setup wizard procedure stops at step 4 and does not proceed towards the request for the first access credentials.
To Reproduce
Steps to reproduce the behavior:
.../paperwork/frontend/public
Click on "NEXT"
verify the dependence if ok (and it's ok)
Click on "NEXT"
MySQL login credentials are required; input them and Click "Check Credentials";
click on "NEXT"
The "Customized ypur paperwork" page: there is no need to change anything
Click on "NEXT"
nothing happens
Expected behavior
the wizard should ask for the first credentials but the page does not appear and therefore it is impossible to proceed and complete the setup
Desktop (please complete the following information):
OS: Windows 10
Browser chrome, firefox, edge
Additional context
We tried to change the counter in the file / app / storage / config / setup by inserting the number "5" or the number "6" instead of "4" but there is no effect. If you enter the "7" the next page "login" does not work (blank page)
The text was updated successfully, but these errors were encountered:
Describe the bug
The setup wizard procedure stops at step 4 and does not proceed towards the request for the first access credentials.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
the wizard should ask for the first credentials but the page does not appear and therefore it is impossible to proceed and complete the setup
Desktop (please complete the following information):
Additional context
We tried to change the counter in the file / app / storage / config / setup by inserting the number "5" or the number "6" instead of "4" but there is no effect. If you enter the "7" the next page "login" does not work (blank page)
The text was updated successfully, but these errors were encountered: