Is there an official 'Solved' option?
-
I was able to see some information in the inspection window. Maybe this helps.
Chromeum; Refused to apply style from 'https://my.domain.com.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. VM105:10 Uncaught ReferenceError: require is not defined at HTMLDocument.prepareFooter (VM105:10:9) nodebb.min.js?v=458fane8fda:9 ServiceWorker registration succeeded. 6post-queue.282afa2be9a276fbee08.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'getAttribute') at HTMLDivElement.<anonymous> (post-queue.282afa2be9a276fbee08.min.js:1:2176) topic-1683141428639:1 Refused to apply style from 'https://my.domain.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. 3post-queue.282afa2be9a276fbee08.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'getAttribute') at HTMLDivElement.<anonymous> (post-queue.282afa2be9a276fbee08.min.js:1:2176) (
Firefox; GET https://my.domain.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda The resource from “https://my.domain.com/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=458fane8fda” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff). Uncaught ReferenceError: require is not defined prepareFooter https://my.domain.com/post-queue/topic-1683141428639:632 EventListener.handleEvent* https://my.domain.com/post-queue/topic-1683141428639:625 topic-1683141428639:632:9
So this looks like it could be fixed by changing some directives in nginx but before I do that, it is nodebb being bad or the config 'suddenly' being bad since it's been fine for something like two years now.
-
-
@NodeHam that's custom CSS, not custom js
-
Oops, sorry, too many things at once.
require(['hooks'], function (hooks) {
hooks.on('action:search.quick.start', function (params) {
params.searchOptions.in = 'titlesposts';
});
hooks.on('action:search.submit', function (params) {
params.searchOptions.in = 'titlesposts';
});
}); -
@NodeHam yeah you'll need to update that js eventually but for now, just disable custom JS and see if that helps.
-
@NodeHam Feel free to contact me on sudonix.com if you'd like me to take a look at this issue to see if we can get it resolved. Obviously, I'll need site details etc, but you can share that over PM.
-
Are you with nodebb? I mean, I don't want to take up your time if this is a nodebb problem.
The board worked fine for a long time and this slowly started to happen. I noticed many months ago that sometimes I could not log in and thought it might only be a multi-session issue, cache or other browser issue but as you know, it's gotten to this after I recently updated.