@inna in a plugin/theme you could overwrite that function
// library.js
const helpers = require.main.require('./src/controllers/helpers');
helpers.buildCategoryBreadcrumbs = // copy of function from core with your modifications
@inna in a plugin/theme you could overwrite that function
// library.js
const helpers = require.main.require('./src/controllers/helpers');
helpers.buildCategoryBreadcrumbs = // copy of function from core with your modifications
@Braulio-Cesar-Holtz-Ribeiro try running npm ls nodebb | grep nodebb@
and tell me what that outputs
@evgeniy-onegin you can put CSS in the custom CSS section under ACP > Appearance > Custom stuff
@inna first let me explain how these tokens work
[[admin/menu:alerts.version, 1.2.3]]
This is a translation token. It gets replaced with
Running NodeBB v1.2.3
So you don't need to have [[]]
around {{}}
if you want to print just the version:
{{ version }}
However, it looks like the version isn't exposed on the front-end. So you'll either need to hard code it (and update it whenever you update NodeBB), or use a plugin hook to expose it.
It looks like the mailgun plugin is receiving a response of "Forbidden" from mailgun. I'd double check your settings on the plugin page.
@raj is there an error in the browser console? Have you tried clearing your cache?
@inna you can try putting a console.log
call in there to see whether it's executing. Is it still in the persona file?
Put this in your custom header (ACP -> Appearance -> Custom HTML & CSS -> Custom Header):
<script>
require(['highlight'], function (hljs) {
require([
'https://cdnjs.cloudflare.com/ajax/libs/highlightjs-line-numbers.js/1.1.0/highlightjs-line-numbers.min.js'
], function () {
$(window).on('load action:ajaxify.end', function () {
setTimeout(function () {
hljs.initLineNumbersOnLoad();
}, 100);
});
});
});
</script>
I'm making some changes to better represent minify errors. In the meantime, I suggest you use a JS linter plugin in your editor to provide realtime feedback for syntax errors.
@inna you'd want to put console.log(breadcrumbs)
right before the return at the end of the function. If you put it outside the function it will only execute once at startup
@jongarrison what directory are you expecting them to show up in? They should be showing up in the build/public/templates
directory under whatever template it's called.
How did you install your theme?
@inna files in build
are compilation artifacts. Don't edit anything in there.
What you want to do is add an HTML widget to your global footer. In your ACP go to Customize -> Widgets
Then add a widget to the global footer and put this in it:
[[admin/menu:alerts.version, {{ config.version }}]]
Nice work. Looks really useful.
@abhinov-singh you can't expect urgent help when you reply months late yourself. You can Google how to check if mongodb is running, which would be faster than asking here if it's actually urgent.
Anyways,
systemctl status mongod
@inna yeah I recommend doing this in a custom plugin or theme, rather than editing the persona files directly.
Anyways, you'll need to import categories
and meta
as well like so:
const categories = require.main.require('./src/categories');
const meta = require.main.require('./src/meta');
Everything else looks right
@azeus @evoixmr New version. Please try out [email protected]
npm install nodebb-plugin-calendar@latest
Changelog:
This version has compatibility with [email protected]+, but only officially supports [email protected]
because of the way websockets work, the server only accepts websockets from the true forum URL. For instance, the suunto forum is actually at https://forum.suunto.com/ which does not have that message.
The "connection lost" message is usually caused because the URL at which you are visiting a NodeBB forum is not the "url"
value set in config.json
No no no no no. Comment out the line with var meta
. The one that shows up at the top of the error message you posted. Make sure you uncomment all of those other things.
This is not a bug in NodeBB. As the error message clearly says, the variable meta
was already declared in that scope in library.js. (As const meta ...
)
@azeus the latest upgrades are compatible with NodeBB back to v1.3
You will, however, need to reset your permissions unfortunately because I changed how they worked.