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
I just wanted to propose the User/Admin out of sync state not completely stopping or preventing MiKTeX Console startup?
In some use-cases admin updates are being centrally managed and therefore this state preventing startup all together can cause "headaches".
So, is it by any chance possible that this requirement/exception somehow gets "downgraded" to a warning, which does not hinder the MiKTeX Console from starting?
Most probably this will need to be persisted somewhere, that the user has decided to "override" this warning. Such that, in case of any other error-logs, that might get sent to you (the maintainer), it's prominently reported and you can filter out issues reported, to tell them to first go about and sync user/admin, before you continue any serious issue tracking.
Like I said if the user fires up, gets the warning, but continues, and can live with it, ie nothing else breaks -> fine *for everyone.
If she/he still has issues, they can go about and look for someone with Admin privileges to "Run the Admin Update", and if after that there still are issues, then probably the Admin is going to be the one raising tickets here.
Is this a valid thing to ask for - or is it technically or otherwise not feasible or possible?
I decided to put this here as a "feature" request this way, b/c I was guessing the technical feasibility could be answered quicker this way, before needing to deep dive into the source code?
PS: thanks for all the effort put into making TeX work so well.
The text was updated successfully, but these errors were encountered:
Submitting a MiKTeX problem report
I just wanted to propose the User/Admin out of sync state not completely stopping or preventing MiKTeX Console startup?
In some use-cases admin updates are being centrally managed and therefore this state preventing startup all together can cause "headaches".
So, is it by any chance possible that this requirement/exception somehow gets "downgraded" to a warning, which does not hinder the MiKTeX Console from starting?
Most probably this will need to be persisted somewhere, that the user has decided to "override" this warning. Such that, in case of any other error-logs, that might get sent to you (the maintainer), it's prominently reported and you can filter out issues reported, to tell them to first go about and sync user/admin, before you continue any serious issue tracking.
Like I said if the user fires up, gets the warning, but continues, and can live with it, ie nothing else breaks -> fine *for everyone.
If she/he still has issues, they can go about and look for someone with Admin privileges to "Run the Admin Update", and if after that there still are issues, then probably the Admin is going to be the one raising tickets here.
Is this a valid thing to ask for - or is it technically or otherwise not feasible or possible?
I decided to put this here as a "feature" request this way, b/c I was guessing the technical feasibility could be answered quicker this way, before needing to deep dive into the source code?
PS: thanks for all the effort put into making TeX work so well.
The text was updated successfully, but these errors were encountered: