Hi! I don’t know exactly the changes after which this behaviour appears. When you go to Page Index or Attachments on any page, a forever-spinning wheel appears. No results.
You can see this behaviour here, or when accessing any page, for instance, this one.
Comments and History on any page work fine. Tree, Deleted Pages and Deleted Attachments work also fine.
I consistently get this error on the web browser console when accessing any failing link:
12:58:03.732 Uncaught TypeError: The specifier “vue” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”. main-DHjSUXv_.js:1:648
I’ve recently updated to XWiki Debian 17.6.0 on Ubuntu 24.04.3 LTS. I’m unsure if the error was there before updating.
I’ve been playing with some XWiki.UIExtensionClass objects (still struggling to remember or find where I added to delete them), and opening/closing some less, css and vm files under /flamingo. I couldn’t find any .bak file, so it seems I didn’t change anything. All files are dated on 28 July. Folders on 8 August. I guess I updated on 8 August. I remember it was last week.
Could I force a new update? Would it be advisable to wait until 17.7.0 by the end of August and see what happens during a new update?
I recognize that I don’t understand how the creation of such an UID can affect the functioning of docextra.vm. But even after deleting them, the forever spinning wheel is still there.
History works fine. It is #Attachments what is failing in all pages. Also, /xwiki/bin/view/Panels and /xwiki/bin/view/Menu fail showing the spinning wheel:
And /xwiki/bin/view/Main/AllDocs?view=index and /xwiki/bin/view/Main/AllDocs?view=attachments fail as well.
Always the same error on the console:
22:53:44.769 Uncaught TypeError: The specifier “vue” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”. main-DHjSUXv_.js:1:648
I’m failing at struggling to understand where I screwed up things. Any help is welcome! Thanks.
It’s definitely not your fault. That’s very easy to miss. We need to improve the way we handle this meta field. @vmassol recently reported Loading... .