Topic on Extension talk:Scribunto

On uninstalling Scribunto

6
Jeblad (talkcontribs)

There are no real explanation on how to uninstall this extension. It can be fairly dangerous to do so, and it can be wise to advice against it on a production system, but a description exist in a previous revision. This explanation is later removed, so use it at your own peril.(diff)

Anomie (talkcontribs)

Note that the same can apply to other extensions, Scribunto isn't particularly special in this respect. Anything that adds a new content model can give issues when removed, as can other things in some cases (e.g. T212742). Even when actual exceptions don't arise, you can easily be left with strange unformatted log entries.

We seem to generally not "officially" post instructions telling people to manually mess around with their databases to try to fix things, as it's easy to make things worse when doing so.

Jeblad (talkcontribs)

Not providing uninstall instructions is pretty bad. I guess all extensions that create new content models should have a warning about corruption of the database if the extension is removed.

And no, I don't do what anyone claim to be “official”, I do what I believe is right.

Anomie (talkcontribs)

Note there's no "corruption of the database" going on. The problem is that removing the extension removes the handler for the perfectly valid data left behind in the database, so attempting to access that data results in an error about the missing handler for the content model.

I'm well aware that you do what you believe is right. Most people do, even if their beliefs conflict with objective reality. (NB: I don't think there's an objective reality in this particular situation, just tradeoffs between different considerations)

Jeblad (talkcontribs)

You are the objective reality? Good to know.

Anomie (talkcontribs)

I specifically said the opposite of that.

Reply to "On uninstalling Scribunto"