@pichalite When i say strange i mean - I'm sure it was working before (now i am wondering how long people havent been able to post for ). Oh well not a big issue in the end. Thanks for your help.
whitts
Posts
-
Registered users can now only see cats available to unregistered users. -
Registered users can now only see cats available to unregistered users.@pichalite Whats really strange is that if i give registered users the rights to create Topics in the main categories the sub cats become available. My current setup looks like this:
-
MainCat1 - Read/View Access but not Create rights
- SubCat1 - Read/Access and Create Rights
- SubCat2 - Read/Access and Create Rights
- SubCat3 - Read/Access and Create Rights
-
MainCat2 - Read/View Access but not Create rights
- SubCat1 - Read/Access and Create Rights
- SubCat2 - Read/Access and Create Rights
- SubCat3 - Read/Access and Create Rights
Before they could post to the sub cats but not the main cats.. now they cant see any of them unless i give create rights in the main cat.
-
-
Registered users can now only see cats available to unregistered users.@pichalite Composer should be the official one from the 0.9.3 release (package.json says its 1.0.26). I havent updated it for a while. The forum is internal unfortunately. Thanks
-
Registered users can now only see cats available to unregistered users.@pichalite Hi, its a mixture.. around 5 main categories out of 7 and loads of sub categories. They can access and read the categories but just cant post to them. I tried removing the Create Topic priv for registered users from the cats and then re-adding it but it didnt help
-
Registered users can now only see cats available to unregistered users.Hello,
I am running Nodebb 0.9.3 with MongoDB. I have been using this forum for a while and it has been working properly but today i noticed that registered users can no longer post to categories that require the user to be registered. When a user goes to post a topic in the composer they only see a subset of categories - there doesnt seem to be anything common between the cats they can see (all areas require the user to be logged in to post). Nothing has changed on the forums in months. My Admin user can see all of the categories.
Logs do not show anything.
Thanks
-
Question and Answer plugin@julian Thanks for checking - i just upgraded to the latest version hoping that it might fix this issue but now i cant mark posts as answered without nodebb crashing:
Newest version crashing nodebb 0.9.3 when marking post as answered 路 Issue #28 路 NodeBB/nodebb-plugin-question-and-answer
I just upgraded to the latest version and when marking a topic as answered, nodebb crashes with the following error: 17/3 11:43 [18316] - error: TypeError: topics.deleteTopicField is not a function at C:\Apps\nodebb\node_modules\nodebb-p...
GitHub (github.com)
Thanks,
-
Nodebb 9.3 - Shutting Down and restarting automatically when clicking InstallPlugin - menu on ACPI just started getting this error today on 0.9.3 as well:
15/3 07:14 [158700] - error: TypeError: Cannot assign to read only property 'id' of <
at Object.Plugins.normalise (C:\Apps\nodebb\src\plugins.js:223:20)
at Request._callback (C:\Apps\nodebb\src\plugins.js:214:12)
at Request.self.callback (C:\Apps\nodebb\node_modules\request\request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:1035:10)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:962:12)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
TypeError: Cannot assign to read only property 'id' of <
at Object.Plugins.normalise (C:\Apps\nodebb\src\plugins.js:223:20)
at Request._callback (C:\Apps\nodebb\src\plugins.js:214:12)
at Request.self.callback (C:\Apps\nodebb\node_modules\request\request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:1035:10)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:962:12)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)I haven't installed any plugins for weeks.
Thanks,
-
Question and Answer pluginHi Julian.. i just started using the unsolved / solved routes and noticed that the solved route is showing all topics (whether they were asked as a question or not / answered or not answered) Where as the unsolved route shows just the unsolved.. Can some one confirm if this is just on my end? Thanks
-
Are there any plugins or themes that change the way the reply box works?@svetlana you can adjust the height of the reply box by dragging the chevron down or up and I believe that it stores it in local storage so that it remembers the height for next time. Does that help?
-
Sort by Newest to Oldest Question@pichalite said:
@whitts I just tried it in testing ground... if you reply... delete and purge the reply the post stays on top
I meant is this is a bug
-
Sort by Newest to Oldest Question25/2 19:33 [162332] - error: TypeError: Cannot set property 'jsonString' of undefined [cluster] Child Process (162332) has exited (code: 1, signal: null) at C:\Apps\nodebb\src\events.js:53:23 [cluster] Spinning up another process... at Array.forEach (native) at C:\Apps\nodebb\src\events.js:50:16 at fn (C:\Apps\nodebb\node_modules\async\lib\async.js:746:34) at C:\Apps\nodebb\node_modules\async\lib\async.js:1212:16 at C:\Apps\nodebb\node_modules\async\lib\async.js:166:37 at C:\Apps\nodebb\node_modules\async\lib\async.js:706:43 at C:\Apps\nodebb\node_modules\async\lib\async.js:167:37 at C:\Apps\nodebb\node_modules\async\lib\async.js:1208:30 at C:\Apps\nodebb\src\database\mongo\hash.js:53:4 TypeError: Cannot set property 'jsonString' of undefined at C:\Apps\nodebb\src\events.js:53:23 at Array.forEach (native) at C:\Apps\nodebb\src\events.js:50:16 at fn (C:\Apps\nodebb\node_modules\async\lib\async.js:746:34) at C:\Apps\nodebb\node_modules\async\lib\async.js:1212:16 at C:\Apps\nodebb\node_modules\async\lib\async.js:166:37 at C:\Apps\nodebb\node_modules\async\lib\async.js:706:43 at C:\Apps\nodebb\node_modules\async\lib\async.js:167:37 at C:\Apps\nodebb\node_modules\async\lib\async.js:1208:30 at C:\Apps\nodebb\src\database\mongo\hash.js:53:4
@pichalite So is the newest to oldest thing a bug then? Thanks
-
Sort by Newest to Oldest Question@pichalite Now i know why i never went to that link - it crashes my forum ... Prob due to me being on an old master.
-
Sort by Newest to Oldest Question@pichalite ah.. at least now i know when someone has deleted and purged
-
Sort by Newest to Oldest Question@pichalite I am trying to replicate it but I cant :(.... Heres a screenshot of what i saw:
Maybe someone posted in the older post, deleted and purged?
-
Sort by Newest to Oldest QuestionHello again,
I have my topics sorted by Newest to oldest and it seem that a new post (say its one hour old) will be positioned below an older post (say 1 week old) if the oldest post has a more recent last reply date (in this case the newest post has no replies since its brand new).
I understand that people want to see the topics with the newest posts but if a new post (with no replies) is newer than the last reply of an older post shouldn't it be at the top?
(i am still on a master branch from a few weeks ago)
Thanks,
-
Mandrill Changes@julian Man, i wish the local emailer plugin could receive emails..
-
Is this bug?I posted this as an issue as well for persona on github thinking it was a theme issue but looks like it could be a composer issue:
-
How you running NodeBB ?Stuck on windows (company VMs) so at first tried to setup NodeBB with NSSM.. Seemed to work fine until the forum crashed and then i ended up with multiple process running (repeat a few crashes and i had so many instances running that everything slowed down).. Now running with nodebb start from a batch file and everything is running great
-
Persona - teaser avatar not showing tooltip with name.I changed the createusertooltips code to:
app.createUserTooltips = function(els) { els = els || $('body'); els.find('.avatar,img[title].teaser-pic,img[title].user-img,div.user-icon,span.user-icon').each(function() { if (!utils.isTouchDevice()) { $(this).tooltip({ placement: 'top', title: $(this).attr('title') }); } }); };
..but it still doesn't work.
The element looks like this in Chrome:
<img class="user-img" alt="myusername" src="/uploads/profile/8-profileimg.jpg">
Shouldnt the title have been injected?
Thanks
-
Persona - teaser avatar not showing tooltip with name.@frissdiegurke I think i should start searching github issues prior to posting from now on.