search

extdn / extension-dashboard-m2

A Magento 2 dashboard to display installed extensions. Read the blog post on some of the thinking behind it:
https://store.fooman.co.nz/blog/mlau-2019-devexchange-extension-and-security-recap.html
38 stars 6 forks source link

I installed on 2.3.5-P1 community edition and it bricked my admin login. #4

Open ghost opened 4 years ago

ghost commented 4 years ago

You really need to note that this extension is out of date or broken.

After installation i was unable to login to admin. I did all the usual php bin/magento commands after installing extensions to try to recover functionality.

I don't have logs because i had to restore my server immediately after but there were lots of errors about admin backend elements missing..

fooman commented 4 years ago

@theelectricdave Thanks for the feedback. This extension so far hasn't had an official release tagged yet - in particular as we haven't yet been able to create a scalable way to manage the db of all releases in the ecosystem so far.

Seeing that there is a bit of interest in it recently this may push us further towards that goal. Saying that I would not expect this extension to be able to be able to break the admin login functionality in such a way without something else to also be the case.

I have just done a test install, as well as added a basic integration test which performs a test opening the admin dashboard after install which passes successfully.

If you are able to provide specifics of your error more than happy to take a look.

jissereitsma commented 4 years ago

@theelectricdave To further comment on this: If you report any issue to any extension vendor (or developer), please do make sure to save the logs somewhere, because without logs, this is just "hear-say". I've installed the extension just now under Magento 2.3.5-p1 and it works without any issues. Also, did you make sure to follow the right procedure? You mention that you needed to restore an entire server (not just the site?), so I assume this was not done on a testing environment but directly on a production server instead. Even though I would recommend to never ever make changes on a production site directly, still there is a series of steps that need to be undertaken to put any extension into action (go into developer mode, use composer to install this extension, run DI compile, run static content deployment, refresh caching). But because you are not reporting any of these steps, it could very well that you simply missed a step. The more details you provide, the more practical any help becomes. Help us help you and therefore help yourself.