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 was archived by the owner on Nov 4, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 4, 2021. It is now read-only.
When you enable a plugin, but it immediately errors and disables itself, there's no visual feedback to the user. You must reload the plugins page and only then will the error be shown.
Such real-time events should happen real time on the plugins page. It should update itself when:
a plugin error is added
a plugin disables itself
plugin logs get added where there were none before (maybe)
The plugin logs point is a bit unclear to me. They are only shown in the logs drawer and in there they are loaded live as they arrive. Is that what you meant?
That's why there's a "(maybe)" with that point. The idea is that if there are 0 logs for the plugin, no need to show the "logs" button. If the first console.log gets stored in the db, the button will appear.
Might not be the best, so totally up to whoever is working on this to decide how to go.
Activity
Twixes commentedon Jun 3, 2021
The plugin logs point is a bit unclear to me. They are only shown in the logs drawer and in there they are loaded live as they arrive. Is that what you meant?
mariusandra commentedon Jun 3, 2021
That's why there's a "(maybe)" with that point. The idea is that if there are 0 logs for the plugin, no need to show the "logs" button. If the first
console.loggets stored in the db, the button will appear.Might not be the best, so totally up to whoever is working on this to decide how to go.
Twixes commentedon Jun 3, 2021
Hm, well, there are logs of loaded/unloaded anyway, so I think we can just show Logs always. Also makes it obvious that Logs are even a thing.