search

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.56k stars 9.32k forks source link

Can't Access Component Manager #4159

Closed astorm closed 8 years ago

astorm commented 8 years ago

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.

  1. Install Magento
  2. Configure Web Root to point to Magento's pub folder
  3. Navigate in admin to System -> Web Setup Wizard

    Expected result

  4. Web Setup Wizard page displays

    Actual result

  5. Standard Magento 404 (Whoops, our bad...) page displays
themew commented 4 years ago

Not working in OpenLiteSpeed with webroot in /pub/ Still getting 404 with Magento 2.3.4

dvershinin commented 4 years ago

The big question is not this bug. The big question is Magento 2 Q/A, speed of fixing things, inadequate closing of tickets then further neglect.

@KrystynaKabannyk was the issue really fixed when you closed it? Following all the scrolling thereafter it's obvious that it at least returned very soon, or likely never been truly fixed. Based on the volume of complaints, it has to be reopened.

It takes a second to realize how people are filing issues here and in other closed tickets: Typed a problem on Google search, landed up here, commented here. But the QA team is not looking at tickets which are closed or simply putting them to the lowest priority despite them actually being important and trivial to fix, like this one.

Something must change with the Magento team's workflow. No premature closing of tickets, please. At least some monitoring set to the volume of complaints on closed tickets, please.

dharake commented 3 years ago

Guys the component manager, see entire web setup wizard and GUI module control have been deprecated (its somewhere in release notes of 2.4.1 i think). You need to use ssh here on out, to the best of my knowledge.

16203041916823178768749054648148

dharake commented 3 years ago

Your Magento is shit. It simply doesn't work after clean installation with Docker. 2.4.2 Can't visit any page of web app =)

I gave up trying to use docker for magento

dharake commented 3 years ago

The big question is not this bug. The big question is Magento 2 Q/A, speed of fixing things, inadequate closing of tickets then further neglect.

@KrystynaKabannyk was the issue really fixed when you closed it? Following all the scrolling thereafter it's obvious that it at least returned very soon, or likely never been truly fixed. Based on the volume of complaints, it has to be reopened.

It takes a second to realize how people are filing issues here and in other closed tickets: Typed a problem on Google search, landed up here, commented here. But the QA team is not looking at tickets which are closed or simply putting them to the lowest priority despite them actually being important and trivial to fix, like this one.

Something must change with the Magento team's workflow. No premature closing of tickets, please. At least some monitoring set to the volume of complaints on closed tickets, please.

Hopefully Adobe help steer them in a better direction 🤞

mateuszrusiecki commented 3 years ago

Hopefully Adobe help steer them in a better direction

@dharake no they won't. It just can not be done :)

liquidia commented 3 years ago

Magento system is flawed ... its too complex and confused UX make it more difficult ... Magento developer should learn from Wordpress how to make easy to install and use.. i was hoping they would change the direction with magento 2 but they moved to totally different direction and making it harder and harder ..