Hello @administrators

Global Sidebar is coming below the global footer.

actually it should come like Below the sidebar content footer should come.

Mobile Screen. Footer content is Coming First and Sidebar Content Coming Next
Screenshot from 2020-06-05 20-29-49.png
Footer Contents in Computer Screen
Also See Footer Content is Not Exactly in Middle when i add sidebar widgets
Screenshot from 2020-06-05 20-29-31.png
Sidebar Contents in Computer Screen
Screenshot from 2020-06-05 20-29-28.png

I think Some Bootstrap Layout issue if Bootstrap is Used.
This issue only if i use Global Widget
Please Consider it and Fix in Next Update

Are you running this on your local machine? Do you have build-essentials installed?

@insuusvenerati try running ./nodebb build and then start NodeBB

My YouTube plugin needs updating. But I'm in London tomorrow to Thursday. Then spending alternate weeks in gibraltar. So its hard to find the time. 😉

Try to select topic starters:

Screen Shot 2015-10-08 at 9.59.02 AM.png

Even more problems in Firefox 41 😉

Guys, this problem also on this board:

https://github.com/NodeBB/nodebb-plugin-composer-default/issues/6

NicolasSiver created this issue in NodeBB/nodebb-plugin-composer-default closed Latest lines in composer are not clickable #6

You did change by moving blocks under component, that is why It doesn't work for old themes.
I have fixed problems.

Same problem again...

Actions that I have made to 'fix' this problem:

Disable single plugin ./nodebb reset plugin="nodebb-widget-essentials" - No Success Disable all plugins - No Success Drop all collections in Mongo, and ./nodebb setup - No Success Delete nodebb.min.js from public directory - No Success Delete all public subdirectories that could be found in .gitignore - No Success Delete public directory and checkout latest from current branch - Success

Maybe it will give you some insights 😉

That error is caused by the following bit of code in src/plugins.js

paths = paths.map(function(pluginLib) { var parent = path.dirname(pluginLib); return cached.filter(function(libPath) { return libPath.indexOf(parent) !== -1; }); }).reduce(function(prev, cur) { return prev.concat(cur); });

If paths is an empty array calling reduce will throw that error. We should add better checks to detect that.

As mega said you need to add all users to a sorted set called users:reputation.

So go through all your users and add their user ids to users:reputation with the score being their reputation.

That's an unrelated bug check here https://github.com/NodeBB/NodeBB/issues/2711

joe1chen created this issue in NodeBB/NodeBB closed Ajaxify prevent default change breaks Admin link in navbar #2711

@Tanner write API could help with that, but until then, here's the high-level implementation/workaround:

FTPP (form-to-post plugin) establishes new POST route at /feedback When that route is called, take req.body.text (where text is the id in the corresponding form) and call Topic.post as a pre-registered user.

That's pretty much it. There's more to expand on (such as spam prevention/throttling/auth/security), but yeah.