This setup screen is confusing, especially for someone installing neos for the first time. It requires knowledge of how multiple packages, configuration and sites interact - while you e.g. only want to a) test the demo or b) start with a fresh, empty install.

• A question that arises is: If I fill out the fields for a new site package, does the still selected site package at the top still get used? If not, why is it still active?
• Do I even need to create a new site package with a dummy site?
• And if I just want to try the demo, do I still have to specify a site name?

(from https://discuss.neos.io/t/setup-tool-confusing-screen/4351)

Jira issue originally created by user @hhoechtl:

I think it would be good to introduce some kind of loading animation during the database creation step in the setup as you only see that the application is doing something by checking the browsers status.
As creating the database can take up to 30 seconds it would be good to indicate to the user that there's something happening and therefore prevent him for reloading.

Jira-URL: https://jira.neos.io/browse/NEOS-1434

Jira issue originally created by user wexi:

When installing Neos, if you choose the option to create a new site package, the setup does not proceed to step 5 but instead gives you the setup login screen.

Jira-URL: https://jira.neos.io/browse/NEOS-1739

Jira issue originally created by user Martelinho:

Setup of Neos doeesn't work when using Imagick Library.
I always get the attached 500 server error when calling the setup in the browser (http://DOMAIN.TLD/setup/). The error occurs after entering the setup password and continuing. I think its in the procedure of checking the requirements for image manipulation.
Setup works fine when using GD Library.

The following versions are used:
PHP => 7.0.8
imagick => 3.4.1
ImageMagick => 7.0.1-8 Q16 x86_64 from 2016-06-01

Has anyone an idea as I'm new to NEOS and its community?

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-1864

Jira issue originally created by user brgmn:

If a site package that already exists with the same name should be created the setup wizard throws an exception. The package name should be checked during inserting and a nice error message should be shown.

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-1055

Jira issue originally created by user codesnip:

When performing the initial Neos-Setup on an MacOS Lamp-Environment, assets are missing: !Bildschirmfoto 2015-11-03 um 22.56.30.png|thumbnail!

Runnign ./flow resource:publish, as adviced by aertmann helps. Shouldn't this happen automatically before?

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-1651

Jira issue originally created by user brgmn:

At the moment it's a bit confusing to choose between importing or creating a site in the kickstarter part of the setup wizard. Maybe there could be just a radiobutton added and the inactive option be faded out (see screenshot). Currently it is possible to select to import a site but there's no way back to create a new site if you have selected a site to import before (empty option missing).

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-1017

Jira issue originally created by user rodi:

During the first setup step (Neos requirements check) the output of information in the image manipulation section should be reduced if one of the needed image extensions (gd, gmagick, imagick) is found.

I don't know if it is better to hide it completely or to offer a link / button to show the additional information.

And there is also the question how to communicate unsupported image types

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-1307

Jira issue originally created by user jrenggli:

I think it would be a good thing to provide some CSH in the new setup wizard.
For example using the popover functionality and the icon-exclamation-sign icon.

Just a few lines of descriptive information will make it more user friendly imho.

Jira-URL: https://jira.neos.io/browse/NEOS-539

The setup login is not adapted to new POST arguments and won't work currently.

Jira issue originally created by user soee:

At the moment there are 2 ways to enter database details to be used by Setup wizard. One is to enter them in form, second is to manually enter them in global Settings.yaml file. In both cases Setup will see and use them.

There is a problem if we want to enter DB details for Development or Production context though. If we enter them in one of this configuration files:

Configuration/Development/Settings.yaml

or

Configuration/Production/Settings.yaml

Setup wizard will not see them at all.

Maybe it would be a good idea to add support for this 2 configuration files and if they exist and contain DB details, than use them in Setup wizard.

But there are some questions:

• what if Development and Production configuration contain different DB details - should we fill both with default data?

• is it possible that there might be more than this 2 context configurations?

• should Setup wizard store DB details entered in form in Development/Production configuration files?

  Jira-URL: https://jira.neos.io/browse/NEOS-1443

With Flow 7 Components will no longer be supported. However, looking at the current code of the component (https://github.com/neos/setup/blob/master/Classes/Core/ConfigureRoutingComponent.php), it just forces the router to load the Setup Routes.yaml and will then run as long as the package exists?

Jira issue originally created by user mrimann:

We're running a Neos 1.2.x based installation based on Ubuntu 14.04 with PHP 5.5.9-1ubuntu4.5 - the access via Browser is served by Nginx which executes php5-fpm (separate Pool for the vHost's User-Account).

The installation works pretty well, the Frontend is accessible and a visitor can navigate and view the pages -> all fine.

But calling the Setup via http://neos.cluster-1.dev.internezzo.ch/setup throws the following error message:

The path to your PHP (cli) binary could not be detected. Please set it manually in Configuration/Settings.yaml. (More information)

This avoids accessing the Setup.

Everything else seems to work pretty fine, even executing the command-controllers from a shell. So the error message is probably just misleading.

Jira-URL: https://jira.neos.io/browse/NEOS-958

Jira issue originally created by user @kitsunet:

The setup says:

"No suitable PHP extension for image manipulation was found. You can continue the setup but be aware that Neos might not work correctly without one of these extensions."

If no image manipulation library is installed the setup will happily accept that with above message but then throw:

Notice: Undefined index: imagineDriver in /var/www/awesome/NeosX/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_Neos_Setup_Step_NeosSpecificRequirementsStep.php line 135
TYPO3\Flow\Error\Exception thrown in file
Packages/Framework/TYPO3.Flow/Classes/TYPO3/Flow/Error/ErrorHandler.php in line 80.
Reference code: 2016011622520313f326

So we need to either catch that (by setting a useful value for this setting) or say that you cannot proceed without lib.

Jira-URL: https://jira.neos.io/browse/NEOS-1761

Jira issue originally created by user @robertlemke:

Once the setup has been run successfully, the user should be asked if the setup tool should now be deactivated ("recommended"). And if the users chooses to do so, the package TYPO3.Setup is disabled.

Jira-URL: https://jira.neos.io/browse/NEOS-771

running

FLOW_CONTEXT=Testing flow setup:database

should place the config in the correct context ;)

Jira issue originally created by user garvitdelhi:

Instead of throwing an exception when step is not found in the setup, we might also quietly jump to step 0 or may be another step.

Jira-URL: https://jira.neos.io/browse/NEOS-994

Jira issue originally created by user @hhoechtl:

If you run the setup and you get an error having a "more information" link pointing to https://wiki.typo3.org/Exception/Flow/1341839376

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-1886

With this commit 460f48e a new migration was applied. Therefore the changed key should be used in our templates as well