We can replace manually and rebuild NodeBB ?
EDIT: I replace manually. That fix bug of @ mentions and emojis 🙂
What theme are you using?
We don't use this code anymore in the footer
window.addEventListener('DOMContentLoaded', function() {
require(['forum/footer']);// <--- This line
});
It should look like this
https://github.com/NodeBB/NodeBB/blob/master/src/views/partials/footer/js.tpl
Yeah that theme is using an outdated footer.tpl https://github.com/youhosi/nodebb-theme-oxide/blob/master/templates/footer.tpl. It needs to be updated to match persona https://github.com/NodeBB/nodebb-theme-persona/blob/master/templates/footer.tpl
@RandomAnimeGamer said in Console errors (Emoji, Fetch, & Require) on page load (nodeBB 2.1.0):
https://zbgamewiki.com:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css
Is this file giving a 404 when you try to access it in the browser?
It should load the css like this https://community.nodebb.org/assets/plugins/nodebb-plugin-emoji/emoji/styles.css
@baris said in Console errors (Emoji, Fetch, & Require) on page load (nodeBB 2.1.0):
Is this file giving a 404 when you try to access it in the browser?
It should load the css like this https://community.nodebb.org/assets/plugins/nodebb-plugin-emoji/emoji/styles.css
A very good point I wish I picked up on (I was actually in a work meeting during this exchange entirely asking someone to check for a 404 LOL), I tried loading it the way you did above and got CSS text output successfully.
When I open the file in a new tab the way it's being requested from nodebb, I got ERR_CONNECTION_TIMED_OUT, but not explicitly a 404.
I tried loading as both of the below to get that error:
https://zbgamewiki.com:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=51u9a06pmid
https://zbgamewiki.com:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css
@RandomAnimeGamer I found a solution to the emoji style.css error. As part of the Ubuntu installation guide, it recommends using a port number in config.json's url parameter.
This guide has many flaws, and should be double-checked by the nodeBB team for accuracy. First it has a broken link that (might) have said how to set up SSL with nginx and nodeBB, and now this.
I am still getting the issue on failed to fetch, even after updating config.json, rebuilding, and restarting.
Uncaught (in promise) TypeError: Failed to fetch
at service-worker.js:14:11
event.respondWith(caches.match(event.request).then(function (response) {
if (!response) {
return fetch(event.request);// <--- This line
}
return response;
}));
});
Seems it just up and fixed itself, not sure what caused it. I hadn't been doing any code changes or major restarts, just custom CSS.
Solution to Problem 1 - Not sure, it just fixed itself as I was editing custom CSS.
Solution to Problem 2 - By changing the theme from an old, outdated one to Slick (a more updated theme), this started working.
Solution to Problem 3 - As part of the Ubuntu installation guide, it recommends using a port number in config.json's url parameter. By removing this port specification, the error was resolved.
@RandomAnimeGamer what you mean it recommends specifying a port? Here's a quote from the guide:
Note: When entering your site URL, make sure it is exactly what you plan on accessing your site at. If you plan on visiting http://example.org to open your forum, then enter exactly http://example.org.