@archprateek don't worry, I saw that. I'll investigate soon.
PitaJ
Posts
-
[nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers needed -
Plugin activation depending on systemhmmm... well ideally plugins and core would only load their assets when necessary. For instance, in core, we only load jQuery UI if we have some jQuery UI thing. There are many other places where we could pull more code out to be on-demand.
-
WebSocket 403 ErrorsYou must set the
url
value in config.json to the URL at which you access your site. -
upgrade command not working@horridbumblebutt
./nodebb upgrade
doesn't upgrade the version of NodeBB. -
[nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers neededNew version. Please try out
[email protected]
Note: this version requires NodeBB v1.5.1npm i nodebb-plugin-calendar@latest
Changelog:
- Better fix for multi-day "all day" events being displayed with the wrong number of days
- Fix all-day dates incrementing when edited
-
Resizing Browser Issue@tradingdojo it's probably because you have too many header icons so the navbar wraps around to a second line.
-
New Persona Mobile Menus@JaredBusch in that case, I'll consider adding a way to switch the sides of the menus. I'll probably add it to the user settings page.
-
New Persona Mobile Menus@JaredBusch I don't know what to tell you. It should be 40% of the screen.
-
New Persona Mobile Menus@JaredBusch you can swipe from almost half of the screen.
-
NodeBB ES6/7npm@5
really stepped it up. It's now insignificantly different in terms of speed. -
Why I chose to use nodeBB over phpBB, Discourse, MyBB and other forums.@Esteban-Constante if you're not clustering, you absolutely should. It should greatly increase the responsiveness of your forum.
-
Nodebb Usage Statistics@julian I imaging it's a count within the top 100,000 visited sites or something
-
Why do I even bother upgrading??Why is there no way to roll back once you upgrade?
Well, it is mostly possible. The only time it isn't is when we make a database change that isn't backwards compatible. Writing a second version of upgrade scripts for every database change we make would be twice as much maintenance for something most people wouldn't use.
Why is there no way to record what version of plugins you have installed besides copying the entire node_modules directory (that is ignored from source control btw)?
./nodebb plugins
will list out all active plugins on your forumWhy do half the plugins and all my templates break when I upgrade?
We try to avoid breaking changes but NodeBB is still under heavy active development. We try to warn people to always check their site setup in a staging instance before upgrading, especially if that upgrade is marked as breaking. We also tell people to backup their NodeBB install and database before upgrading. Our versions are kinda weird and don't really follow the conventions but we're working on that. For now, our versioning works like this:
for X.Y.Z
- X is the named version, we increment it when we feel that NodeBB is significantly different than before
- Y is the major version, we increment it when we make breaking changes
- Z is the minor version, we increment it when we make bug fixes and improvements
In the future we plan on moving to Semver where
- X is the major version, which is incremented on breaking changes
- Y is the minor version, which is incremented on improvements and additions
- Z is the patch version, which is incremented on bug fixes
Breaking changes are a part of life, and while we try to minimize them, sometimes they are necessary to implement features that people want. Other times, they slip in accidentally.
We have a very large API surface and imperfect tests and documentation, which we are working on to improve.Why do I get copious javascript errors in the console when I try to view the new version?
I'm not sure. Please share how you normally upgrade. Also, if you'll share what version you upgraded from and to I'd appreciate it.
-
What's the tpl? View engine?@test217 no, it is not possible. Why? Is there some feature or something that it's missing?
-
What's the tpl? View engine?@test217 it's called templates.js: https://github.com/benchpressjs/templates.js/
-
New Persona Mobile Menus@evoixmr thanks for the reports. I think I've fixed these issues. I've updated Persona again on this forum, so if you'd like to again try to reproduce those issues, I'd appreciate it.
-
Redis Error@Michael-Pfaff yes it might help to add some swap
-
New Persona Mobile Menus@evoixmr it's not released yet. We're testing here first to avoid shipping bugs.
-
How do I use nodebb as an account authorization server?GitHub - julianlam/nodebb-plugin-sso-wordpress: Allows users to log in via a configured Wordpress account
Allows users to log in via a configured Wordpress account - julianlam/nodebb-plugin-sso-wordpress
GitHub (github.com)
GitHub - julianlam/nodebb-plugin-session-sharing: Allows login sessions from your app to persist in NodeBB
Allows login sessions from your app to persist in NodeBB - julianlam/nodebb-plugin-session-sharing
GitHub (github.com)
-
New Persona Mobile MenusHello, everyone!
As you may have noticed, we've made some changes to our flagship Persona theme. On mobile, the slideout menu is now on the left to match with the convention on native phone UIs. We've also moved chats into a separate slideout menu on the right side, so it is now much easier to see how many unread messages you have.
To accomplish these changes, we moved from the existing slideout menu library, Slideout.js, to a brand new, custom built slideout menu library, which we plan on releasing as a separate module soon.
This was a large change, and we want to ensure the functionality and behavior of the menus are flawless. So, we're asking for your feedback. Please reply with any bugs or concerns, thanks!
Child Themes
This Persona change is a breaking change for child themes. To adapt your child theme to the new Persona, you will need to do the following after this new version of Persona is released:
- if overriding the
partials/menu
orheader
templates, update them to include the changes - add the
slit.js
file to themodules
property oftheme.json
, and removeslideout.js
from thescripts
- if using your own client-side JS library instead of the one shipped with Persona, you'll need to implement the same changes made to
persona.js
If you wish to keep the old version of the menus, you will need to do this instead:
- copy the
partials/menu
andheader
templates from Persona so your theme overrides them - copy
persona.js
andslideout.js
to your theme and include them in yourscripts
if you aren't using custom versions already
Known issues
It appears that the Recent Cards plugin incorrectly set the marker telling the slideout menus to ignore touch moves on the cards. This has been fixed and will be released in a new version soon.
- if overriding the