The image is definitely squashed when you look here: https://community.nodebb.org/user/henrywright I'm using Chrome to view the site.

Looks like a warning, but not a serious one. We don't use that package in NodeBB itself so it is likely one of its dependencies

Yep, it's supposed to work like that. It's not really indicative of anything, because we can't really tell how far along a page is when requesting it from the server, so we animate the progress bar to a certain point, and move it to 100% when ready. A bit of an underhanded trick, but it works amazingly to make it look like NodeBB is: Doing something Incredibly fast.

@BDHarrington7 thanks for the link. I'll check out that one, looks a good read.

Thanks @psychobunny That worked with a very slight amendment to the last command: npm unl lwip npm unl redisearch npm i redisearch@^0.0.5 In case it's helpful, before doing that I was getting this error: npm ERR! peerinvalid Peer [email protected] wants redisearch@^0.0.5

@Bri it seems to be related to 2 critical settings for uploads, avatars have there own maximum size while profile headers use the maximum size for any upload that should go in posts

Currently watching categories is opt-out. On forums having lots of new topics, this results in a huge number of items in example.com/unread. I think the unread page would be far more useful if watching categories was opt-in. That way /unread would contain only the items a user is interested in from the start and they won't have to go ignore a bunch of categories in order for /unread to become useful.

@pitaj I did some testing today with /categories 404'd. Seems as though things continued to work fine. I'm not disabling the functionality, just access to the page.

@BDHarrington7 Thanks for the info!

My wife (graphic designer) recommends some sort of row highlighting (alternating row colors) to better separate each location. I will try to get more out of her later.

@pitaj that's true but if not done properly, aliasing links could be very dangerous for a site's search engine ranking. Personally, I wouldn't go down that route (no pun intended ha).

I opened an issue for this. https://github.com/NodeBB/NodeBB/issues/3734

@psychobunny data-component is a fix for ~20 of the errors and there's a few more "single" fixes that address > 1 error so validating won't be as hard as it looks. But I was trying to rally some more eyes to look through the errors because there's some I'm stumped on how to fix best.

Fixes it for me as well, thanks Baris!

@baris although I had the problem on my own forum in the past, I've never seen it here in these forums until yesterday.

This can be easily done with a plugin. Use the static:app.preload hook and add a middleware to the express object. Something like below. myPlugin.onPreLoad = function(data, callback) { data.app.use(function(req, res, next) { if (req.path.startsWith('/') || req.path.startsWith('/api')) { if (req.uid) { helpers.redirect(res, '/recent'); } else { helpers.redirect(res, '/categories'); } } else { next(); } }); callback(); };

@agarcia17 That doesn't disable the route, it just removes the link from the navigation menu.

@baris said in A page containing topics created by users I'm following: ad into recen I still think that ability to see a specific's user for e.g if i am following John, then i should be able to see a list of all the topics they r following to mind common mutual interests. Ofc john should be able to turn this on or off in his privacy settings that his followers can see his topics for which he is following.

@Fastidious master is the development branch.

@julian how about running one huge find and replace job? Wait... on second thoughts maybe not ha