Web Setup Wizard not visible in backend (V.2.1.2) ONGOING

[dharake]

The component manager page returns a 404 when Magento is installed using the more secure /path/to/magento/pub (vs. /path/to/magento) as the system web root in Magento CE 2.1.2
Preconditions:
Magento CE 2.1.2

Steps to reproduce:
Install Magento
Configure Web Root to point to Magento's pub folder
Navigate in admin to System -> Web Setup Wizard

Expected result
Web Setup Wizard page displays

Actual result
No Menu item for Web Setup Wizard
Standard Magento 404 (Whoops, our bad...) page displays if manually directed to URL
When using SSL & Varnish: Receive "This site can’t provide a secure connection" ERR_SSL_PROTOCOL_ERROR

[dharake]

A work around that was achieved on one client's site:

Procedure:
Install Magento 2.1.0
Use the web setup wizard to upgrade Magento to 2.1.2

Result:
You should have the most up to date version with a working Web Setup Wizard

[veloraven]

@dharake thank you for your report.
We already have internal ticket MAGETWO-52799 for this issue.
I have updated it with link to this report.

[dharake]

@veloraven thanks for your help. There was a commit in June for MAGETWO-52799, 2f9ccf0

Any idea if this works? If so would it not have been included in last release in Ocotber of Magento 2.1.2?

[timstoel]

@dharake I am not sure if rolling back to 2.1.0 is an option on our production site. I believe we installed 2.1.1 for our production setup.

Is there a way to get the same results as installing 2.1.0 and upgrading to 2.1.2 by editing some files related to this issue?

[dharake]

Possibly this commit works : 2f9ccf0

Awaiting confirmation from @veloraven

If you test it let me know, but obviously don't do this on your production site :)

[timstoel]

@dharake

In my 2.1.1 installation the lines in app/code/Magento/Backend/etc/di.xml that need to be deleted are not present. In lib/internal/Magento/Framework/App/DocRootLocator.php the file already matches the commit.

I added the three lines to app/code/Magento/Backend/etc/adminhtml/di.xml and nothing has changed.

[dharake]

Ok @timstoel thanks for that. We'll have to wait and see what the Magento peeps have to say. Personally I wouldn't hold my breath seeing they have been sitting on this issue since April. Really poor job I'm afraid, this undermines the whole Magento ecosystem if no one can install mods.

[timstoel]

@dharake So I could get around this by installing 2.1.0 and upgrading to 2.1.2? It would take some time to move our 5000 items with attributes and template and everything, but I've got to move forward somehow. My other option is Magento 1.9 and moving to 2 later on. I can't just sit here and wait for Magento to fix this.

[dharake]

See how you get on with that on a blank install first, but it worked for me. Conversely you'd have to import all the items back to 1.9 anyway, just to have to upgrade again to 2. So although it's a pain, that would still be my recommendation. Especially if you've been working on the templates on 2, because they won't work for 1.9

[timstoel]

I'll spin up another VM with 2.1.0, upgrade it and report back. There is the URL workaround as well, maybe I need to get to 2.1.2 and set up all of my add-ons before I install Varnish.