That’s probably not critical, but it is to be expected, or did I do something wrong?
Also note the box below “Apply” which just says “job.status.warning” - this looks like an unresolved placeholder text.
That’s probably not critical, but it is to be expected, or did I do something wrong?
Also note the box below “Apply” which just says “job.status.warning” - this looks like an unresolved placeholder text.
Hard to tell if that’s normal or not but at least it looks specific to this extension. From what I understand the uninstall did its job from Extension Manager point of view so it should be OK.
Indeed, just fixed it.
I’m not sure because I don’t think that the MD extension does anything with Classloaders. It could be a generic XWiki issue since AFAICS the class should be available in the ClassLoader.
What is uninstalled by default is invalid extensions and extensions are generally invalid because they are missing a dependency, which explain the class not found.
Maybe there’s a missing dependency definition between extensions related to the Markdown plugin or so… I think I remember that during the upgrade before, something related to “markdown” was listed as being “unused”, so I allowed the upgrade process to uninstall it.
Unfortunately, I’m not quite sure though - it might also have been something related to the MediaWiki renderer which we recently installed and also uninstalled again.
So maybe there’s some dependency problem with the MediaWiki renderer… :-/ Sorry that I’m not of any real help here.
So I’ve tried to reproduce but couldn’t. Here’s what I did:
The DW executed and the orphaned step executed:
I selected all of them and clicked Continue and I got an error:
I’ve reported Loading...
But then I clicked continue and it said it worked:
Mh, so there also seems to have been a problem during your removal attempt?
In my case, the extension also seems to be gone after this exception - so not sure what caused it. It does not seem to do any (obvious) harm.
Yes:
Ah, missed this. Thanks!